#13 RED: durable retry/attempt accounting #41

Closed

lost-rob0t wants to merge 0 commits from rage/13-retry-attempt-red into main

lost-rob0t commented

2026-08-31 18:12:23 +00:00

(Migrated from github.com)

Bounded Auto-ARADR + Auto-RAGE slice for #13.

Canonical design: research/LLM-LOG-RESEARCH-042-task-retry-attempt-accounting.org.

This PR is intentionally RED-first. It adds no production retry implementation yet.

The new Common Lisp/Tek9 integration fixture proves the current expert plane drops explicit attempt/retry metadata from immutable usage projections. Required behavior after implementation:

persist explicit attempt identity and retry predecessor provenance;
preserve existing request/token/cost accounting;
reconstruct retry/attempt counts after expert-host restart through bounded Tek9 task/usage retrieval;
keep incomplete attempt metadata explicit;
no Python retry rule engine, no corpus scan, no Tek9 repository mutation.

The branch is based on current main after PR #40 (7b1d4359764fcc87fb967ed6e6577a9eaf6f3045). Production mutation is gated on an independently executed legitimate RED.

Bounded Auto-ARADR + Auto-RAGE slice for #13. Canonical design: `research/LLM-LOG-RESEARCH-042-task-retry-attempt-accounting.org`. This PR is intentionally RED-first. It adds no production retry implementation yet. The new Common Lisp/Tek9 integration fixture proves the current expert plane drops explicit attempt/retry metadata from immutable usage projections. Required behavior after implementation: - persist explicit attempt identity and retry predecessor provenance; - preserve existing request/token/cost accounting; - reconstruct retry/attempt counts after expert-host restart through bounded Tek9 task/usage retrieval; - keep incomplete attempt metadata explicit; - no Python retry rule engine, no corpus scan, no Tek9 repository mutation. The branch is based on current `main` after PR #40 (`7b1d4359764fcc87fb967ed6e6577a9eaf6f3045`). Production mutation is gated on an independently executed legitimate RED.