Skip to content

[codex] remediate 0.18 accuracy and warm indexing - #2100

Closed
TheGreenCedar wants to merge 14 commits into
dev/codestory-nextfrom
codex/2099-v018-remediation
Closed

[codex] remediate 0.18 accuracy and warm indexing#2100
TheGreenCedar wants to merge 14 commits into
dev/codestory-nextfrom
codex/2099-v018-remediation

Conversation

@TheGreenCedar

Copy link
Copy Markdown
Owner

Closes #2099
Refs #2098

Context

The retained 0.18 product receipt proves a Dart accuracy regression and a 21.692-second Redis one-file refresh. This draft starts from that failed evidence and keeps broad qualification closed until the focused remediation lanes pass.

Base: a41e605
Current head: 4585ebf

What changed

  • Added the machine-readable remediation failure ledger.
  • Replaced whole-task warm labeling with separate runner, first-packet, continuation, final-packet, and whole-task timing.
  • Made reused comparator rows timing-ineligible.
  • Added a reconciled incremental wall receipt with scheduled-path reasons and exclusive core/retrieval phases.
  • Added the exact append-LF incremental preflight.

How to review

Start with the incremental wall receipt in the contracts/runtime/CLI path, then the installed timing cohort contract, then the two evidence scripts. Product repairs will follow as focused commits in this same draft lane.

Verification

  • Node benchmark and remediation-ledger tests: 186 passed.
  • codestory-contracts: 115 passed across unit and integration targets.
  • Focused store promotion, runtime incremental, CLI receipt, and rendering tests passed.
  • cargo fmt --all -- --check and git diff --check passed.
  • Redis exact append-LF, five repeats: 19.702-21.048 seconds, 100% outer-wall reconciliation.

Risk and non-claims

This commit records and separates the failing work; it does not claim the accuracy or performance regression is repaired. No broad qualification, calibration, packaging, or release proof has run.

@TheGreenCedar

Copy link
Copy Markdown
Owner Author

Accuracy slice complete on 166e87e.

Dart is 3/3 on the unchanged scorer with all four claims, zero forbidden or unsupported-proof errors, and zero source reads. The packet is 16 rows / 15,978 bytes and contains all required helper, client, finalization, request, response, and IO transport source. The Monolog, Alamofire, Gin, Requests, ripgrep, and SWR structural watchlist has no carrier losses; compacted graph relations retain their semantics.

The draft remains open for Phase 2. Broad qualification has not run.

@TheGreenCedar

Copy link
Copy Markdown
Owner Author

0.18 accuracy candidate invalidated (decontamination)

PR #2100 / branch codex/2099-v018-remediation is not mergeable as an accuracy candidate. Contaminated accuracy work is quarantined; a clean decontamination lane replaces it.

Quarantine identities

Artifact Value
Contaminated branch codex/2099-v018-remediation @ 166e87e3bb6c8f553525ced7e36ab27a843790cc
Dirty worktree (preserved, not rewritten) /Users/albert/.codex/worktrees/2099-v018-remediation/CodeStory
Integration base dev/codestory-next @ a41e605ea01e9e2c8b400eb5ee5456efd05f060e
Replacement branch codex/2099-v018-decontamination (from a41e605e)
Evidence root /Users/albert/.codex/evidence/codestory-v018-decontamination/
Failed product receipt (preserved) /Users/albert/.codex/evidence/codestory-v018-a41e605e-failed-product-receipt

SHA-256 digests

aefaaac79115bb538e23d495539b2145429bafd278f7702ef8c2a10e63393088  dirty-remediation-complete.binary.patch
130c4a084285af4a9324a342f8bd33284d7637e8bb2973367cba640c850e9a70  dirty-remediation-performance.binary.patch
cf85c6a3029115393c89eaceb0b1f94bd8d733bdd2f563530969d1f80f1a5523  dirty-remediation-untracked.tar.gz
ad36dfa86d8056c2eedf9e0df0788b0922821fc491adfc9aeb7ed166d740eace  dirty-remediation-git-status.txt
a5fc6dee4f4f4a5485a0b1ab8a84df557c2c1330c918dc924faf6b9336e0e658  dirty-remediation-identity.txt
3a4bfce662d7cce7b006d334ca8d176a56cf55febfe057fe8f1b32df664bec64  unreviewed-partial/packet_evidence_carriers.rs.binary.patch
98043904b94901db73fb726fd088b82fb5161157ecdb9067f3929422e158b0ce  unreviewed-partial/packet_evidence_carriers.rs.worktree
6e2f23551c2b5e36d7741e70b9b5b9aa334fc10f82b1210d609661128a9c8293  unreviewed-partial/packet_evidence_carriers.rs.HEAD
b15c1380f67d16bbae564a7a9641fe1332f5a4148790fb1150f8f78387df6f2c  dirty-untracked-files/.../core_publication.rs
6f1494eb6a1dce7125ee1977a894f6d767ffc9f6459988871f17a6a280866d62  dirty-untracked-files/.../core_generation.rs
d796693321990719759a9e9ac82ff1c5cb91d18505fcb3c3d3a64f8481c2ca02  dirty-untracked-files/.../codestory-incremental-refresh-microprobe.mjs

Index tree at capture (matches HEAD tree; dirty changes unstaged): 667a4d7250807e8a17f4908540b927225d50f9c9

Policy

  • Accuracy commits 2f4d0b82..166e87e3 will not be replayed onto the decontamination branch.
  • Dirty performance bytes stay quarantined under the evidence root until Phase 5 causal-unit replay.
  • Uncommitted packet_evidence_carriers.rs edits are archived separately as unreviewed partial work.
  • Historical 18-task / Dart accuracy rows are marked evidence_eligibility: "contaminated_development" (release_gate: false, generalization_claim: forbidden) and are never a release or generalization gate.
  • No broad package / calibration / release qualification is running for this candidate (only unrelated protected-runner heartbeat was queued).

Parent: #2098 · Child: #2099 · Quarantined PR: #2100

@TheGreenCedar

Copy link
Copy Markdown
Owner Author

Quarantine reminder (Phase 8)

This PR remains historical quarantine and is not mergeable as an accuracy / 0.18 product candidate.

Decontamination supersedes this lane on draft PR #2101 (codex/2099-v018-decontamination @ c18d79485f03b3c930b6a5170748429827f04027). Do not merge #2100; do not replay accuracy commits into the decontamination head.

@TheGreenCedar

Copy link
Copy Markdown
Owner Author

Superseded. Contaminated remediation lane; not a candidate. Active work is #2103.

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

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant