Make corpus consult mandatory + add live source-site search (v0.7.0)

[kurenn]

Answers "the intake references should always be consulted, and even search the websites provided to match the app being prototyped." Consulting the corpus stops being an optional skim and becomes a mandatory, two-tier discovery step.

Tier 1 — always consult the distilled corpus

• Mandatory within discovery, register-gated (a florist brief matches nothing and correctly pulls nothing — the mandate is "consult," never "must find something").
• Fires before the design-direction confirm, keyed off the emerging register/genre, so corpus moves are part of what the user approves — never a post-yes override. A Step-4 backstop checkpoint stops a rich-brief path skipping it. If a corpus move would change an already-confirmed direction, it's re-presented for a fresh yes. This closes the timing seam (the old instruction keyed off register, set only at Step 4, so it could silently no-op).

Tier 2 — search the source sites live (new)

• When a browser is available and the app matches a corpus genre (or the user shared reference URLs), open ≤3 sites, run one search pass each for the exact components this app needs (a site's ⌘K / component grid / landingfolio's industry filter).
• Reuses the intake browse protocol + privacy guard (only these URLs; discard the user's own tabs). Bounded, transparent, and falls back to Tier 1 alone when no browser — never blocks a build.

Guardrails

• Passed an adversarial review; all 5 findings fixed before this PR — the key one being that the mandate must not override a confirmed design direction (now: consult-before-confirm, refine-not-override).
• SKILL.md untouched (2598/2600); cross-refs resolve; additive doc change.

🤖 Generated with Claude Code