Skip to content

Re-arm projection rows parked as terminal Codex collisions #4327

Closed

Description

@ScriptedAlchemy

#4326 (Fixes #4279) stops a stored session's differing project_path from refusing a Codex rollout as a collision, and stops parked terminal rows from keeping every pass backpressured. Rows already parked terminal on existing profiles (for example the beta.88 profile in #4279) are not re-armed, so their dropped message text stays missing until a full projection rebuild.

Acceptance: on upgrade, rows parked terminal only because of the project_path mismatch #4326 now accepts are re-armed once and project their messages. Genuine collisions (transcript_path, lineage, project_key) stay parked. A test seeds a profile with such a parked row and shows the messages appear after one pass.

Activity

  1. ScriptedAlchemy commented on Oct 19, 2026

    @ScriptedAlchemy
    OwnerAuthor

    Full-backlog assignment: own the Codex projection follow-up cluster #4327, #4328 and #4329, coordinated with production report #4279 and existing fix PR #4326. Read all issues and the latest #4326 diff/comments first. Reuse or stack on that fix, preserving its source identity and code; do not duplicate or revert it. Implement one-time rearming only for the obsolete project_path collision, keeping genuine transcript/lineage/project-key conflicts parked. Give distinct live rollout files independent rewrite identities so one cannot supersede the other's messages, with migration/replay coverage. Expose daemon-owned per-provider projected/refused/parked and last-progress/throughput/stall evidence without direct private DB reads or invented counters. Test old-profile upgrade, repeated upgrade, two-file rewrites, genuine collision and slow-versus-stalled passes through production APIs. Preserve protected text, projection receipts, rollback, cancellations and session authority. Do not claim all observed CPU is explained by one collision. Use existing Bazel/codegen, real nonzero counts and <=72-character commit headers; no data resets, raised timeouts or disabled tests. Publish reviewable changes and acceptance evidence; keep any full production soak unverified if not performed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions