jake/Lumotia
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update residuals status after tracing and storage passes

Browse Source 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jake
2026-05-12 23:27:15 +01:00
parent a36ae7e068
commit c55b0aaae0
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/superpowers/plans/2026-05-12-engine-slop-residuals.md
View File

@@ -9,6 +9,22 @@ description: Roadmap for the deferred code-quality items that did not fit in the
> **For agentic workers:** This is a meta-plan. It catalogues independent residual work areas, each of which should get its own detailed TDD plan when scheduled. Do **not** treat the sections below as a single execution checklist. > **For agentic workers:** This is a meta-plan. It catalogues independent residual work areas, each of which should get its own detailed TDD plan when scheduled. Do **not** treat the sections below as a single execution checklist.
## Status update — 2026-05-13
Completed:
- B. eprintln → tracing sweep — landed in `184214b`.
- Tracing finishing pass — hotkey `log::` migrated to `tracing::` in `48c4838`.
- A. Storage-layer typed errors — survey in `fdab777`, migration in `52565ea`, legacy `StorageError(String)` removal in `a36ae7e`.
Next recommended:
- Phase 10a dogfood before Area E, to validate the new observability and storage-error semantics in real app use.
Still open:
- D. Property-based DSP testing.
- E. FE/BE error boundary cleanup.
- C. Actor-model refactor.
- F. Packaged-binary Linux launcher contract.
## Context ## Context
On 2026-05-12 an external code review rated the codebase 4/10 and laid out a four-bucket de-sloppifying plan. That pass shipped (uncommitted in working tree at time of writing). It hit the *prognosis-level* items only: On 2026-05-12 an external code review rated the codebase 4/10 and laid out a four-bucket de-sloppifying plan. That pass shipped (uncommitted in working tree at time of writing). It hit the *prognosis-level* items only: