Skip to content

Doc gate: 7 of the README's 8 eigenscript blocks are still unchecked — triage which are runnable #949

Description

@InauguralPhysicist

Follow-up from the #947 review (closed #934). The gate itself is sound — the
scanner widening loses zero legacy coverage (79 blocks before and after,
identical sets), and three planted faults all fire: drifted output fails naming
README.md:136, a dropped check marker trips the per-file zero-coverage guard
while the other files stay at 79, and an orphaned marked block is reported by
file and line.

What is thin is the coverage it currently buys:

eigenscript check            1
eigenscript (unmarked)       7
eigenscript skip             0

Opt-in is the right default — the README genuinely carries illustrative fences
that are not whole programs — but one checked example out of eight means the
README is nearly as free to drift as it was before, and the per-file
zero-count guard cannot tell "deliberately illustrative" from "nobody got to it".

Work: walk the seven unmarked blocks and put each in one of three states —
eigenscript check with an output fence, eigenscript skip with a one-line
reason, or a plain ``` fence because it is a fragment rather than a program.
After that pass, an unmarked eigenscript fence in the README is a defect, and
the gate can say so.

Small and clean-scope — a good on-ramp.

Related: #934, #945, #946.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions