rdbms-playground

T

claude@clouddev1 b935090d7b docs: ADR-0034 — history.log as a complete journal; replay reads ok-only

Found while implementing 3f: history.log is success-only, but the
in-memory Up/Down recall ring records every submission — and the ring
is re-seeded from the log on open, so failed commands are recallable
in-session yet lost across sessions. Replay and recall also want
different inputs (state-builders vs everything-typed), which one
success-only file can't serve. And replay never parsed the pipe
format (run_replay parses whole lines), so `replay history.log` fails
on line 1 with no test covering it.

Decision: history.log becomes a complete journal tagged ok/err;
hydration reads all, replay reads ok-only and learns the format.
Amends ADR-0006 + ADR-0015 §5/§12. Code deferred to two tracked
sub-tasks. No migration for existing all-ok logs.

2026-05-22 19:17:52 +00:00

.codegraph

round-5 follow-up: completion + i18n sweep

2026-05-13 15:58:29 +00:00

docs

docs: ADR-0034 — history.log as a complete journal; replay reads ok-only

2026-05-22 19:17:52 +00:00

src

db: fix self-referential cascade over-count + SQL-delete render test

2026-05-22 19:17:43 +00:00

tests

db: fix self-referential cascade over-count + SQL-delete render test