Grill the bunx installer design

[diegohb]

Grill the bunx installer design

What to build

A decision record — posted as a comment on the installer implementation ticket — settling how the bunx opencode-architect CLI works. Run the grilling skill with the maintainer and drive every open question to a decision. This package's payload differs from the aurelia-expert reference (ten opencode-* agents plus bundled references, not skills), so the reference pattern cannot be cloned blindly.

Questions the session must settle:

• Payload and targets: what exactly does install copy into the consumer's project, and where? Agents are copied for transparency (ADR-0001); references resolve at load time (ADR-0003); the plugin entry already auto-installs from opencode.json. How does the CLI's copy target coexist with the plugin auto-install path — alternative, complement, or replacement? What happens when both are used?
• Command set: install, status, uninstall (à la aurelia-expert), or a different surface?
• Scope semantics: local (project .opencode/) vs global (~/.config/opencode/) — what applies to agents vs references in each scope?
• Idempotency: version-marker strategy for no-op re-runs and upgrades.
• Test strategy: what the installer test suite covers.

Acceptance criteria

• Every question above has a recorded decision with rationale, or is explicitly deferred with a reason
• Decision record posted as a comment on the installer implementation ticket
• Decisions do not contradict ADR-0001 (copy transparency), ADR-0002 (runtime docs sync), or ADR-0003 (reference resolution)

Blocked by

None (can start immediately).