RUMBO R4 — Successor PR #412 Exact TEST_ONLY Binding

Status: PASS / MERGE_NOT_AUTHORIZED / PRODUCTION_NO_GO

This record supersedes the historical PR #392 binding for active continuity work.

Exact GitHub binding

  • PR: 412
  • base SHA observed at binding precheck: 1ad77acefc7326595c50d7b0edffa81a2188e737
  • head SHA: d0043f418c1b0f7d21b36dc1c5469c9ded49cfd7
  • changed files: 5
  • PR state: OPEN / DRAFT
  • mergeable at precheck: true
  • branch relation at precheck: 7 ahead / 4 behind current main

Repository identity SHA-256:

59e28afe0dd67d61cdaaaa5d470a6470b6c1540f025d172f094fe3321857fc23

Control package SHA-256:

afbdc77510286adc5721ada5a0ddfa75e10305cb5200d6fd37cd8438c9c6119f

External evidence object

Canonical evidence SHA-256:

67613e277793d67e574db7af2399084e454209af492b78dbff2c8c99e0ff5b8b

Scope:

TEST_ONLY_SUCCESSOR_PR_HEAD_BINDING_NO_MERGE_NO_PRODUCTION

The evidence object also recorded:

  • runtime R4-ACCEPTANCE-GUARD;
  • HTTP runtime file version 40;
  • guard configured true;
  • merge authorization enabled false;
  • production_go=false;
  • Codex runtime acceptance PENDING_CODEX_ACK;
  • observer run 33229303565 queued at binding precheck.

One-time transaction

Val Town evaluation ID:

01a04b5f-19d9-73cd-a69c-a81df8bad877

Result:

  • selftest: PASS
  • authorization ID: 5ea45798-b901-42c3-bd6a-bc3998f6c2a8
  • request SHA-256: 28ca0c6ec5eeb5b1f54554b863cfe03c02e94876a95dee38b44713cca6b37c2d
  • consumption receipt SHA-256: f2fbfe727122a89f3833d97a54b9497d29d860f5bf1efdabeef76ceca708195f
  • merge_authorized: false
  • production_go: false

The dedicated guard bearer and raw one-time token were used only inside the Val Town runtime and were not logged. The temporary self-test script was deleted after the single successful execution.

Claim boundary

This proves a live, exact, one-time TEST_ONLY authorization for the stated PR #412 snapshot.

It does not authorize merging, deployment, product production, or bypass of any unresolved trust-root gate. If the PR head or relevant base evidence changes, this receipt becomes historical and a new exact binding is required.