Skip to content

Stage and verify complete bootstrap receipt and seed permissions before native canaries #212

Open

Description

@realmarcin

The first real M5 prerequisite production canary on runtime 2f99a16 failed before canonical save. Package staging copied all 378 declared file bindings, but the production replay prompt and parent bootstrap checker also require .temp/edge-calibration-20261115/fresh-47/receipt.json. That bootstrap receipt was outside the source manifest and was not staged. The native worker independently confirmed its absence including ignored files and preserved a failed canary result.

The same inspection found seed occurrence.json, packet.json and source.json at mode 0400. The maintained preparation checker requires 0600. rounds.write intentionally seals package files as 0400, so blindly using it for these original bootstrap artifacts breaks the actual path even when bytes are correct.

Fix the staging contract to bind the exact complete bootstrap inputs/receipt with their required modes, or generate a new explicitly identified valid preparation receipt through the maintained path where its runtime bindings require it. Do not fabricate or silently update old receipts. Run the actual prepare_calibration --check fresh-47 in the staged clone during the free preparation checks and before any native worker. Verify actual persisted bytes and modes, and add a meaningful regression covering the real checker.

Preserve reviewer-a and its failed outputs under m5-prerequisite-reviewers-20261117. No canonical pair was saved, no science started and the second clone was not provisioned. Re-canary a new clone on the repaired runtime before any fanout. Related #206/#207/#208; found during PR #211 live verification.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions