2 commits

Author	SHA1	Message	Date
huishi3	5206ffa4e0	docs(cli): add e2e test placement decision tree and output conventions ... Three docs that answer "where should my new test go?" for CLI-related e2e: - cli/test/e2e/README.md: decision tree across 5 test tracks, Track B boundary, env var setup (SKILLHUB_E2E_*), new-test checklist, CI status - web/e2e/auto-generated/README.md: marks directory as pipeline output, naming convention, boundary with hand-written specs - e2e-automation/README.md: output location convention, module subdirectory layout, boundary clarification (pipeline only produces browser-subject specs)	2026-05-08 03:54:24 -07:00
huishi3	2f54418600	test(cli): add Track B e2e tests against live backend ... 7 end-to-end tests that exercise the CLI against a real SkillHub backend, auto-skipped when SKILLHUB_E2E_REGISTRY/SKILLHUB_E2E_TOKEN are not set: - E1: publish → search (exact slug) → install → content match → remote remove - E2: publish v1 → publish v2 → install latest gets v2 → --version pin gets v1 - E3: install nonexistent slug → non-zero exit - E4: invalid token whoami → EXIT.auth - E5: keyword substring search finds freshly-published skill - E6: SKILL.md missing name field → server rejects - E7: name exceeding length cap → server rejects Includes shared helpers: live-registry env detection, unique slug generation, polling with timeout, and skill fixture builder.	2026-05-07 06:53:01 -07:00