extraction-report.sh never reads extraction-quality*.json, so the Stage 1 surface shows no extraction quality at all #151

What happens

skills/extractor-quality-loop.md makes the validator's extraction-quality.json the proof that an extraction reached the 95% gate: dimensions, found/expected, gaps, confirmedZeros, selfGraded. bin/extraction-report.sh is the Stage 1 surface, but it contains no reference to that file (grep -n extraction-quality bin/extraction-report.sh → nothing).

On a knowledge base whose provenance resolves to documents, most sections are correctly skipped. The result is a surface that shows nothing about the extraction's measured quality, even though the quality file sits next to the extracted output.

Evidence (card-disbursement requirements-driven build, 2026-09-25)

• A project-local extractor for a non-code source (an XMI/BPEL process model, scored on its own six dimensions per the skill's "not code-shaped" section) wrote analysis/<src>/extracted/extraction-quality-*.json, at 100% on 7 dimensions.
• extraction-report.sh . → "2 pass, 18 skipped", with no quality section.
• The project cited the scores in triage.md and in the register instead.

Repro

1. Put an extraction-quality.json (the skill's example shape) under analysis/<src>/ or analysis/<src>/extracted/ next to a documents-provenance KB.
2. Run bin/extraction-report.sh <p>: nothing on the page mentions it.

Suggested fix

• Discover extraction-quality*.json under the analysed KB's directory tree. The skill says analysis/<Project>/extraction-quality.json; the field project used extracted/extraction-quality-<name>.json, so accept both.
• Render one section per file with:
  • every dimension's score, found/expected and gaps (the keys come from the file, not a fixed list — the skill allows a stack's own dimensions);
  • the overall score against threshold;
  • confirmedZeros;
  • selfGraded, rendered as a fault when set with passed: true, since the skill says a self-graded report cannot pass.
• Absence should be skipped for a KB with no extractor (text-native corpora), and fault when the provenance says an extractor ran.
• Optionally, the Stage 1 gate could read the same file.

Filed rather than fixed because the renderer's section model and provenance rules need a golden KB captured from a real extractor run for each provenance.

Files

• bin/extraction-report.sh
• skills/extractor-quality-loop.md: output format, file location
• bin/gate-check.sh Stage 1: optional