The --yes guard counted the conditionally-skipped seederTier prompt as a
missing required value, so `create <id> --architecture polling ... --yes`
failed even though seeders only apply to websocket plugins. The guard now
only requires seederTier when the resolved architecture is websocket.
This bug shipped in 1.3.0 and was missed in manual UAT (the polling case
was exercised interactively, not with --yes). The new test suite caught it.
Also in this change:
- Add packages/wwv-cli/test/create.test.mjs: 9 integration tests that spawn
the built CLI into temp dirs and assert the scaffolded tree (polling vs
websocket, community vs private seeder tier, billboard/model/point render,
--core, kebab-id naming, icon mapping, and the --yes / invalid-flag /
duplicate-dir failure guards). Uses Node's built-in test runner, no new deps.
- Add .github/workflows/cli.yml: path-scoped to packages/wwv-cli, runs
build (tsc) + the integration tests. Fast versus the full app suite.
- Add paths-ignore for packages/wwv-cli to the heavy app workflows (ci,
playwright, docker-publish, test-setup-scripts, test-local-dev push) so a
CLI-only change runs just cli.yml instead of the whole suite.
- Bump CLI to 1.3.1 and add a test script.
* refactor(docker): separate self-host Docker compose structure from development
test(ci): add github action to verify self-host scripts
* Potential fix for pull request finding 'CodeQL / Workflow does not contain permissions'
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
---------
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>