Reconcile existing GitHub issue metadata against the lifecycle contract

[proerror77]

Parent

#455

What to build

Perform one dry-run-first reconciliation of the existing Monday issue graph after the contract, lifecycle read/mutation commands, and auditor are merged. Preserve every comment and failure record; repair only approved labels, formatting, native relationships, and closure state after evidence-backed acceptance review.

Acceptance criteria

• Preflight exports the current issue/PR state, events, labels, native relationships, and closing references as immutable rollback evidence.
• A dry-run table lists every proposed body, label, parent, blocker, assignee, and state change before any mutation.
• Literal escaped newlines are repaired without changing contract meaning, and every open issue ends with exactly one category and one triage state.
• Approved prose Parent/Blocked-by relationships are represented natively without deleting the readable contract sections.
• CEX: add an MCTS research adapter for time-series HFT alpha discovery #205 and PRD: Verified Polymarket + Chainlink baseline research path #225 receive explicit parent acceptance audits; they close only if their outcomes are currently proven.
• CEX: 永续 mark/index、funding、OI 与 basis collector #222, CEX: WebSocket L2 delta 时序与连续性 collector #224, Roll out the current Rust Polymarket collector into continuous ready-event publication #326, and Publish and deploy a source-bound Polymarket quote runner #421 remain open unless their independent runtime criteria are proven; missing target/controller inputs use the appropriate non-runnable state.
• Stacked PR issue relationships are corrected without changing code or merge order.
• The post-migration auditor is green, or every retained exception is named and justified.

Blocked by

#456, #457, #458, #471, #607, #608, and #609 must merge first.

Runtime control

• Named controller: Codex /root under the repository owner's authorization in the initiating task.
• Target: GitHub issue, PR, label, and relationship metadata in proerror77/monday only.
• Stop rule: stop before any closure whose acceptance cannot be proven from current repository/runtime evidence.
• Rollback: restore bodies/labels/relationships from the immutable preflight export; reopen any issue closed incorrectly.

[proerror77]

This was generated by AI during triage.

Triage Notes

What we've established so far:

• Native blockers Define the closed-loop GitHub issue and PR contract #456, Mutate issue lifecycle from GitHub without a local mirror #457, Audit issue hygiene and PR closure semantics without mutation #458, Read issue lifecycle state from GitHub without a local mirror #471, and the required status-reconciliation issue Invalidate stale lifecycle status after linked issue metadata changes #480 are closed with evidence.
• The current runtime contract has no anchored Candidate field.
• Its Rollback refers to an immutable preflight export, but no durable export identity, location, or digest has been recorded.
• Keeping this issue ready-for-agent before those identities exist would violate the fail-closed lifecycle contract. Category enhancement and qualifier runtime remain correct.

What we still need from you (@proerror77):

• Confirm the durable immutable location for the preflight export and record its identity, digest, capture time, and source main SHA.
• Approve the exact dry-run mutation set and restoration procedure derived from that export. Only then should this issue return to ready-for-agent with one active controller.

[proerror77]

This was generated by AI during triage.

Evidence decision: bounded immutable preflight contract

Decision

Reuse Monday's existing canonical JSON plus SHA-256 sidecar pattern, persisted in a retained remote Git commit and unmerged evidence PR. Do not use GitHub Actions artifacts because their retention expires. Do not add a release, external object store, OCI repository, host service, or new evidence service for this governance operation.

The current decision baseline is main@69e42c1b47a1d0ea91a595637ee8cff031e67f11. The actual preflight must re-read and bind the then-current default-branch SHA immediately before capture.

Preflight identity

Before any metadata mutation, the named controller Codex /root captures the target proerror77/monday Issue and PR graph only. Branch protection, deployment, runtime resources, source code, and the separately publishing Agent-led PRD are excluded.

One retained, never-force-pushed evidence branch/PR must contain:

• preflight.json and preflight.json.sha256 with the complete canonical repository Issue/PR graph.
• manifest.json and manifest.json.sha256 binding schema version, repository identity, capture UTC, controller, target and exclusions, default-branch SHA, API version and media types, endpoint/page inventory, pagination completeness, per-page ETag or Last-Modified where available, object counts, and the preflight digest.
• forward-plan.json listing every approved body, label, assignee, parent, blocker, and state mutation before execution.
• reverse-plan.json derived from the preflight and containing the exact inverse for every mutable field.

The snapshot covers every repository Issue and PR plus the label catalog. Issue data includes body, state and reason, labels, assignees, timestamps, comments, timeline/events, native parent/sub-issues, blocked-by/blocking relationships, and closing PR references. PR data additionally includes head/base identities, commits, files, reviews, review comments, check-runs, commit statuses, and closing references. Keys are canonicalized and arrays use stable IDs or documented order before hashing.

The Candidate identity is the remote evidence commit SHA plus the verified preflight.json SHA-256 and evidence PR URL. A local worktree path is never part of the identity. The remote branch, commit, and PR must be independently readable from a fresh checkout/API client and must not be deleted.

Zero-write restoration dry-run

Any future mutation operation must append a content-addressed post-state receipt commit that binds the preflight commit, forward plan, controller, target, operation receipts, and canonical post-state digest. Restoration dry-run accepts the exact preflight commit and receipt commit only.

It must:

1. Fetch the exact remote commits and verify Git tree identities plus every SHA-256 sidecar.
2. Re-fetch the same complete endpoint/page set and verify scope, pagination, default-branch SHA, ETags where available, and canonical digests.
3. Refuse if live mutable state is not exactly the receipt state, if any endpoint/page is missing, or if any unplanned object changed.
4. Print the complete reverse patch from receipt state to preflight state for body, labels, assignees, native parent/blocker relationships, and Issue state.
5. Perform zero GitHub writes and exit nonzero on every mismatch.

Comments and timeline/events are preserved provenance, not rollback targets: the controller must never edit, delete, recreate, or impersonate them. Any comment/event addition, edit, deletion, or unexplained drift stops automated restoration and requires named-controller review.

Stop and rollback rules

Stop before mutation or restoration on an unreachable evidence commit/ref, digest mismatch, API/schema/media-type drift, incomplete pagination, rate-limit/error response, default-branch drift, relationship discrepancy, missing post-state receipt, unexpected live-state change, or an incomplete reverse patch. Preserve all failed-operation receipts. Actual rollback is a separately authorized controller action after the zero-write reverse patch is reviewed; it never changes branch protection, #460, deployment, runtime resources, source code, or the Agent-led PRD lane.

Readiness outcome

#459 remains needs-info. No broad legacy mutation is authorized until the real remote preflight commit/PR, file digests, Candidate identity, forward/reverse plans, and independent readback exist. #460 and branch protection remain frozen.