TEMPORARY — AC2 isolation differential for #1323, do not merge #1341

Closed

engineer wants to merge 3 commits from tmp/1323-ac2-isolation-differential into main

pull from: tmp/1323-ac2-isolation-differential

merge into: frankenbit:main

frankenbit:main

frankenbit:release-prep/rolling

frankenbit:sentry/1465-fragment-contexts

frankenbit:rigger/1463-split-readme-pin-check

frankenbit:i/1426-mirror-propagates-metadata

frankenbit:i/1401-readme-asserts-mirror-state

frankenbit:i/336-sha-pin-propagation

frankenbit:sentry/1342-approval-whitelist-presence

Conversation 0 Commits 3 Files changed 2 +7 -79

engineer commented 2026-09-06 16:03:18 +02:00

Owner

Copy link

🔴 DO NOT MERGE. DO NOT REVIEW. Throwaway PR existing only to run CI, per the disposable-fixture pattern. I close it myself when the two cycles are recorded.

#1323 AC2 requires that a gate deliberately made to leave state behind reddens, and that it is the ISOLATION assertion that fires rather than a downstream gate failing for its own reasons. This forge exposes no job log, so I cannot read which step failed — the discrimination has to come from the experiment's shape instead.

cycle A   a PASSING gate leaks zz-isolation-probe.tmp, tree guard PRESENT   expect RED
cycle B   the same leak, tree guard REMOVED                                 expect GREEN

If B is green, no downstream gate failed because of the leak — so A's red is attributable to the isolation assertion alone. The leaked name is unique and read by nothing, and the gate still exits 0, so all nine outcomes stay success and the guard's own abstain path cannot be what fires.

🔴 **DO NOT MERGE. DO NOT REVIEW.** Throwaway PR existing only to run CI, per the disposable-fixture pattern. I close it myself when the two cycles are recorded. `#1323` AC2 requires that a gate deliberately made to leave state behind reddens, **and that it is the ISOLATION assertion that fires rather than a downstream gate failing for its own reasons.** This forge exposes no job log, so I cannot read which step failed — the discrimination has to come from the experiment's shape instead. ``` cycle A a PASSING gate leaks zz-isolation-probe.tmp, tree guard PRESENT expect RED cycle B the same leak, tree guard REMOVED expect GREEN ``` **If B is green, no downstream gate failed because of the leak — so A's red is attributable to the isolation assertion alone.** The leaked name is unique and read by nothing, and the gate still exits 0, so all nine outcomes stay `success` and the guard's own abstain path cannot be what fires.

engineer added 1 commit 2026-09-06 16:03:18 +02:00

TEMPORARY AC2 PROBE: a passing gate leaves a file behind (#1323) ... 427d350f89

Cycle A of a two-cycle differential. Gate g9 still exits 0; it just leaves
zz-isolation-probe.tmp in the shared workspace. Nothing reads that name, so
no downstream gate can fail because of it.

Not for merge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMmaXmMhZdAAnttWBS6zqa

engineer added 1 commit 2026-09-06 16:04:52 +02:00

TEMPORARY: add a fragment so no gate fails for its own reasons (#1323) ... a17c4a586d

The first cycle-A run had a confound: no changelog fragment, so the
fragment gate inside the consolidated job could have been what reddened
it. That is exactly the 'a downstream gate failing for its own reasons'
case AC2 names, and it would have made the differential prove nothing.

Not for merge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMmaXmMhZdAAnttWBS6zqa

engineer added 1 commit 2026-09-06 16:07:15 +02:00

TEMPORARY cycle B: remove the tree guard AND its attest wiring (#1323) ... d8650dba59

Same leak, guard gone. If B is GREEN then no downstream gate failed
because of the leaked file, so cycle A's red is attributable to the
isolation assertion alone.

⚠️ The attest wiring must go WITH the guard. attest grades
steps.treeguard.outcome, and with the step removed that outcome is
EMPTY — which attest correctly treats as could-not-grade and refuses.
Leaving it would have made cycle B red for a reason that has nothing to
do with isolation, and the differential would have proved nothing.

Not for merge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMmaXmMhZdAAnttWBS6zqa

engineer closed this pull request 2026-09-06 16:10:57 +02:00

bosun referenced this pull request 2026-09-06 16:12:41 +02:00

test(ci): the nine consolidated gates share one checkout — isolation is audited, not enforced #1323

Some checks are pending

Hide all checks

base-divergence-check / check (pull_request) Failing after 7s

Details

prep-order-check / check (pull_request) Successful in 6s

Required

Details

register-check / register-drift check (pull_request) Successful in 7s

Required

Details

fork-pr-approval-notice / explain fork workflow approval (pull_request_target) Successful in 25s

Details

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

Required

Details

tests / workflow-schema (pull_request) Successful in 4s

Required

Details

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

Required

Details

gitea-twin-check / check (pull_request) Successful in 31s

Required

Details

tests / dated-examples (pull_request) Successful in 4s

Required

Details

toolkit-self-gates / toolkit-self gates (PR's own rt) (pull_request) Successful in 7s

Required

Details

workflow-parse-check / toolkit-self parse guard and controls (pull_request) Successful in 5s

Required

Details

changelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 52s

Required

Details

ac-closure-check / ac-closure check (pull_request) Successful in 52s

Required

Details

changelog-body-check / check (pull_request) Successful in 0s

Required

Details

ac-closure-check / check (pull_request) Successful in 0s

Required

Details

workflow-parse-check / workflow parse and schema (pull_request) Successful in 5s

Required

Details

workflow-parse-check / check (pull_request) Successful in 0s

Required

Details

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

Required

Details

fragment-check / changelog fragment-kind (pull_request) Successful in 57s

Details

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

Required

Details

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

Required

Details

tests / shellcheck (pull_request) Successful in 31s

Required

Details

tests / contract-paths (pull_request) Successful in 37s

Required

Details

go-ci / lint + build + test (pull_request) Successful in 1m17s

Required

Details

go-ci / page landing-tree failure (pull_request) Has been skipped

Details

tests / bats (pull_request) Failing after 1m17s

Required

Details

fragment-check / coverage (pull_request)

Required

fragment-check / density (pull_request)

Required

readme-pin-check / digest (pull_request)

Required

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bump

major

Override the cut bump to MAJOR (release-toolkit#107)

  

bump

minor

Override the cut bump to MINOR (release-toolkit#107)

  

bump

patch

Override the cut bump to PATCH (release-toolkit#107)

  

kind/bug

Something is broken

  

kind/chore

Maintenance, tooling, refactor

  

kind/docs

Documentation work

  

kind/feature

New feature or capability

  

priority/critical

Critical: must be addressed immediately

  

priority/high

Important, should be addressed soon

  

priority/low

Low priority, address when convenient

  

priority/medium

Normal priority

  

size/L

Large: significant feature, ~6-16h

  

size/M

Medium: moderate feature, ~2-6h

  

size/S

Small: simple change, ~1-2h

  

size/XL

Extra large: major feature or refactor, 16h+

No labels

bump

major

bump

minor

bump

patch

kind/bug

kind/chore

kind/docs

kind/feature

priority/critical

priority/high

priority/low

priority/medium

size/L

size/M

size/S

size/XL

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

frankenbit/release-toolkit!1341

No description provided.