spec: 010 Tasks 11.6 and 11.9 — the section with no file, the file with no rule - #108
Merged
Merged
Conversation
…th no rule Two ends of the same defect. 11.6 is a convention describing a file this repo does not generate; 11.9 is a published file no rule reached. The llms.txt section now describes what GitBook serves, measured live while writing it: 56,527 bytes, 201 entries, 201 with a description — 143 here and 58 from v9 — plus an Agent Instructions section the platform appends, documenting a ?ask= query endpoint nothing in this programme had recorded. No type field, and none should be added: the banner carries the type and the .md variant prints it. Writing it pinned a third source down. A line's three parts come from three places: the slug from the filename (Phase 10 learned that the hard way), the description from front matter, and the title from the SUMMARY.md entry text — not the H1. Measured: 32 pages spell the two differently and the index uses the SUMMARY text on all 32. Nobody had asked, because on the other 110 they agree. One claim in the first draft was wrong in this programme's usual direction: it said every v9 description opens with "Superseded". The prefix is "Brighter V9 (superseded)." and the example URL named a space root that does not exist. Checked against the bytes and corrected before the commit. That check found three v9 pages carrying the prefix and nothing else — DarkerBasicConfiguration, ImplementAQueryHandler and Logging, whose bodies are an H1 and, twice, the word TODO. The empty description is the symptom; the empty page is the defect. Left for a ruling, with the precedent recorded. README.md now takes rule 7. The boundary was never a policy: opening_sentence() skips the line after the H1 because on all 142 pages that line is the banner, and on the README it is the sentence — so pointing the rule at the file unchanged would have summarised the site root with its second paragraph and reported correct front matter as a mismatch. Root pages take rule 7 and nothing else, and are excluded from the uniqueness corpus as well as its reporting. Red-proofed on four branches with the extractor called directly first, because rule 7 has already been green while reading the wrong input. pagelint's corpus is 143 pages from this commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spec 010, Phase 11, Tasks 11.6 and 11.9. No page under
contents/changes; nothing published moves.Two ends of the same defect. 11.6 is a convention describing a file this repository does not generate. 11.9 is a published file no rule reached.
Task 11.6 — the
llms.txtsectionRewritten from a live measurement rather than from memory: 56,527 bytes, 201 entries, all 201 carrying a description — 143 from this space, 58 from
v9— plus a trailing Agent Instructions section GitBook appends, documenting a?ask=<question>query endpoint nothing in this programme had recorded.No type field, and none should be added. The banner carries the type and the
.mdvariant prints it one line under the H1, so a prefix would spend the snippet repeating what the page is about to say. AC9 was narrowed for exactly this.A third source, finally pinned down
A line is
- [Title](url): description, and its three parts come from three different places:SUMMARY.mdentry text, not the H1SUMMARY.mdtext on all 32Nobody had asked where the title came from, because on the other 110 pages the two agree and either answer looks right.
One draft claim was wrong, in the usual direction
The first draft said every
v9description opens with "Superseded". It isBrighter V9 (superseded)., and the example URL named a space root that does not exist —v9's pages publish under this space's path. Both were plausible reconstructions of a session's work. Checked against the bytes and corrected before the commit.And that check found three
v9pages carrying the prefix and nothing else —DarkerBasicConfiguration.md,ImplementAQueryHandler.md,Logging.md, whose bodies are an H1 and, twice, the wordTODO. Phase 10's sweep behaved correctly: there was no sentence to append. The empty description is the symptom; the empty page is the defect. Left for a ruling, with the precedent (Phase 10 removed six empty scheduler pages fromv9's SUMMARY) recorded next to the way these three differ.Task 11.9 —
README.mdtakes rule 7The boundary was never a policy.
opening_sentence()skips the line after the H1, because on all 142 pages that line is the banner. On the README, that line is the opening sentence — so pointing the existing rule at the file unchanged would have summarised the site root with its second paragraph and then reported its correct front matter as aDESCRIPTION MISMATCH. A rule extended without being read would have failed loudly on a correct page.Root pages take rule 7 and nothing else: no banner rules (they declare no page type), no heading qualification (attributing a chunk to the site root is circular), and they are excluded from the uniqueness corpus as well as its reporting, so no page can be reported as colliding with one that is exempt.
--fixis narrowed the same way — all three repairs are no-ops on the README today, but by accident, and an accident is not a boundary.Red-proof
The extractor was called directly first, because rule 7 has already been green on 142 pages while reading the wrong input on twenty of them.
"Documentation for the Brighter and Darker projects."— the real sentenceDESCRIPTION MISMATCH, exit 1DESCRIPTION UNREADABLE, exit 1DESCRIPTION MISMATCH, exit 1That last row is worth keeping: deleting the sentence does not give
SUMMARY MISSING— the next paragraph becomes the summary and mismatches instead. The file was copied aside and restored byte-identically, asserted both ways.pagelint.py's corpus is 143 pages from this commit. Every figure in the spec quoting 142 refers tocontents/alone; Task 11.4 counts both.Gates
linkcheck 144 files, clean; pagelint 0 errors / 791 warnings / 143 pages;
--check-shape0;--check-redirects0 at 77 entries;--changed origin/master0 at 3 files, 20 hunks, 0 documentation pages, 0 code blocks strict.🤖 Generated with Claude Code