Skip to content

Trust: refresh helper-runtime prelink (1 stale InfoJitHelper) — release-readiness user_release_ready=no (re-#24302) #25892

Description

@PurHur

Category

Foundation · Pillar 1 trust / helper-runtime freshness (re-#24302 / re-#25881)

Problem

./script/release-readiness.sh --json reports user_release_ready: no because check-helper-runtime-prelink.php --strict finds 1 stale committed unit (332 fresh, 0 broken):

  • ext_standard_InfoJitHelper_php (/ext/standard/InfoJitHelper.php)

Fingerprint drift follows ModuleRegistry.php edits from phantom-extension policy PRs (#25888/#25889/#25891); InfoJitHelper lists that path in deps[]. Cold checkouts skip the stale unit and re-emit live.

north-star5-verify --fast, inventory (6644/6644), spine, cold-build, and vm-driver-probe are green; only the prelink freshness gate is red. gen-0 provenance is a separate stale warning (not this ticket).

Repro

./script/docker-exec.sh -- bash -lc 'source script/php-env.sh && php script/check-helper-runtime-prelink.php --strict'
# expect: N fresh, 0 stale, 0 broken
# actual: 332 fresh, 1 stale (InfoJitHelper)
./script/release-readiness.sh --json
# expect: helper-runtime-prelink status ok; user_release_ready yes (absent other failures)

Done when

  • php script/check-helper-runtime-prelink.php --strict → 0 stale
  • Unit re-emitted via emit-helper-runtime-object.php --prelink / --unit= (not fingerprint restamp)
  • release-readiness helper-runtime-prelink gate ok

Refs #24302, #23458, #25881

Metadata

Metadata

Assignees

No one assigned

    Labels

    IMPORTANTCritical patharea:toolingTooling / CI / docsbugSomething isn't workingimplementation-readySpec complete: repro, php-src ref, done-when — safe for workers to claimphase-0:FoundationPhase 0 – foundation & DevEx

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions