Remove PLAN.md; scrub user-facing links to it [skip tag]

Author: parasxos

.dockerignore

@@ -16,7 +16,6 @@ hooks
 tools
 corpus/raw
 corpus/scripts
-PLAN.md
 docs/MAINTENANCE.md
 CONTRIBUTING.md
 CHANGELOG.md

.github/ISSUE_TEMPLATE/install_works.md

@@ -5,8 +5,7 @@ title: "Install works — [your-handle]"
 labels: ["installed", "external"]
 ---
 
-Quick install confirmation — closes part of the v1.0 gate
-(per [`PLAN.md`](../../PLAN.md) §8).
+Quick install confirmation.
 
 - [ ] I ran `/plugin marketplace add parasxos/claude-plugins`
 - [ ] I ran `/plugin install cpp26-adapter@parasxos/claude-plugins`
@@ -21,5 +20,4 @@ Quick install confirmation — closes part of the v1.0 gate
 
 **Anything that didn't work?** *(Optional — leave blank if everything was clean.)*
 
-<!-- Maintainer note: every confirming install is the social signal the
-     plugin needs to clear its Phase 8 acceptance criterion. Thanks. -->
+<!-- Maintainer note: every confirming install is a real social signal. Thanks. -->

CONTRIBUTING.md

@@ -1,9 +1,8 @@
 # Contributing to cpp26-adapter
 
 Bug reports, eval-task suggestions, and install confirmations are all
-welcome. The repo carries the full build history (16 commits across
-the 9 binding-plan phases), so reading [`PLAN.md`](PLAN.md) and the
-commit log gives a clean picture of why every component exists.
+welcome. The commit log carries the full build history and gives a
+clean picture of why every component exists.
 
 ## Quick paths
 

PLAN.md

@@ -90,9 +90,8 @@ mcp-server/
   pyproject.toml            ← deps: mcp, pyyaml, pydantic, rapidfuzz
   tests/                    ← pytest; run via `pytest mcp-server/tests`
 
-PLAN.md               ← the binding plan (v1.1); reference, not edited per refresh
 README.md             ← user-facing layout overview
-MAINTENANCE.md        ← this file
+docs/MAINTENANCE.md   ← this file
 ```
 
 ## Plugin naming convention

docs/MAINTENANCE.md

@@ -9,7 +9,7 @@ The two gates standing between today and `v1.0.0`:
    triggers a `v1.0.0` bump.
 
 2. **≥1 external installer.** Per the binding plan's Phase 8 acceptance
-   ([`PLAN.md`](../../PLAN.md) §8). This is genuinely social — someone
+   (the binding plan §8). This is genuinely social — someone
    other than `parasxos@gmail.com` needs to install via the marketplace
    command and ideally provide a confirming signal (a star, an issue,
    a comment, a clone).
@@ -141,7 +141,7 @@ https://github.com/parasxos/cpp26-adapter
 
 A long-form post that walks through the architecture lives at
 [`docs/architecture.md`](../architecture.md) and the binding plan
-that drove the implementation lives at [`PLAN.md`](../../PLAN.md).
+that drove the implementation lives at the binding plan.
 For a blog, the natural structure is:
 
 1. The problem (LLMs default to pre-C++26 because of training data)

docs/announce/RELEASE_PREP.md

@@ -119,6 +119,4 @@ the cyan box of the diagram while the reviewer lives in the pink.
   scored by regex against fenced cpp blocks + LLM-judge for quality.
   v0.9.0 cleared 95% on first audited run.
 
-See [`PLAN.md`](../PLAN.md) for the full binding plan with phase-level
-acceptance criteria, and [`MAINTENANCE.md`](MAINTENANCE.md) for the
-quarterly refresh process.
+See [`MAINTENANCE.md`](MAINTENANCE.md) for the quarterly refresh process.

docs/architecture.md

@@ -20,4 +20,4 @@ python3 -m venv .venv
 
 ## Wire-up
 
-The plugin's `.mcp.json` registers this server as `cpp26-ref` and launches it via stdio. See Phase 3 of `PLAN.md`.
+The plugin's `.mcp.json` registers this server as `cpp26-ref` and launches it via stdio.