ci(mcp-plugin-delivery-contract-drift): include workspace-runtime in drift gate #3152
Reference in New Issue
Block a user
Delete Branch "feat/mcp-contract-drift-runtime"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Extends
.gitea/workflows/mcp-plugin-delivery-contract-drift.ymlto also fetch and byte-comparemolecule-ai-workspace-runtime's vendored copy ofcontracts/mcp-plugin-delivery.contract.jsonagainst core's local copy.Why: the runtime is now a contract party (its literal drift caused RCA#2970 / the concierge-online bug). The runtime already has an in-repo literal gate, but adding it to the cross-repo byte-compare closes the loop so core/template/runtime cannot diverge.
What changed:
molecule-ai-workspace-runtime.Lint policy: no
continue-on-error;bp-required: pending #3080remains unchanged (soak-then-promote). SOP markers below.SOP Checklist
lint-workflow-yaml.pyandlint_required_context_exists_in_bp.pypassed locally. The new step mirrors the proven template block.feedback_behavior_based_ast_gates.Closes #3095.
APPROVED on current head
73f1f01937.5-axis review:
5-axis current-head review clean. The workflow change is limited to mcp-plugin-delivery-contract-drift.yml and extends the accepted template byte-compare pattern to molecule-ai-workspace-runtime. It uses the same trusted-context token handling, fetch/fallback behavior, and a hard diff -u against core's local contracts/mcp-plugin-delivery.contract.json, so runtime drift fails loudly while untrusted forks still soft-skip without secrets. No unrelated workflow or code changes found.