ahmed mohammedandClaude Opus 4.7
8b42a0931c
kb/ is its own wiki root: 34 pages across 7 categories, index.md catalog, log.md, AGENTS.md schema layer, and raw/ holding copies of README, the spec, the 13-task plan, the design master and the SDD ledger. Every page cross-references 3 to 6 others and all 107 wikilinks resolve except two [["list"]] artefacts inside JSON snippets in the copied plan. Kept separate from the repository root on purpose: its generated graph lands in kb/.ua/ instead of overwriting the code graph. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
693 B
693 B
Analysis row lifecycle
A row is created before the plan is validated, so every attempt is visible in the rail. Status moves through
running → done | failed | partial | abandoned.
partial means some stages produced output before the run stopped. abandoned means the browser went away
mid-run. Both surface as pills in the history rail rather than being hidden, and /app/[id] renders whatever
exists with a "this run was interrupted before it finished" note.
/app/[id] never redirects a running row. An earlier version did, which turned a row orphaned by a crashed
process into an infinite self-redirect.
Related: SSE stream, SQLite schema, History rail.