From badef0e101a97036d0350e761a85e741de549c55 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 14 Nov 2026 18:44:04 +0000 Subject: [PATCH] Say where the reference implementation is kept and log the merge of #19 MAINTAINING.md: the maintainer's reference implementation is kept in a private repository, on a branch that is never merged. The development repository that held it up to stage 15 is archived. Maintainer log 36 records the check of the merge of #19 and the copy of the reference implementation. Co-Authored-By: Claude Fable 5.2 --- MAINTAINING.md | 4 ++-- log/2026-11-14-maintainer-36.md | 24 ++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 2 deletions(-) create mode 100644 log/2026-11-14-maintainer-36.md diff --git a/MAINTAINING.md b/MAINTAINING.md index 7d20aba..950ff90 100644 --- a/MAINTAINING.md +++ b/MAINTAINING.md @@ -75,7 +75,7 @@ The squash commit on `main` is the release, identified by `version` and commit h ## Reference implementation -The maintainer computes expected results with its own implementation, kept on branch `maintainer/reference` of the private development repository and never merged. Recompute with it whenever a check, patch, `compare` or export definition changes. +The maintainer computes expected results with its own implementation, which builders never see. It is kept in a private repository, on a branch that is never merged. Up to stage 15 that was branch `maintainer/reference` of the development repository, which is archived since 2026-11-14; the implementation was copied from there, file for file. Recompute with it whenever a check, patch, `compare` or export definition changes. ## Start the next builder session @@ -91,7 +91,7 @@ Do not give builders material from any specific game or client project. ## Publication -The repository was published on 2026-10-08 as a new repository with the history of the private development repository's `main`, rewritten: the same 18 commits, authors, committers, dates and messages, without the two `Claude-Session:` lines of the first squash commit, and with one quoted example phrase in a maintainer log described instead. The rewrite dropped the commit signatures. Pull requests #1 to #17, the builder branches and the reviews stay in the development repository; the numbers in commit messages and logs refer to it. +The repository was published on 2026-10-08 as a new repository with the history of the private development repository's `main`, rewritten: the same 18 commits, authors, committers, dates and messages, without the two `Claude-Session:` lines of the first squash commit, and with one quoted example phrase in a maintainer log described instead. The rewrite dropped the commit signatures. Pull requests #1 to #17, the builder branches and the reviews stay in the development repository, which is archived since 2026-11-14; the numbers in commit messages and logs refer to it. Every later change follows the content rules of SPEC section 20 from the start: a public repository also shows every branch, the commits of every pull request (GitHub keeps them under `refs/pull/` after a branch is deleted) and the earlier versions of edited pull request descriptions and comments. diff --git a/log/2026-11-14-maintainer-36.md b/log/2026-11-14-maintainer-36.md new file mode 100644 index 0000000..258ad4f --- /dev/null +++ b/log/2026-11-14-maintainer-36.md @@ -0,0 +1,24 @@ +# 2026-11-14 · maintainer · session 36 + +After the merge of #19: the check of that merge, and where the reference implementation is kept now. + +## Merge of #19 + +- Pull request #19 was squash-merged as `9f91ab8` on `main`. The commit carries the owner's identity and a signature that GitHub verifies, its tree equals that of the branch head `d1091f9`, and its message holds no agent trace. The workflows `ci` and `publish rules` passed on the pull request, and `ci` passed on `main`. +- Pull request #20 was opened from the same branch after the merge and closed without a merge. `main` did not change, and the repository has no branch besides `main`. + +## Reference implementation + +- The development repository is archived since 2026-11-14 and takes no more commits. The owner keeps the reference implementation private, so that builders cannot read it. +- The reference implementation, the scripts that write the test data and the review scripts up to stage 15 were copied from commit `48e4237` of its branch `maintainer/reference` to a branch of another private repository, file for file: the two trees have the same hash. That branch is never merged. +- Check of the copy: its `review/compare_checks.py` (review step 2) against a build of release 0.15.0 (`71d7451`) compares 29 results, and none differs. +- `MAINTAINING.md`, Reference implementation and Publication, says so. + +## Next stage + +None is planned, as in session 35; the owner decides. + +## Checks + +- Only `MAINTAINING.md` and this log change. +- `npm run check:publish` on the branch with this pull request's title and description: 1 commit, nothing found.