# Architect-bridge smoke test

`ultra-cc-architect` is a separate plugin (extracted in v3.0.0). This
plugin auto-discovers `architecture/overview.md` if produced. This
checklist verifies the bridge still works after either plugin changes.

## Manual checklist

1. Install both plugins from the marketplace.
2. Create a project: `/ultrabrief-local` → produce `brief.md` for a small
   task ("add --verbose flag to a CLI").
3. Run `/ultra-cc-architect-local --project <project-dir>`. Verify
   `architecture/overview.md` and `architecture/gaps.md` appear.
4. Run `/ultraplan-local --project <project-dir>`. Verify the planner's
   Phase 1 output mentions architecture-discovery as one of the inputs
   (look for `architecture/overview.md` in the validator log).
5. Open the resulting `plan.md`. The plan should reference
   `cc_features_proposed` from the architecture note when it picks
   features. The plan does **not** have to adopt them — they are priors,
   not requirements.

## What "works" means

- Discovery finds `architecture/overview.md` (or any of the tolerated
  loose names: `architecture-overview.md`, etc.) and surfaces drift as
  warnings only.
- Plan synthesis cross-references the architecture note without
  hard-failing if it is missing.
- No CI test enforces the bridge; that is intentional. The two plugins
  are filesystem-coupled, not code-coupled.

## When to re-run

- After bumping either plugin's minor or major version.
- After changing `lib/validators/architecture-discovery.mjs` in this
  plugin.
- After changing the architecture-note schema in `ultra-cc-architect`.

## Known tolerances

| Drift | Behavior |
|-------|----------|
| Missing `architecture/` directory | Discovery returns absent; plan proceeds without architecture input |
| Loose name (e.g., `architecture-overview.md` at project root) | WARN; discovery still finds it |
| Body schema changed | WARN; discovery only reads the first heading |
| `cc_features_proposed` missing | Plan ignores priors silently; no error |
