#13: durable retry/attempt accounting #42

Merged

lost-rob0t merged 11 commits from rage/13-retry-attempt-red into main

2026-08-31 19:22:10 +00:00

lost-rob0t commented

2026-08-31 19:21:50 +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.
Evidence: evidence/LLM-LOG-EVIDENCE-025-task-retry-attempt-red.org and evidence/LLM-LOG-EVIDENCE-026-task-retry-attempt-green.org.

Accepted RED first proved explicit attempt/retry metadata was dropped. Adversarial RED then proved a legacy immutable usage replay could conflict if absent optional fields were serialized as NIL keys. The final implementation preserves legacy projection identity while persisting explicit attempt/retry evidence when present.

Verified behavior:

bounded restart-durable attempt/retry reconstruction through Tek9 task/usage indexes;
existing request/token/cost accounting preserved;
no retry inference from timing/session adjacency;
incomplete metadata remains explicit;
no Python rule engine, Tek9 repository mutation, or dotfiles mutation;
SWI-Prolog retains pricing inference ownership.

Exact tested head: beaab8aa2806d6bb2a7081b6b579a77e781d551c; evidence-only exact-head workflow 33429992265 is GREEN across Common Lisp/Tek9/SWI-Prolog, Python policy/transport, and Home Manager.

Bounded Auto-ARADR + Auto-RAGE slice for #13. Canonical design: `research/LLM-LOG-RESEARCH-042-task-retry-attempt-accounting.org`. Evidence: `evidence/LLM-LOG-EVIDENCE-025-task-retry-attempt-red.org` and `evidence/LLM-LOG-EVIDENCE-026-task-retry-attempt-green.org`. Accepted RED first proved explicit attempt/retry metadata was dropped. Adversarial RED then proved a legacy immutable usage replay could conflict if absent optional fields were serialized as NIL keys. The final implementation preserves legacy projection identity while persisting explicit attempt/retry evidence when present. Verified behavior: - bounded restart-durable attempt/retry reconstruction through Tek9 task/usage indexes; - existing request/token/cost accounting preserved; - no retry inference from timing/session adjacency; - incomplete metadata remains explicit; - no Python rule engine, Tek9 repository mutation, or dotfiles mutation; - SWI-Prolog retains pricing inference ownership. Exact tested head: `beaab8aa2806d6bb2a7081b6b579a77e781d551c`; evidence-only exact-head workflow `33429992265` is GREEN across Common Lisp/Tek9/SWI-Prolog, Python policy/transport, and Home Manager.