Repository navigation
Reconcile existing GitHub issue metadata against the lifecycle contract #459
Description
Parent
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
/rootunder the repository owner's authorization in the initiating task. - Target: GitHub issue, PR, label, and relationship metadata in
proerror77/mondayonly. - 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.
Activity
proerror77 commentedon Aug 2, 2026
Triage Notes
What we've established so far:
Candidatefield.Rollbackrefers to an immutable preflight export, but no durable export identity, location, or digest has been recorded.ready-for-agentbefore those identities exist would violate the fail-closed lifecycle contract. Categoryenhancementand qualifierruntimeremain correct.What we still need from you (@proerror77):
mainSHA.ready-for-agentwith one active controller.proerror77 commentedon Aug 2, 2026
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 /rootcaptures the targetproerror77/mondayIssue 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.jsonandpreflight.json.sha256with the complete canonical repository Issue/PR graph.manifest.jsonandmanifest.json.sha256binding 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.jsonlisting every approved body, label, assignee, parent, blocker, and state mutation before execution.reverse-plan.jsonderived 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.jsonSHA-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:
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.proerror77 commentedon Aug 2, 2026
Evidence decision: durable preflight boundary (2026-08-03)
Current evidence
Issue Lifecycleaudit: 54 violations; this is a read-only work queue and is not a publication gate for the separate Agent-led PRD lane.main@8778004352e3157fa0950d50e16c9580208ae7bd.071a38b3d403c71a70e108cfeddf46df6024e7dc) plus observed GraphQL media provenance in PR fix(governance): bind observed GraphQL media type #615 (merge20ca2a1c).Smallest safe contract
Use the existing repository-native capture output: canonical
preflight.jsonandmanifest.json, each with its SHA-256 sidecar, written atomically with no overwrite. Capture must run against the then-currentmainSHA and include the complete Issue/PR graph, label catalog, comments/events, native relationships, closing references, PR head/base and review/check/status collections, page inventory, counts, API/media provenance, controller, target, and exclusions.Before any metadata mutation, preserve those four files plus
forward-plan.jsonandreverse-plan.jsonin one retained, never-force-pushed remote Git commit and unmerged evidence PR. The content identity is(evidence commit SHA, preflight.json SHA-256, evidence PR URL); it must be readable from a fresh clone/API client and must not depend on a local worktree. Do not substitute expiring Actions artifacts or add an OSS/service.Zero-write restoration dry-run
Given the exact preflight commit and post-state receipt commit, independently fetch both trees and verify every sidecar, scope, controller/target identity, default-branch SHA, page/pagination inventory, and canonical digest. Re-read the same live endpoint set and refuse on any concurrent mutable or provenance drift, missing page, API/media/schema/rate-limit error, or receipt mismatch. Print the complete canonical reverse patch for body, labels, assignees, native parent/sub-issue and blocked-by/blocking relationships, and Issue state; perform zero GitHub/filesystem writes. Comments/events and closing references remain provenance-only and are never edited or recreated. Actual rollback is a separately authorized controller action after review.
Readiness
#459 remains
enhancement + needs-info + runtime. It must not return toready-for-agentuntil the retained evidence commit/PR, file digests, Candidate identity, forward/reverse plans, and independent readback exist. #460 and branch protection remain frozen.proerror77 commentedon Aug 2, 2026
Evidence update after #609: carrier remains the stop boundary
plan-restorecontract at25b6e6d15b5bffc7fb0894a87a07dbcf7e616e5b; Issue Plan zero-write Issue lifecycle restoration from an exact receipt #609 is closed with completion evidence.Therefore #459 remains
enhancement + needs-info + runtime, unassigned. No formal full capture, forward plan, reverse-plan carrier, post-state receipt, or mutation is authorized. The next bounded decision is a separately reviewed repository-native immutable-carrier contract; until it exists, #460, required checks, branch protection, and the 54-item work queue remain frozen.proerror77 commentedon Oct 4, 2026
Keeping this runtime issue open. Missing evidence: an approved immutable evidence carrier, retained full preflight/Candidate identity and digests, approved forward/reverse plans, and independent post-reconciliation/restoration readback.