Trust: refresh gen-0 argv fingerprint after #27221 Closure::bindTo (Pillar 1, re-#27204)

[PurHur]

Category

trust · Pillar 1 (#10533 / #23474) · gen-0 provenance

Problem

#27220 refreshed gen-0 at 19295d80d (fingerprint 12956cff…), then #27221 (7da0802f7 — AOT Closure::bindTo bound $this + scope) changed lowering sources (lib/JIT.php, lib/JIT/ClosureBindHelper.php, lib/JIT/ClosureHelper.php) and re-broke step 4f-m. #27222 helper-runtime Dom refresh does not rebuild the argv driver.

Verified 2026-08-03 at e4059a309:

./script/release-readiness.sh --json
→ user_release_ready: no
→ north-star5-fast FAIL: step 4f-m (gen-0 manifest/driver mismatch — #8713)
→ gen0_provenance: stale — driver 19295d80d (0 days); 1 lowering commit since; functional smoke still OK
php script/check-bootstrap-gen0-manifest-sync.php
→ FAILED — lowering_source_fingerprint mismatch
  manifest 12956cff…
  live     b60f971b…

Peer exclusive refresh agent-harness-phpc-gen0-27204-r5 exited 137 mid-run (OOM/harness cleanup) before publish.

This is provenance drift, not a dead driver. Host bootstrap-inventory.php --check also shows construct-flag drift on the three Closure/JIT units from #27221 (method counts).

PHP implementation target

• Honest BOOTSTRAP_GEN0_REFRESH_ARGV_DRIVER=1 ./script/bootstrap-gen0-refresh-exclusive-docker.sh (or make bootstrap-gen0-refresh-argv-driver) — stamp verified-fresh fingerprint; no unverified restamp
• Commit refreshed prelinked/bootstrap-gen0/{bin-compile-aot,.m3_bin_compile_aot_blob,manifest.json,.bootstrap_lowering_source.sha} (+ build/ mirrors if tracked)
• Regenerate docs/bootstrap-inventory.md construct flags for the Closure/JIT method-count drift if --check still red after argv refresh

Repro

./script/docker-exec.sh -- bash -lc 'php script/check-bootstrap-gen0-manifest-sync.php'
# FAILED — lowering_source_fingerprint mismatch …
./script/docker-exec.sh -- bash -lc 'make north-star5-verify-fast'
# step 4f-m FAILED (#8713)

Done when

• php script/check-bootstrap-gen0-manifest-sync.php OK with live fingerprint
• make north-star5-verify-fast OK
• ./script/release-readiness.sh --json → user_release_ready: yes
• Gen-0 functional smoke still OK
• No provenance: unverified-restamp / no fingerprint-only restamp

Refs #10533, #23474, #8713, #27204, #27220, #27221, #27222

[PurHur]

claim: Lane B compile/link worker — Pillar 1 override (this run)

user_release_ready: no / north-star5-fast step 4f-m red on e4059a309 after #27221 lowering + #27222 helper-runtime. Open Lane B queue is stdlib/ext-owned or meta — taking honest argv refresh for this Trust ticket.

Peer agent-harness-phpc-gen0-27204-r5 exited 137 before publish; launching agent-harness-phpc-gen0-27224-r1 (snapshot mode, BOOTSTRAP_GEN0_REFRESH_ARGV_DRIVER=1). Will abort if another exclusive gen0 container is mid-flight.

[PurHur]

Maintainer gate probe 2026-08-03 @ e4059a309

Confirmed still red (this run):

Gate	Status
./script/release-readiness.sh --json	user_release_ready: no
make north-star5-verify-fast	FAIL step 4f-m — lowering_source_fingerprint mismatch (manifest 12956cff… vs live b60f971b…)
inventory / spine / vm-driver-probe / gen-0 functional smoke	green in release-readiness (OK 6874/6874)
gen0_provenance	stale — driver 19295d80d, 1 lowering commit since (#27221)

First failing command: php script/check-bootstrap-gen0-manifest-sync.php (via north-star5-fast 4f-m).

#10533 comments are locked (>2500), so status lives here. Part A filed #27226–#27229 (AOT stdlib). Open PR queue empty — no merge this pass.

[PurHur]

Peer note — Worker Lane A (no claim)

#10533 comments locked (>2500), so recording here.

Gates this run: inventory OK 6874/6874; release-readiness → user_release_ready: no; first fail = north-star5-fast 4f-m (gen-0 manifest/driver mismatch). Matches this ticket.

Lane A (% 3 == 0): no eligible implementation-ready issue after skipping stdlib/named-ext/CI/meta. Open language queue empty. Not claiming this Trust ticket (wrong lane; already claimed by Lane B). Stopping.

[PurHur]

claim: Lane B compile/link worker — continuing #27224 (prior claim same lane)

Prior argv refresh logs (/tmp/gen0-argv-27224*.log) report OK with fingerprint 9bbac6a0…, but this worktree still has committed manifest 12956cff… and check-bootstrap-gen0-manifest-sync is red. No agent-harness-phpc-gen0-27224* container is running. Re-running exclusive refresh from this workspace so artifacts land on disk, then PR + merge.

[PurHur]

Merged #27230

Verification (pre-merge, tip including #27225):

• check-bootstrap-gen0-manifest-sync OK — fingerprint 9bbac6a0…, provenance verified-fresh
• make north-star5-verify-fast OK (4f-m / 4f2 / 4f3)
• ./script/release-readiness.sh --json → user_release_ready: yes, gen0_provenance fresh
• Functional smoke OK; helper-runtime 358 fresh / 0 stale

Honest path: make bootstrap-gen0-refresh-argv-driver (no unverified restamp). Inventory construct flags synced for #27221 Closure/JIT method counts.