the marketplace submodule is behind the corpus's merged main — the advance carries two authored bodies, so the site's generated pages move #209

Activity

1. aitrawog commented on Oct 29, 2026

   

   aitrawog

   on Oct 29, 2026

   ContributorAuthor

   More actions

   CLAIM — this leg.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0

   Scope. This repo's marketplace gitlink advances from 75e1d4a to the corpus's merged main (7836546e), and the site's generated half is regenerated and shipped in the SAME PR — because the advance carries two AUTHORED bodies (internals/skills/cutover-policy/SKILL.md and internals/skills/git-workflow/SKILL.md), the recipes/** pages DO move this time.

   Order. Producer-first: the corpus PR opencharly/marketplace#605 has merged and is tagged v2026.302.1434; the umbrella's consumer leg (opencharly/opencharly#806) lands first; this repo's leg follows it — the order this repo's own scripts/consumer-currency.sh names.

   Next. Worktree off fresh origin/main, bump the pin, regenerate the site's generated half, FAIL on drift, build Astro, gate with the org-wide charly/pr-validator. The PR opens on this issue.

   Next update: when the PR opens, or when blocked.

   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
2. aitrawog

   self-assigned this

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

   

   aitrawog

   on Oct 29, 2026

   ContributorAuthor

   More actions

   STATUS — the corpus-pin consumer leg is open.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0

   Head. 6f1871c54777069f4802dc69350008b57067b312 — 3 files changed, 15 insertions(+), 1 deletion(-): the marketplace gitlink 75e1d4a → f46285f9, and the two generated pages the gitlink projects (recipes/internals/cutover-policy.md +2, recipes/internals/git-workflow.md +12).

   Done. The scope was derived from the producer's own report (marketplace/scripts/consumer-currency.sh names this repo as behind), not written by hand. The regeneration at the NEW pin is a byte-exact no-op against the committed tree; the drift gate is green; the Astro build is green from a clean npm ci on the pinned node (1749 pages); the repo's script gates are green; the published bodies were proved byte-identical to the umbrella's own files at the umbrella's tag v2026.302.1338.

   Next. Read every comment and the validator's full report on this PR; fix every finding in ONE appended commit per round; land through the protected merge; then close the issue by hand and post RESOLVED.

   Next update. When the validator's verdict lands, or at the next milestone.

   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
4. github-actions

   added a commit that references this issue on Oct 29, 2026

   docs(corpus): advance the corpus submodule to the corpus that carries…

   ...

   4c875cc
5. aitrawog commented on Oct 29, 2026

   

   aitrawog

   on Oct 29, 2026

   ContributorAuthor

   More actions

   RESOLVED — this issue is closed by the merge of #210.

   Agent: charly · session ses_8efb271d-f2c0-47d3-85e3-2a1e00b11ae0

   Landed. Squash 4c875ccb54398e19eb5ae42e12c51e81387cb15d, merged 2026-10-29T18:59:34Z by the org's auto-merge, on a charly/pr-validator PASS. All four checks — validate / validate, validate / lint, validate / arm, deploy — completed success.

   What changed for this issue. This repo's marketplace gitlink advances 75e1d4a → f46285f93ab1d0e44674dff0ac9a9360e9d84980, the head opencharly/marketplace's merged main serves. The advance carries TWO AUTHORED BODIES, so the site's generated half moves with the pin: src/content/docs/recipes/internals/cutover-policy.md (+2) and src/content/docs/recipes/internals/git-workflow.md (+12) — the umbrella's own general-guidance skills, republished from the umbrella's tag v2026.302.1338 (opencharly/opencharly#805), which stated the ! subject marker's relation to a PR body's breaking-change answer. The corpus's own candy names exactly those two files as the only projections that change, and the measured diff agrees.

   The three gates, on the committed tree.

   $ tail -3 /tmp/lcn209/regen-newpin.log
   charly docs: 395 recipe pages, 196 plugin pages (205 provider words), 79 cli pages, 834 candy pages, 216 box pages (1726 generated pages cleared before regeneration)
   GENERATE_RC=0
   
   $ git status --porcelain=v1 --untracked-files=all -- src/content/docs
   (0 entries — the regeneration at the NEW pin is a byte-exact no-op against the committed tree)
   
   $ bash .github/docs-corpus/check_drift.sh
   content: committed tree matches the pinned inputs (regeneration is a no-op).
   DRIFT_RC=0
   
   $ node --version
   v26.11.1
   $ npm ci
   found 0 vulnerabilities
   NPM_CI_RC=0
   $ npm run build
   [build] 1749 page(s) built in 46.15s
   [build] Complete!
   NPM_BUILD_RC=0

   The pin sits one commit above the tag that names the merge. The corpus's tag v2026.302.1755 names the squash 0347894ded1bc355f9a846440bf5158bde9ba854, one commit BELOW the head its main serves (f46285f9), because the tag-on-merge workflow writes CHANGELOG/<CalVer>.md AFTER the tag. This repo's pin follows the SERVED HEAD, not the tag — the corpus's own scripts/consumer-currency.sh and this repo's own scripts/check_pin_currency.sh both judge a consumer's recorded pin against the corpus's merged main.

   Not folded in, and reported instead. This repo's two CI-time pins — CHARLY_PIN be7a505f476c1a5b0302d878e0b5686a2cde3e07 and UMBRELLA_PIN 1c88fcf15f8fb9dd8b2814210472a63d3a79d0e2 — are a DIFFERENT pin class with their own producers, and they were not moved here; the generation ran against exactly those pinned commits, so the shipped pages are a projection of the corpus bump alone. Their currency is reported by check_pin_currency.sh on every run (never a gate failure — the remedy for a stale pin is a regeneration PR, not a red build).

   Next update. None — this issue is closed.

   Assisted-by: Claude Code minimax/minimax-m3.1-flash:cloud (fully tested and validated)
6. aitrawog

   closed this as completedon Oct 29, 2026