Skip to content

One file per standard and its debt; the train runs the browser acceptances once per batch; QR-03 takes the middle of three - #174

Merged
github-actions[bot] merged 5 commits into
mainfrom
claude/project-thread-jbqzew
Nov 16, 2026
Merged

github-actions[bot] merged 5 commits into
mainfrom
claude/project-thread-jbqzew

Conversation

@afflom

@afflom afflom commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

The train runs the browser acceptances once per batch

Since #164 the train runs the fast gates and the browser acceptances for each ready pull request in turn. The first run that took pull requests (run 43817755958) passed on a runner and took 83 minutes for two pull requests (#142 in 43 minutes, #169 in 39), and nothing merged in that time.

The train now merges every ready pull request that passes the fast gates onto main in order, then runs the browser acceptances once on that tree. If they pass, all of them are accepted. Only if they fail does it go back to main and take them one by one, fast gates and acceptances each, to find which it refuses. What is tested is still exactly the tree that merges.

The change is in the model, app/specs/pipeline/workflows/merge-train.yml.json. I ran the new loop in a scratch repository with a stubbed gate: three pull requests board, the batch fails, the one-by-one pass accepts two and refuses the one that fails, and a conflicting one is refused once.

QR-03 takes the middle of three cold starts

#164 made the labelling time the slowest of three cold starts. On shared runners that failed pull requests at random (#160: 274 against 250, with main green on the same base). The measure is now the middle of the three, so neither one lucky sample nor one slow moment of a runner decides it. The threshold is unchanged.

One file per standard and per standard's debt

Every pull request that registers a standard or changes a standard's debt edited the same two lists: standards in app/specs/standards/spec.json and app/specs/standards/debt.json. Two such pull requests conflict with each other. This is the class #164 closed for guests.

  • Standards register: each standard is app/specs/standards/register/<key>.json (70 files). spec.json keeps the comment, ungoverned and unassigned, and says "standards": {"parts": "register"}.
  • Standards debt: each standard's debt is app/specs/standards/debt/<key>.json (24 files). debt.json is gone; spec.json says "debt": {"parts": "debt", "as": "map"}.
  • These are read by the loader the product record already uses, tools/specs/record.py and its JavaScript twin record.mjs, unchanged. test/specs/record.test.mjs holds the two to the same reading for the standards record as well.
  • tools/standards/gate.py reads the register through that loader. --seed writes one debt file. On a pull request the base's debt is read per file, or from the base's debt.json where the base still has one.
  • test/page/standards.test.mjs reads the register and debt through record.mjs.
  • A generator step's each may name files (one request per file) in place of one file. generators/system's registerkey step uses it; the program itself is unchanged.
  • The standards feature text names the new places.

Standards are now read in key order, not in the order they were appended. test/standards/requirements.json and every generated output are byte-for-byte unchanged.

To register a standard now: add app/specs/standards/register/<key>.json; seed its debt with tools/standards/gate.py --seed <key>, which writes debt/<key>.json. An open pull request that touched the old lists moves its entries into those files when it next merges main.

Not in this change

Checks run on 16389a0 (merged with main 0f9d804)

  • tools/generators/run.sh --check (GN-01)
  • tools/standards/gate.py --check --base origin/main (ST-01: 379 of 1627 requirements enforced, as on main)
  • tools/handwritten/gate.py --check --base origin/main (25,524 hand-written lines, none added or grown)
  • tools/guests/gen.py check: 20 current
  • node --test test/specs/*.test.mjs: 5 pass; test/router/labels.test.mjs passes (176 against 250 here)
  • bash -n on the train's script, and the scratch-repository run above.

Not run: the new train loop on a runner; cargo test -p repo-conformance and the browser acceptances on this head.

🤖 Generated with Claude Code

https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ

The standards register, its debt and the parts debt are read as parts by
tools/specs/record (Python and JavaScript), which now reads a map by path
and a marker at any depth. A generator step's "each" may name files.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@github-actions

Copy link
Copy Markdown
Contributor

Merge train notice: the merge train merges this pull request once it is green on current main; don't enable auto-merge.


Generated by Claude Code

…hat board together

One by one only when the batch fails, to find which it refuses. A train of
several pull requests took over an hour before anything merged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@afflom afflom changed the title One file per standard, per standard's debt and per part's debt One file per standard and per part's debt; the train runs the browser acceptances once per batch Nov 16, 2026
The slowest of three failed pull requests at random on shared runners
(274 against 250 on #160, main green on the same base).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
…-jbqzew

The parts debt stays in app/specs/parts/spec.json: PT-01 is now a LexLean
program that reads it there (#142).

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@afflom afflom changed the title One file per standard and per part's debt; the train runs the browser acceptances once per batch One file per standard and its debt; the train runs the browser acceptances once per batch; QR-03 takes the middle of three Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Merge train: 16389a0: not merged, because it conflicts with main (c26b29a) and the pull requests the train takes before it. Fix it on this branch (merge main first) and the train tests it again.


Generated by Claude Code

@github-actions
github-actions Bot merged commit 7815f8e into main Nov 16, 2026
7 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Live: this change is on the published page, as main a507f8268a8fbf91964130677f068e468f1705f1.

The publish job opened the published page in a fresh Chromium and its live checks passed (PG-01, PD-01, PD-02): https://github.com/afflom/me/actions/runs/43919204957

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.

2 participants