prompts: a COBOL two-pass measurement round anyone can run

README.md

@@ -1990,7 +1990,7 @@ it points at the installer's staged copy of the skills when the cwd is not a che
 
 ## Improve it with your agent
 
-[`prompts/`](prompts/) holds twelve **self-contained orchestrator prompts**: the loops this project is
+[`prompts/`](prompts/) holds thirteen **self-contained orchestrator prompts**: the loops this project is
 built with, written so a coding agent can run them. They encode the workflow rather than describing
 it.
 
@@ -2018,11 +2018,13 @@ Three worth starting with:
 | [`capture-audit.md`](prompts/capture-audit.md) | A fresh showcase capture read by parallel adversarial lenses, and the findings turned into family-wide gates. |
 
 <details>
-<summary>The other seven — head-to-head, ranking-eval from your own sessions, per-language, onboarding, sibling sweep, command tour, showcase build</summary>
+<summary>The other ten — head-to-head, ranking-eval from your own sessions, per-language, onboarding, sibling sweep, command tour, showcase build, add a language, quality-panel calibration, COBOL corpus measurement</summary>
 
-The other seven — a paired head-to-head against a competitor, a ranking-eval loop that mines real
+The other ten — a paired head-to-head against a competitor, a ranking-eval loop that mines real
 retrieval misses from your own sessions, a per-language improvement pass, a zero-context onboarding
-study, a sibling sweep, a live command tour, a showcase build — are listed with their audiences in
+study, a sibling sweep, a live command tour, a showcase build, the path a new language's grammar
+actually took, a quality-panel calibration round, and a COBOL two-pass corpus measurement — are
+listed with their audiences in
 [`prompts/README.md`](prompts/README.md). Each states its own scope and its honesty rules, and most name the gates they must leave green.
 
 </details>
@@ -2787,13 +2789,14 @@ files under `bench/`.
 
 ### 16. Improvement
 
-`prompts/` holds twelve **self-contained orchestrator prompts**. Each prompt is a workflow that a
+`prompts/` holds thirteen **self-contained orchestrator prompts**. Each prompt is a workflow that a
 coding agent can run against this repository. Each prompt writes a plan and stops for your approval
 before it runs a command. Build the binary first. The prompts measure against the binary.
 
 The prompts cover a full audit, a gap analysis from real use, a capture audit, a head-to-head
 comparison, a ranking evaluation, a language improvement pass, a zero-context onboarding study, a
-sibling sweep, a command tour, and a presentation build. The index is `prompts/README.md`.
+sibling sweep, a command tour, a presentation build, adding a new language, a quality-panel
+calibration round, and a COBOL corpus measurement. The index is `prompts/README.md`.
 
 If the tool answers incorrectly on your codebase, run `prompts/improve-for-my-language.md`. The
 prompt harvests your session transcript and produces one finding per event with its evidence. Open

prompts/README.md

@@ -10,6 +10,7 @@ before you approve it. Read the plan, cut what you disagree with, then say go.
 | Prompt | Who it is for | What it produces |
 | --- | --- | --- |
 | [`add-a-language.md`](add-a-language.md) | Anyone who wants a language ripwire does not index yet | A vendored grammar, extraction, disclosed blind spots and a red-first gate — the path the Elixir grammar actually took, file by file, including the parse-rate measurement that decides whether to start at all |
+| [`cobol-measure-on-your-corpus.md`](cobol-measure-on-your-corpus.md) | Anyone with COBOL to point it at — public IBM i corpora first, and optionally production code they cannot share, which is a separate, aggregate-only section | Parse rates by artifact kind and PERFORM/CALL/COPY recall **split by tier**, tree edges apart from token-fallback edges, for the two-pass two-grammar stack; occurrence counts for the constructs our roadmap is still guessing at (CICS, embedded SQL, COPY REPLACING, nested programs, free format); and a yes/no on whether a SCIP resolver can produce `typed_enclosing_range`, which is what decides whether the fork can go away (#70). |
 | [`improve-for-my-language.md`](improve-for-my-language.md) | Anyone running ripwire on their own repository — a first session included; the maintainer plan is a labelled section at the end | Transcript-grounded gaps for one language — grammar coverage, symbol kinds, ranking, legends, first-run friction — as an issue-ready report with a reproduction per finding. |
 | [`improve-quality-panel.md`](improve-quality-panel.md) | Anyone whose panel shortlist they can judge — run it from your OWN codebase | Per-family agreement verdicts from blind reads of real functions, misses diagnosed by pipeline stage, and an ordered plan in which any ranking change owes a pre-registered calibration round. |
 | [`full-audit.md`](full-audit.md) | A maintainer, anyone deciding whether to trust the tool, or anyone willing to run it against their own large repository | A severity-ranked, gated audit across six lenses — bugs and hostile inputs, measured performance at the scale rung, verb-to-moment matching, token efficiency, an ecosystem scan of papers and repos with real momentum, and the honesty of the output — after first proving each instrument can see what it measures. |