Repository navigation
Claude/coderoast claude md malf p80u1w - #17
Merged
Merged
Conversation
…LAW-n addresses The superproject's flaw register minted registry-form addresses on 2026-09-16. That pass repointed the superproject doc tier and the DF/LF citations; its F<n> half was scoped to the superproject and said so. This closes it here. Every site was read before it was rewritten. The MetaLog entries kept their numbers, so these are prefix changes that cannot mis-map. Deliberately untouched and distinguished by reading, not by pattern: the ML F1 score, float16 and hex literals, flake8 suppressions, and the MetaLog specification's own F2(b) clause — a public standard's numbering, in a different number space. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…module, not the deleted script .github/workflows/lint.yml line 16 said the lint-siblings roster is held to packages.yml by the superproject's "pin_coherence.py INV-13"; it now names the pin_coherence check module's INV-13, re-wrapped to two lines. The superproject's scripts/pin_coherence.py was deleted on 2026-09-17 (coderoast commit b60d217c) when its check became the pin_coherence check module (scripts/pharos/checks/pin_coherence.py, run as `./pharos check --module pin_coherence`) and its producer verbs became scripts/version_line.py. Comment only: no step, input, ref or shell line changes, and every workflow in this repository still loads as YAML (checked with PyYAML). The same repoint lands in the superproject's compatibility_matrix.md (coderoast commit b2e7602f) and in the four other sibling repositories whose workflow comments named the script. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…lock_lint.py names the wallclock check module
The superproject deleted `scripts/wallclock_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2:
every gate becomes a `pharos check` module; the `source` family). A sweep of every live surface
for the old spelling found one present-tense sentence in this ledger — the comment-token census
line saying which live superproject gates READ the `DETERMINISM-ALLOW` token. It now names the
`wallclock` check module (spelled `./pharos check --module wallclock` from the superproject
root). The recorded scope fact five lines down ("`wallclock_lint.py`'s SCOPE covers insight-canon
and insight-eidos only") is a dated measurement and keeps its wording; insight-metalog joined
that scope on 2026-09-09, and the module walks 17 of its units today.
`scripts/random_determinism_lint.py` on the same line is repointed when that gate migrates.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…py names the json_write_closure check module The superproject deleted `scripts/json_write_closure_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). A sweep of every live surface for the old spelling found one present-tense sentence in this ledger — the Q1 row saying the JSON write-closure rule "is mechanically gated by" the script, run in lint.yml's pin-coherence job. It now names the `json_write_closure` check module (spelled `./pharos check --module json_write_closure` from the superproject root) and keeps "(`scripts/ json_write_closure_lint.py` then)" so the dated finding still reads; the job, the derived-list claim and the exit-2-on-empty-derivation claim are unchanged and still true of the module. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…m_determinism_lint.py names the random_determinism check module
The superproject deleted `scripts/random_determinism_lint.py` on 2026-09-17 (DN-108.D2, plan
row P1.2: every gate becomes a `pharos check` module; the `source` family). The comment-token
census line in this ledger saying which live superproject gates READ the `DETERMINISM-ALLOW`
token now names the `wallclock` and `random_determinism` check modules (spelled `./pharos check
--module random_determinism` from the superproject root). The recorded scope fact a few lines
down ("`random_determinism_lint.py`'s SCOPE does name insight-metalog (6 module interface
units)") is a dated measurement and keeps its wording. `scripts/log_seat_routing_lint.py` on
the same line is repointed when that gate migrates.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…eat_routing_lint.py names the log_seat_routing check module The superproject deleted `scripts/log_seat_routing_lint.py` on 2026-09-17 (DN-108.D2, plan row P1.2: every gate becomes a `pharos check` module; the `source` family). The comment-token census line in this ledger saying which live superproject gates read their markers now names the `log_seat_routing` check module (spelled `./pharos check --module log_seat_routing` from the superproject root) beside the `wallclock` and `random_determinism` modules already named there. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
…ove onto da2abf63 Layer 3 (the last) of the malf-toolchain re-pin that unblocks the next CodeRoast release tag. THE DEFECT. The workspace pinned malf-toolchain at b5e15eee5e2cc9a2709309850f845b28ba8d9e58. The `malf` driver at that revision does `local pin="$MALF_WORKSPACE_ROOT/scripts/pin_coherence.py"` followed by `[[ -f "$pin" ]] || return 1`, in both `cut-verify` and `bump`. That superproject script no longer exists: the check became the Pharos check module `scripts/pharos/checks/pin_coherence.py` and its two producer verbs (`released` and `bump X.Y.Z`) moved to `scripts/version_line.py`. So the next `v*` tag would run `.github/workflows/cut-verify.yml`, which checks malf-toolchain out at the pinned revision and runs that checkout's `malf cut-verify`, which exits 1 on the missing file -- and every release job declaring `needs: [cut-verify, ...]` would be skipped. Measured: `git show b5e15eee:malf | grep -c pin_coherence` returns 6; `git show da2abf63:malf | grep -c pin_coherence` returns 2, and both survivors are correct (one comment and one `python3 "$pharos" check --module pin_coherence` invocation). THE TARGET IS NOT THE TOOLCHAIN'S main. `origin/main` is b62485cde9e1d5438b2c4ebabe86189a0ea7f028 and its count is also 6 -- main does not carry the fix. The target is da2abf639f64e1c1bca382aa7a973e9cc2f00412, the head of malf-toolchain's `claude/coderoast-claude-md-malf-p80u1w` branch, which is a strict fast-forward of main (7 commits ahead, 0 behind). That branch must be merged, not squashed, or every reference below would name a commit that no longer exists. WHY da2abf63 IS A LEGAL TARGET FOR EXTERNAL REFERENCES. The re-pin is layered because a commit may only pin edges whose TARGET it does not touch. Layer 1 (390108f5) moved malf-toolchain's 9 action->action refs onto the content head 5081176 and touched only 6 files under `.github/actions/`, none of them a target of those refs. Layer 2 (da2abf63) moved the 10 workflow->action refs onto layer 1 and touched only `.github/workflows/`, so all 10 target actions have identical bytes at layer 1 and at da2abf63. This layer touches no malf-toolchain file at all, so every workflow and every action a consumer executes has, at da2abf63, exactly the bytes it has at the revision this workspace pins. INV-17 (d) verifies that chain independently: each pinned SHA must be an ancestor of its successor differing by nothing but `uses:` lines. IN THIS REPOSITORY. 10 references move from b5e15eee to da2abf63: 8 `uses:` step(s) and 2 `actions/checkout` refs. Verified: every changed line is either a `uses: CodeRoasted/malf-toolchain/...@<40-hex>` step or the `ref:` of an `actions/checkout` whose `repository:` is `CodeRoasted/malf-toolchain`; every changed file parses under `python3 -c "import yaml; yaml.safe_load(open(f))"`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgF1dGH16hPwX7aaaKguWw
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
2 participants
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.
No description provided.