✨ Make CLI context handoff production-ready#269
Merged
Conversation
Make build context render the canonical app shape, add local baseline truth parity, and surface agent handoff commands from cloud and TDD runs.
Render syntax tokens with normal spans instead of CSS Custom Highlight API selectors so Lightning CSS can minify the reporter bundle cleanly.
Clear per-run report, detail, current, and diff artifacts before each local TDD run while preserving approved baselines. This keeps CLI dogfood context aligned with the screenshots captured in the current run.
Surface the generated local report URL in workspace context and include reviewed screenshot names in all-green agent handoffs so agents can orient from the current run without switching to JSON first.
Run broader SDK E2E flows through local TDD context and make the Swift E2E assert the agent handoff before cleanup. Also refresh the Ember test-app lockfile metadata corrected by npm install.
Simplify the Swift SDK E2E handoff cleanup and make agent context evidence classification resilient to status-only failed comparisons.
d7785fa to
13291f4
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
## Summary This PR layers the secure cloud auth flow on top of the CLI context work from #269. - Separates user login from project upload credentials - Adds `vizzly project link <org>/<project>` for minting project-scoped upload credentials - Stores linked project tokens in macOS Keychain when available, with config-file fallback - Uses linked project tokens for cloud uploads while keeping user JWTs for review actions - Prevents failed project-token requests from consuming user refresh tokens - Updates review commands so approval/comment actions require user auth instead of project tokens - Adds credential-store coverage for Keychain/file fallback behavior ## Testing - node --test tests/commands/project.test.js tests/utils/config-loader.test.js tests/project/core.test.js tests/project/operations.test.js tests/commands/login.test.js tests/commands/review.test.js tests/api/client.test.js - node --test tests/utils/project-link-store.test.js tests/commands/project.test.js tests/utils/config-loader.test.js tests/api/client.test.js tests/commands/review.test.js - npm run lint - npm run build - git diff --check
This comment has been minimized.
This comment has been minimized.
Vizzly - Visual Test ResultsCLI Reporter - 1 change needs review
CLI TUI - 2 changes need review
Changes needing review (2)vizzly-tdd-help · 1202×578 · 27.8% diff vizzly-help · 1202×1430 · 283.8% diff
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
This PR makes the CLI a much more natural local context surface for agents and SDK dogfooding.
Testing