✨ Prove packaged CLI cloud context flow

[Robdel12]

What changed

• Extends the packaged prod smoke harness so it installs the packed CLI, links the real vizzly/frontend project, creates a real cloud build through vizzly run, captures a screenshot, and verifies context build current --source cloud --agent --json resolves that build.
• Parses JSON-lines CLI output in the smoke harness, which matches the real vizzly run --json stream instead of assuming a single JSON object.
• Adds a CLI integration test proving explicit --org / --project scope selects cloud review queue data even when local workspace data exists.
• Ships the smoke script in the package tarball and softens the remaining forced "UI context" phrasing in agent help text.

Verification

• ./node_modules/.bin/biome check --write scripts/smoke-prod-pack.js src/commands/context.js tests/commands/context-cli.test.js package.json
• node --check scripts/smoke-prod-pack.js
• node --test --test-reporter=spec tests/commands/context-cli.test.js tests/commands/context.test.js
• npm run smoke:prod:pack against the real production API and real vizzly/frontend project
• npm run lint
• npm run build
• npm test
• git diff --check

[vizzly-testing]

Vizzly - Visual Test Results

CLI Reporter - 1 change needs review

Status	Count
Passed	18
Meaningful diffs	1
Auto-approved	18

Meaningful diffs needing review (1)

fullscreen-viewer · Firefox · 375×667 · 78.5% diff

Review changes

CLI TUI - 1 change needs review

Status	Count
Meaningful diffs	1
Auto-approved	4

Meaningful diffs needing review (1)

vizzly-run-help · 1202×722 · 13.2% diff

Review changes

---

_{rd/cli-release-readiness-audit · f81cc473}