the vendored corpus pin is 6 commits behind the marketplace's merged main, so the published internals recipes are a stale projection #195

Activity

1. aitrawog commented on Oct 28, 2026

   

   aitrawog

   on Oct 28, 2026

   Last edited by aitrawog

   ContributorAuthor

   More actions

   CLAIM — the consumer leg of the corpus's merged main.

   Taking this leg: advance this repo's marketplace pin from 835d0998 to the corpus's merged main 99a1bb4a6f (a fast-forward, ahead=6 behind=0), and carry the regenerated pages.

   Why this leg is mine to take. The corpus's ## Consumers table names two consumers: opencharly/opencharly (landed as opencharly/opencharly#762, whose pin is now 99a1bb4a6f) and opencharly/docs — this repo. The producer leg (opencharly/marketplace#585) is merged and tagged, so the order allows the consumer leg now. No other open PR or issue in this repo touches the corpus pin, and no other session's branch, worktree or file is in scope.

   The plan, in the order it happens.

   1. branch feat/corpus-pin-corpus99 off this repo's fresh origin/main, in a session worktree;
   2. advance the marketplace submodule through the submodule's own remote-tracking path (git submodule update --remote marketplace — the pin follows the branch .gitmodules declares), never a hand-set gitlink;
   3. regenerate the generated half with the workflow's OWN pinned inputs — the pinned charly at bafd8dbc, the pinned umbrella at e631aacf, the pinned plugin-docs at v2026.289.0814 built from its own tag, and the corpus wiring candy written by .github/docs-corpus/build_wiring.py — and carry the resulting pages;
   4. run this repo's own gate on the committed tree: the regeneration, the drift check, the corpus-currency report and the Astro build;
   5. open the PR, read every comment and the validator's full report, one commit per round; close this issue by hand with a RESOLVED record when it lands.

   STATUS follows at each milestone.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0
   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
2. aitrawog

   self-assigned this

   on Oct 28, 2026
3. aitrawog commented on Oct 28, 2026

   

   aitrawog

   on Oct 28, 2026

   Last edited by aitrawog

   ContributorAuthor

   More actions

   STATUS — the pin is advanced in the session worktree; the regeneration is running against the workflow's own pinned inputs.

   Done so far.

   • The worktree is up: .worktrees/corpus99/docs, a clone of this repo alone, on feat/corpus-pin-corpus99, branched from this repo's fresh origin/main (39203ee).
   • The pin is advanced through the submodule's own remote-tracking path — git submodule update --remote marketplace — and the index now carries 160000 99a1bb4a6f10112f67e3ddd73d3e86b3f6bc3417 marketplace (the corpus's merged main, the tag-on-merge record commit for chore(refs): advance the umbrella pin to v2026.301.0144 and regenerate the corpus (#583) marketplace#585).
   • The generation inputs are materialized exactly as .github/workflows/deploy.yml pins them, measured from the workflow file itself: the charly source at bafd8dbc3110904872831998fb4caa701cc2990c (with its box/* submodules at the commits that checkout records), the umbrella at e631aacf32df4e26a66f2cb6a75fc9e85e212399, and the plugin-docs CLI built from v2026.289.0814 (e9d461d9cfb9a82d6e8042017b9660baefcc16b8) in this session — not a shared install.
   • The dependency-advisory gate is green on this tree: check-dependency-advisories: OK (no known advisory in the production tree or the dev tree).

   The currency report, before the bump — this is the only thing in the repo that can see a corpus that trails its own merged main (the PINNED corpus regenerates its own old pages perfectly, so the drift gate is blind to it):

   corpus pin: 835d099845cd51ac90f6677179d750fbb384fc83 is behind — 6 commit(s) behind the corpus's merged main; an advance available NOW (a pin-bump PR in this repo) (merged main: 99a1bb4a6f10112f67e3ddd73d3e86b3f6bc3417)
   

   Next. The regeneration is running now (it resolves the corpus's carriers and re-projects the recipes), then the pages are carried in one commit, the gate runs on the committed tree — regeneration, drift check, currency report, Astro build — and the PR opens. Next update when the PR is open.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0
   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
4. aitrawog commented on Oct 28, 2026

   

   aitrawog

   on Oct 28, 2026

   ContributorAuthor

   More actions

   STATUS — the corpus leg is open for review: the pin is advanced, the pages are carried, and the gate is green on the committed tree.

   Done.

   • The PR is open against this repo: docs(corpus): advance the vendored corpus pin to the corpus that carries the pathspec rule, and regenerate #197, branch feat/corpus-pin-corpus99, head 99161e37b27a98244953431f3ddc2d221a2a4c79, branched from this repo's fresh origin/main (39203ee).
   • The pin moved through the submodule's own remote-tracking path — git submodule update --remote marketplace — and the index carries 160000 99a1bb4a6f10112f67e3ddd73d3e86b3f6bc3417 marketplace: the corpus's merged main tip, the tag-on-merge record commit for chore(refs): advance the umbrella pin to v2026.301.0144 and regenerate the corpus (#583) marketplace#585, and the same commit the umbrella's own corpus pin now holds.
   • The six pages the pin projects are carried in the same commit, and no page is hand-edited — they are the generator's output for the advanced pin.
   • The gate is green on the committed tree: the regeneration is a no-op, the drift gate reports content: committed tree matches the pinned inputs (regeneration is a no-op), the corpus-currency report changed from behind — 6 commit(s) to cur, the drift gate's own test runs 6 tests OK, the dependency-advisory gate is OK, and the Astro build built 1699 pages. Every step exited 0, zero warnings.

   The claim, measured on both sides. The rule's literal form — the string the new guidance tells a reader to write — is 0 occurrences in the whole published recipes/ tree this repo served before, and 0 on the live site; it is present in the pages the site serves after, because this repo's pin is what decides which projection is served.

   Three findings filed or fed, none blocking this leg (each is in the PR's ## Filed issues):

   • the site's own charly and umbrella pins are 91 and 373 commits behind their merged mains, and nothing reports it #196 — the site's own other two pins are far behind their remotes (charly 91 commits, the umbrella 373) and nothing reports it: this repo's currency report watches the corpus only. Filed and claimed; it is its own cutover.
   • deploy drift gate red on main: regeneration drops plugin-docs/pipeline/review — catalog membership is undeclared and the gate is not required #143 (item 3) — the drift gate is still not a required check on main (the org ruleset requires validate / validate and nothing else). Today's evidence is added to that thread, together with the measurement that the symptom it opened with — the regeneration dropping plugin-docs/plugin-pipeline/plugin-review — no longer reproduces.
   • the repo does not declare which npm resolves its lockfile, and the two npm versions in play disagree — a nested overrides entry breaks the CI's npm ci #190 — the npm that resolves the lockfile is undeclared, and this leg's local build ran npm 11.20.0 while CI runs npm 10.9.9. The measurement is added to that thread, and the versions this build ran under are in the PR's How tested.

   Next. The validator's verdict, read in full, and every finding it raises fixed in one commit per round. Next update when the verdict lands, or when the round's fixes are pushed.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0
   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
5. aitrawog commented on Oct 28, 2026

   

   aitrawog

   on Oct 28, 2026

   ContributorAuthor

   More actions

   RESOLVED — the corpus pin is advanced and the site publishes the pathspec rule's remedy.

   Landed. #197 — squash 98a5f6cbfb4d659d28c1ec15804f70f6b1d75783, merged 2026-10-28T04:10:09Z, CHANGELOG 2026.301.0410.

   What the issue asked for. The issue named the defect exactly: the marketplace pin was 6 commits behind the corpus's merged main, so every published internals recipe was a projection of a corpus the org had already replaced, and the site's own drift gate could not see it — the pinned corpus regenerates its own old pages perfectly, so a stale pin is invisible to it.

   What landed. The pin moved to 99a1bb4a6f10112f67e3ddd73d3e86b3f6bc3417 — the corpus's merged main tip, a MERGED ref, advanced through the submodule's own remote-tracking path (git submodule update --remote marketplace, the path .gitmodules' branch = main declares), never a hand-set gitlink. The six regenerated recipes/internals/git-workflow* pages carry the corpus's advance, and the corpus's own consumer report now reads this repo as cur:

   $ bash scripts/consumer-currency.sh
   consumer-currency: 2 consumer(s) read, 0 behind, 0 not-on-the-served-line, 0 undecidable, 0 unreadable (merged main: 99a1bb4)
     opencharly/docs  marketplace  99a1bb4  cur — at the corpus's merged main

   The claim, measured at both ends. The rule's literal form — the string the new guidance tells a reader to write — was absent from the pages this repo served before the change and is present in four of the six regenerated pages after it, with a calibration arm (the retired form's own line still returned by the same key at the old pin, and by nothing at the new one), so the empty "before" is evidence rather than a coincidence.

   The gate, on the committed tree. The regeneration is a no-op against the committed tree (content: committed tree matches the pinned inputs), the corpus-currency report is cur, the drift test runs 6 tests OK, the dependency-advisory gate is clean, and the Astro build assembles 1699 pages — every step exit 0, zero warnings.

   One correction to the record, in full on the PR. The validator's PASS armed native auto-merge 36 seconds before the squash landed, so a body edit carrying the fix for its non-blocking observation could not reach the server. The observation is confirmed and fixed in the derivation; the corrected per-file table and the full RCA are on #197 (comment 6460499537). The landed CHANGELOG/2026.301.0410.md entry is not edited — a merged changelog entry is immutable by the org's own rule — and the change itself, the pin and the pages are unaffected.

   Still open, filed, and separable — not closed by this issue. #196 (the site's own charly and umbrella pins are 91 and 373 commits behind, and the repo's currency report watches only the corpus), #143 (the drift gate is still not a required check on main) and #190 (the repo declares its node but not the npm that resolves its lockfile). Each carries its own measurement and its own owner.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0
   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
6. aitrawog

   closed this as completedon Oct 28, 2026