refactor: drop cross-project spec-validation parser machinery

The fence-label -> parser fact, the specify/grounding-check/planner
parse gates, the parse-trace attestation, and all their cross-references
served a single real user (ailang). Convention over configuration: the
generic machinery is removed plugin-wide; the one consumer carries an
equivalent project-local directive in its own CLAUDE.md.

Archive under docs/plans and docs/specs left intact as time documents.

planner/SKILL.md

@@ -221,22 +221,6 @@ Before handing the plan off, run this checklist inline:
    so "nothing ran" cannot masquerade as "nothing
    regressed". This is a recurring defect family — scrub
    every Run step whose assertion lives in a filter string.
-9. **Parse-the-bytes-you-inline gate.** Every verbatim code body
-   the plan inlines into a task step must be run through the
-   spec-validation parsers the project declares in its CLAUDE.md
-   project facts, following the parser-invocation protocol in
-   `docs/conventions.md` (which owns the no-parser skip, the
-   malformed-entry failure, and the no-op when the project
-   declares no spec-validation parsers) before
-   hand-off. The target is the surface-language snippets the plan
-   lifts verbatim (example programs, fixtures); the project's
-   source-language test / implementation bodies are NOT the
-   target — the `implement` compile gate catches those. A parse
-   failure is a plan failure — the plan would hand the
-   implementer bytes that do not parse, the last defensive line
-   before dispatch — fix the plan, do not hand off. The
-   parse-trace goes into the planner's self-review activity (the
-   session) as the attestation the gate fired.
 
 Fix issues inline.
 
@@ -268,7 +252,6 @@ The planner skill does not perform the commit itself.
 | "Step 5 'implement the parser' is fine, I'll detail it at execution time" | Then it's not a step, it's a wish. Steps are bite-sized OR the plan isn't done. |
 | "Task 7 is similar to Task 4, just say so" | The executor may read tasks out of order. Repeat the code. |
 | "The spec has a TBD too, I can pass it through" | Bounce back to `specify`. Plans inherit spec gaps; spec gaps are not plan placeholders. |
-| "The example program came straight from the spec, it must be valid" | The spec's code blocks are hypotheses, not verified bytes — specify's parse gate can be skipped and a post-spec edit can break them. Re-parse every surface-language body you inline against the spec-validation parsers the project declares in its CLAUDE.md project facts; this is the last line before the implementer hits it (issue #1 Fix 4). |
 
 ## Red Flags — STOP
 
@@ -279,10 +262,6 @@ The planner skill does not perform the commit itself.
 - Step descriptions longer than the code they describe
 - Header missing parent spec reference
 - Self-review skipped because "the plan looks fine"
-- A task step inlining a surface-language code body whose fence
-  label has a project-declared spec-validation parser (its
-  CLAUDE.md project facts), handed off without a parse-trace in
-  the planner session
 
 ## Cross-references