Skip to content

fix(cli): render setup validation errors cleanly - #966

Draft
blafourcade wants to merge 2 commits into
nextfrom
fix/cli-setup-validation-auto
Draft

blafourcade wants to merge 2 commits into
nextfrom
fix/cli-setup-validation-auto

Conversation

@blafourcade

Copy link
Copy Markdown
Contributor

🎯 What & why

aidd setup --scope user --ai claude --plugins all now prints the existing refusal and remedies and exits 1 without a stack trace or minified bundle dump. Help and README explain the shipped user-scope limits.

🛠️ How it works

Construct SetupFlow inside the existing command error boundary. Cover constructor refusals through command and built-binary tests, derive help support from the registry, and update the setup help snapshot. Domain validation and installation capabilities stay as shipped.

🧪 How to verify

  • pnpm --dir cli test: 6,805 passed; one existing opt-in runtime test skipped.
  • Commit hooks: 549 repository script tests, lint, architecture, typecheck, type-honesty, and documentation checks passed.
  • Pre-push dead-code analysis passed. Independent review reran 62 domain, command, and hermetic e2e tests.

⚠️ Heads-up

The unchanged startup update-check hook may construct dependencies before the setup action runs. The regression proves that a refused setup action does not create its own dependencies. Existing unrelated lint and Vitest deprecation warnings remain.

🔗 Linked issue

Closes #891

✅ I certify

  • I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

Keep unsupported user-scope combinations inside the command error boundary so intentional refusals print remedies without a stack trace. Document current registration and installation scope limits.

Refs #891

AIDD-Session-Id: 01a111bd-4959-7be1-9ad4-093a46ef8295
Record the approved review and outcome challenge for #891, mark the plan reviewed, and clarify that dependency construction assertions apply to the setup action.

AIDD-Session-Id: 01a111bd-4959-7be1-9ad4-093a46ef8295
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant