Skip to content

skill: five lessons filed by position, now in the numbered base - #3268

Merged
gHashTag merged 2 commits into
masterfrom
w110-five-lessons-in-the-base
Sep 5, 2026
Merged

gHashTag merged 2 commits into
masterfrom
w110-five-lessons-in-the-base

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 5, 2026

Copy link
Copy Markdown
Owner

Finishes finding 3 of #3265 — and corrects it.

What was wrong

Five ### sub-headings were appended with cat >> SKILL.md, so each landed
under whichever numbered section happened to be last at that moment:

lands under actual topic
§571 X of Y where X can exceed Y the compiler was already saying it
§571 an assertion of absence and its region
§572 a guard that cannot run nineteen of my numbers re-measured
§572 a guard dead in one function, structural in the next
§572 a control that cannot fail

They were uncounted by tri skill claims and unvalidated by tri skill check,
and a reader following a cross-reference to §572 found three unrelated lessons
under it.

Promoted to 572–577 in file order, which required renumbering the previous
§572 to 574 so numbers still ascend with position. Nothing references it — the
other 572 hits in the tree are Wave Loop reports, a different sequence.

Correcting what I published last pass

I wrote that "every lesson I appended over the last several passes" was
misplaced, and implied about fifteen.

140 ### sub-headings exist. Five are misplaced.

The rest are genuine sub-points, written inside their parent section and on its
topic — "The prototype was right for the wrong reason" under §567 (The
prototype gave the right number…)
, "The half of a fix is not the fix" under
§571 (X of Y…) — the convention working as intended across 63 sections.

So the consequence is real but four times smaller than I stated. The claim I
got wrong was about my own working habits, which is the kind I have least
reason to check and most reason to. Same class as #3253.

Verification

check result
heading TEXTS, master vs this 676 = 676, 0 missing, 0 invented
## count 536 → 541
### count 140 → 135
diff 6 insertions, 6 deletions
tri skill check exit 0
tri skill claims 532 → 537 numbered sections
tri skill refs exit 0
cargo test -p tri --bin tri 780 passed

The ##/### deltas are equal and opposite, which is what makes the promotion
visibly a move rather than an addition.

Refs #3265

Five `###` sub-headings were appended with `cat >> SKILL.md` and landed under
whichever numbered section happened to be last at that moment -- two under 571
(`X of Y` where X can exceed Y) and three under 572 (a guard that cannot run),
none of them on those sections' topics. They were uncounted by
`tri skill claims` and unvalidated by `tri skill check`.

Promoted to 572-577 in FILE ORDER, which required renumbering the previous 572
to 574 so the numbers still ascend with position. Nothing references it: the
`572` hits elsewhere in the tree are Wave Loop reports, a different sequence.

This also corrects an overstatement I published last pass. I wrote that EVERY
lesson I appended was misplaced and implied about fifteen. Measured: 140 `###`
sub-headings exist and FIVE are misplaced. The rest are genuine sub-points,
written inside their parent section and on its topic, across 63 sections --
the convention working as intended. The claim I got wrong was about my own
working habits, which is the kind I have least reason to check.

Verified: heading TEXTS 676 = 676, zero missing, zero invented; `##` 536 -> 541
and `###` 140 -> 135, exactly the five moved; six lines changed. `skill check`
exit 0, `claims` 537, `refs` exit 0, 780 tests.

Refs #3265

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) September 5, 2026 09:50
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 09:52:58 UTC

Summary

Status Count
Total Open PRs 14
PRs with Failing Checks 14
PRs with All Checks Green 0
READY 0
FAILING 14
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=ab7505edd6ab != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-05 10:17:48 UTC

Summary

Status Count
Total Open PRs 13
PRs with Failing Checks 12
PRs with All Checks Green 1
READY 0
FAILING 12
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=ab7505edd6ab != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 26a83b4 into master Sep 5, 2026
27 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant