docs: VistA bridge library architecture, worked examples, and plans reorg

docs/README.md

@@ -61,7 +61,7 @@ Each doc is labeled `[TYPE · type? · connection · connection?]`.
 
 ## `plans/` — Implementation and roadmap plans
 
-- **`plans/discoverability-and-tooling-plan.md`** — `[PLAN · planning]` Phased plan to turn m-stdlib into a first-class discoverable surface across the source, CLI, VS Code, and AI consumption channels.
+- **`plans/historical/discoverability-and-tooling-plan.md`** — `[PLAN · planning]` Phased plan to turn m-stdlib into a first-class discoverable surface across the source, CLI, VS Code, and AI consumption channels.
 - **`plans/future-modules-plan.md`** — `[PROPOSAL · planning]` Parking lot for module candidates that haven't crossed TDD-red yet, with priority and promotion process.
 - **`plans/m-libraries-remediation.md`** — `[ROADMAP · planning · design]` Background remediation strategy and prioritised roadmap derived from the M libraries survey — decisions locked.
 - **`plans/m-stdlib-implementation-plan.md`** — `[PLAN · planning · implementation]` Live per-module work plan with phase status, non-negotiables, and per-module specs for v0.0.1 through v0.4.0.

docs/guides/m-doc-grammar.md

@@ -5,7 +5,7 @@ audience: m-stdlib maintainers writing or editing `; doc:` blocks; toolchain
   authors implementing the manifest generator (WA4), the `M-DOC-001` lint
   rule (WA3), the `m doc` family (Wave B), the VS Code extension (Wave C),
   the AI skill (Wave D), or any other consumer of m-stdlib metadata.
-plan: docs/plans/discoverability-and-tooling-plan.md (the design rationale —
+plan: docs/plans/historical/discoverability-and-tooling-plan.md (the design rationale —
   this guide is the normative spec implementing § 3.1)
 tracker: docs/tracking/discoverability-tracker.md (WA1 closes when this guide
   is reviewed; WA2 is the backfill that brings src/ into compliance)
@@ -478,7 +478,7 @@ codebase.
 
 ## 10. Cross-references
 
-- [Discoverability & tooling plan, § 3.1](../plans/discoverability-and-tooling-plan.md#31-formalise-an-m-doc-grammar-extends-does-not-replace--doc) — the design rationale this guide implements.
+- [Discoverability & tooling plan, § 3.1](../plans/historical/discoverability-and-tooling-plan.md#31-formalise-an-m-doc-grammar-extends-does-not-replace--doc) — the design rationale this guide implements.
 - [Discoverability tracker, WA1–WA4](../tracking/discoverability-tracker.md#wa1--specify-m-doc-tag-grammar) — work items: WA1 ships this guide; WA2 backfills tags into src/; WA3 implements `M-DOC-001`; WA4 ships the manifest generator that consumes the grammar.
 - [Module tracker D2](../tracking/module-tracker.md#deferred-decisions--revisit-triggers) — the `@stable` SemVer CI gate is deferred; annotating now keeps the option open.
 - [STDJSON source — `parse` label](../../src/STDJSON.m) — the worked example in § 6 is sourced from this file.

docs/modules/index.md

@@ -17,7 +17,7 @@ this file is the released-module catalogue.
 Beyond the human-readable tables below, the released stdlib also
 ships a structured surface that downstream tools (m-cli `m doc`, the
 planned VS Code extension, the planned AI skill) read at runtime.
-Source: [`docs/plans/discoverability-and-tooling-plan.md`](../plans/discoverability-and-tooling-plan.md).
+Source: [`docs/plans/historical/discoverability-and-tooling-plan.md`](../plans/historical/discoverability-and-tooling-plan.md).
 
 | Artefact | Path | Purpose |
 |---|---|---|

docs/plans/discoverability-and-tooling-plan.md → docs/plans/historical/discoverability-and-tooling-plan.md

@@ -778,18 +778,18 @@ Tracker note logged.
 
 ## 12. Cross-references
 
-- [`README.md`](../../README.md) — top-level project overview, phase
+- [`README.md`](../../../README.md) — top-level project overview, phase
   plan, module inventory.
-- [`CHANGELOG.md`](../../CHANGELOG.md) — release history; the
+- [`changelog.md`](../../tracking/changelog.md) — release history; the
   manifest's `since:` fields must match.
-- [`docs/modules/index.md`](../modules/index.md) — phase-keyed
+- [`docs/modules/index.md`](../../modules/index.md) — phase-keyed
   catalogue; will gain a "manifest" link in Wave A.
-- [`docs/plans/m-stdlib-implementation-plan.md`](m-stdlib-implementation-plan.md)
+- [`docs/plans/m-stdlib-implementation-plan.md`](../m-stdlib-implementation-plan.md)
   — the live build plan (modules and phases). This plan runs in
   parallel.
-- [`docs/guides/m-tdd-guide.md`](../guides/m-tdd-guide.md) — TDD
+- [`docs/guides/m-tdd-guide.md`](../../guides/m-tdd-guide.md) — TDD
   workflow; doctests in §3.4 land additional `*TST.m` routines into
   the same workflow.
-- [`docs/tracking/module-tracker.md`](../tracking/module-tracker.md)
+- [`docs/tracking/module-tracker.md`](../../tracking/module-tracker.md)
   — the work board; manifest stability tier (§3.6) feeds promotion
   decisions on this board.