chore(workflows): self-bootstrap release.yml + manifest-check.yml @v0.11.1-rc.2 #166

Closed

quartermaster wants to merge 1 commit from i/re-pin-v0.11.1-rc.2 into main

quartermaster commented

2026-06-27 02:59:35 +02:00

Owner

Summary

In-cycle re-pin following PR #164 (rc-tag lifecycle auto-prune) per AGENTS.md section 2 mechanism-of-touch.

Changes

.forgejo/workflows/release.yml: _release.yml@v0.11.1-rc.1 → @v0.11.1-rc.2 + toolkit_ref: v0.11.1-rc.2
.forgejo/workflows/manifest-check.yml: _manifest-check.yml@v0.11.1-rc.1 → @v0.11.1-rc.2 + toolkit_ref: v0.11.1-rc.2

(Both wrappers / all 4 surfaces updated in lockstep per Surveyor f0a7 — the doubling discipline #163 is being filed to enforce structurally.)

Verification

$ ./scripts/check-self-bootstrap.sh
[check-self-bootstrap] pinned toolkit_ref: v0.11.1-rc.2
[check-self-bootstrap] OK: all compose-scripts at HEAD match pinned ref (v0.11.1-rc.2)

grep -rn 'v0.11.1-rc.1' .forgejo/workflows/ → clean.

Activation race

The rolling PR release-prep/rolling was already opened by release-decide on the #164 merge push (the workflow fired at the OLD pinned ref v0.11.1-rc.1 immediately). Whether the v0.11.1 cut self-prunes its own rc tags depends on the ordering of this re-pin vs the rolling-PR merge:

This PR lands first → release-decide REFRESHES the rolling PR at NEW code → rolling PR merge fires cut at v0.11.1-rc.2 (NEW code with auto-prune) → cut self-prunes v0.11.1-rc.{1,2} ✅
Rolling PR merges first → cut runs at v0.11.1-rc.1 (OLD code) → no auto-prune at v0.11.1; v0.11.1-rc.{1,2} linger as abandoned-by-skip class until a manual cleanup

Sequencing here goes re-pin first to land the auto-prune at the v0.11.1 cut.

Tag

v0.11.1-rc.2 tagged at 9327148 (Sprint 2 substrate PR #164 merge SHA) + pushed before this PR.

Next on merge

Merge this re-pin PR → push:main fires release.yml @v0.11.1-rc.2 (NEW code)
release-decide.sh walks log → finds the existing rolling PR for v0.11.1 → REFRESHES it (mode=update + rolling PR exists semantic)
Refreshed rolling PR awaits Surveyor verify-at-source per AGENTS.md section 6
On rolling PR merge → cut path runs at NEW code → auto-prune fires for v0.11.1-rc.*
#139 empirical close: does the chore(manifest) post-cut push trigger a workflow run? (Surveyor watch-target)

Refs

AGENTS.md section 2 (mechanism-of-touch) + section 2.4 (rc-tag lifecycle)
Surveyor 6802 (activation-lag framing — re-pin-first sequencing follows from it)
Sister substrate PR: #164

## Summary In-cycle re-pin following PR #164 (rc-tag lifecycle auto-prune) per AGENTS.md section 2 mechanism-of-touch. ## Changes - `.forgejo/workflows/release.yml`: `_release.yml@v0.11.1-rc.1` → `@v0.11.1-rc.2` + `toolkit_ref: v0.11.1-rc.2` - `.forgejo/workflows/manifest-check.yml`: `_manifest-check.yml@v0.11.1-rc.1` → `@v0.11.1-rc.2` + `toolkit_ref: v0.11.1-rc.2` (Both wrappers / all 4 surfaces updated in lockstep per Surveyor f0a7 — the doubling discipline #163 is being filed to enforce structurally.) ## Verification ``` $ ./scripts/check-self-bootstrap.sh [check-self-bootstrap] pinned toolkit_ref: v0.11.1-rc.2 [check-self-bootstrap] OK: all compose-scripts at HEAD match pinned ref (v0.11.1-rc.2) ``` `grep -rn 'v0.11.1-rc.1' .forgejo/workflows/` → clean. ## Activation race The rolling PR `release-prep/rolling` was already opened by release-decide on the `#164` merge push (the workflow fired at the OLD pinned ref `v0.11.1-rc.1` immediately). Whether the v0.11.1 cut self-prunes its own rc tags depends on the ordering of this re-pin vs the rolling-PR merge: - **This PR lands first** → release-decide REFRESHES the rolling PR at NEW code → rolling PR merge fires cut at v0.11.1-rc.2 (NEW code with auto-prune) → cut self-prunes v0.11.1-rc.{1,2} ✅ - **Rolling PR merges first** → cut runs at v0.11.1-rc.1 (OLD code) → no auto-prune at v0.11.1; v0.11.1-rc.{1,2} linger as abandoned-by-skip class until a manual cleanup Sequencing here goes **re-pin first** to land the auto-prune at the v0.11.1 cut. ## Tag `v0.11.1-rc.2` tagged at `9327148` (Sprint 2 substrate PR #164 merge SHA) + pushed before this PR. ## Next on merge 1. Merge this re-pin PR → push:main fires `release.yml @v0.11.1-rc.2` (NEW code) 2. release-decide.sh walks log → finds the existing rolling PR for v0.11.1 → REFRESHES it (mode=update + rolling PR exists semantic) 3. Refreshed rolling PR awaits Surveyor verify-at-source per AGENTS.md section 6 4. On rolling PR merge → cut path runs at NEW code → auto-prune fires for `v0.11.1-rc.*` 5. #139 empirical close: does the chore(manifest) post-cut push trigger a workflow run? (Surveyor watch-target) ## Refs - AGENTS.md section 2 (mechanism-of-touch) + section 2.4 (rc-tag lifecycle) - Surveyor 6802 (activation-lag framing — re-pin-first sequencing follows from it) - Sister substrate PR: #164

quartermaster added 1 commit

2026-06-27 02:59:35 +02:00

chore(workflows): self-bootstrap release.yml + manifest-check.yml @v0.11.1-rc.2

check-self-bootstrap / check (pull_request) Successful in 3s

Details

manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s

Details

manifest-check / check (pull_request) Successful in 0s

Details

1e1311c452

In-cycle re-pin following #164 (rc-tag lifecycle auto-prune) per
AGENTS.md section 2 mechanism-of-touch.

Activation note (per Surveyor 6802): the auto-prune feature added
in #164 takes effect from this ref forward. Whether the v0.11.1
cut self-prunes its own rc tags depends on whether this re-pin
lands BEFORE the existing rolling PR (release-prep/rolling, opened
when #164 merged at the old v0.11.1-rc.1 ref) merges.

- Re-pin lands first -> rolling PR refreshes at NEW code; cut path
  uses NEW code; auto-prune fires + deletes v0.11.1-rc.{1,2}
- Rolling PR merges first -> cut runs at OLD code (v0.11.1-rc.1);
  no auto-prune; v0.11.1-rc.{1,2} linger as abandoned-by-skip

Sequencing here goes re-pin first.

Updates:
- .forgejo/workflows/release.yml: _release.yml@v0.11.1-rc.2 + toolkit_ref
- .forgejo/workflows/manifest-check.yml: _manifest-check.yml@v0.11.1-rc.2 + toolkit_ref

check-self-bootstrap.sh confirms clean post-update.

quartermaster

2026-06-27 02:59:47 +02:00