chore(forgeplan): activate cluster A + deprecate stale PRD-001

[fedorovvvv]

Summary

• Activate 7 RFCs/SPEC in cluster A whose parent PRDs already shipped active via Global installation of forgeplan/web without project initialization. Incremental ports. Tabs for switching between multiple instances #109/feat: multi-instance management (#109) #118 (draft → active).
• Deprecate stale PRD-001 (title/body mismatch — both interpretations shipped out-of-band).
• Health: 79 → 86 active, 16 → 8 draft, 2 → 3 deprecated.

Why

forgeplan health was misleading: 7 supporting RFC/SPEC artifacts plus 1 muddled PRD sat in draft with parents that were long active with R_eff > 0. This was process debt from the forgeplan activate step being skipped at the end of the multi-instance + citty waves. Pure artifact-lifecycle hygiene — no code change, no behaviour change.

Cluster A (activated)

Artifact	Title	Parent (active)
RFC-020	citty integration architecture — bin/ subcommand split	PRD-024
RFC-021	Scope resolver + user-scope path conventions for init	PRD-025
RFC-022	start scaffold-resolution algorithm + error UX	multi-instance wave
RFC-023	Port allocator, pid-liveness probe, atomic registry writes	PRD-027
RFC-024	Combobox primitive — bits-ui wrapper, /playground showcase	PRD-029
RFC-025	HealthBar instance switcher + /api/instances readonly endpoint	PRD-029
SPEC-003	Instance registry JSON schema (~/.forgeplan-web/instances.json)	PRD-027 + ADR-004

PRD-001 (deprecated)

Title says "Show forgeplan + forgeplan-web versions in UI footer" — long shipped (__FORGEPLAN_WEB_VERSION__ + /api/health integration). Body says "Bootstrap CLAUDE.md baseline + add methodological guides" — also shipped (Red lines, routing table, hook table, guides/INDEX.md/CLAUDE-MD-GUIDE.ru.md/GIT-FLOW-GUIDE.ru.md all present).

The artifact's markdown was Lance-only (never in git history); deprecation surfaced it as a new file at prds/PRD-001-…md with status: deprecated. EVID-004/EVID-005 still link to it — they're frozen evidence, no rework needed.

Test plan

• forgeplan health runs clean — verdict: healthy, no new orphans.
• Front-matter status: correct on all 8 files (active × 7, deprecated × 1).
• No code touched (verify via git diff --stat origin/develop...HEAD).
• Reviewer: confirm no parent PRD lost evidence pointer (relations are append-only in markdown, but worth a glance at the diff).
• CI: smoke matrix green (no functional change but rule-21/22/23 verifications still run).

Reversibility

Fully reversible: edit status: line back to draft in front-matter, run forgeplan scan-import to refresh Lance. No git surgery needed.

Drift risks

• Lock contention — forgeplan activate ran in parallel hit the workspace lock 4× during this PR's prep. The CLI is not concurrency-safe for one workspace. Future cluster operations should serialise; not blocking for this PR.
• PRD-001 dependents — EVID-004/005 still claim to "support" PRD-001. Since PRD-001 is now deprecated, those evidence packs are formally orphaned-by-status. No automatic cleanup; leaving them as historical record.

Refs: PRD-024, PRD-025, PRD-027, PRD-029, ADR-004