test: add AXI user journey tests for agent subcommand

[robertolopezlopez]

Summary

• add private-binary user journeys for the agent home view and input errors
• cover default, subset, and individual SCA, SAST, Secrets scanner selection
• cover Container image validation and local image selection

Validation

• private build passed against local AXI checkout
• 2 Jest suites, 9 tests passed
• Prettier, ESLint, git diff check, and make lint passed

Dependency

Draft pending publication of the AXI sast rename and subsequent cliv2-private Go module bump.

CLI-1700

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[robertolopezlopez]

clean private builds still pin AXI 734c2ae85a0a, which accepts code, so every new sast journey fails before scanner selection

[robertolopezlopez]

PR Reviewer Guide 🔍

🧪 PR contains tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

External API Dependency 🟡 [minor]
The beforeAll hook defaults SNYK_API to https://api.snyk.io if TEST_SNYK_API is not provided. According to the CONTRIBUTING.md section on 'Acceptance tests', tests should never call remote endpoints and should instead use fake-server or other mocks. Hardcoding a production URL as a fallback risks unintended external calls during local development or misconfigured CI runs.

SNYK_API: process.env.TEST_SNYK_API ?? 'https://api.snyk.io',

📚 Repository Context Analyzed

This review considered 3 relevant code sections from 3 files (average relevance: 1.00)

• CLAUDE.md (lines 94-229)
• package.json (lines 1-236)
• CONTRIBUTING.md (lines 135-311)

🤖 Repository instructions applied (from AGENTS.md)

what do you think @PeterSchafer

(edit) I am ignoring this, as discussed yesterday I should make use of real server

[PeterSchafer]

Suggestion: The PR looks good! Let's update the commit and get this merged :)

[robertolopezlopez]

I believe this is done already

[PeterSchafer]

Suggestion: this is done globally in setup.

[PeterSchafer]

Suggestion: this is done globally in setup.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 4 relevant code sections from 3 files (average relevance: 1.00) CLAUDE.md (2 segments, lines 94-229) package.json (lines 1-236) CONTRIBUTING.md (lines 135-311)

🤖 Repository instructions applied (from AGENTS.md)