generated from coulomb/repo-seed
The analysis half of the weekly coding retrospection. retro/build.py: windowed detect+measure -> top-3 improvement suggestions per repo (cross-flavor first, recommendations pulled from the Pattern Catalog) + fleet snapshot. retro/publish.py: publishes the report to the hub as the coding_retro read model (event_type= coding_retro progress event) + local JSON/md, graceful degrade. retro entrypoint with --window-days/--publish/--json. Live verify over real sessions surfaced per-repo suggestions with catalog recommendations. 13 new tests; suite 152/152. Consumed by activity-core ACTIVITY-WP-0008 (Weekly Coding Retrospection, Sat 19:00). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
5.2 KiB
5.2 KiB
Weekly Coding Retro (2026-05-08 → 2026-06-07)
23 real sessions · generated 2026-06-07T17:14:00Z
Top improvement suggestions (cross-flavor first, ≤3 per repo)
- net-kingdom (high, score=54.0) [CROSS-FLAVOR]: cross-flavor problem: recurring error — Investigate recurring error on make: *** [makefile:: fix-consistency] error
- activity-core (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- artifact-store (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- citation-evidence (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- infospace-bench (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- railiance-apps (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- state-hub (high, score=13128.0): problem: tool thrash — Batch related shell work into one script, not many small Bash calls
- activity-core (high, score=441.0): problem: schema thrash — Load the tool schemas you'll need once, up front
- citation-evidence (high, score=441.0): problem: schema thrash — Load the tool schemas you'll need once, up front
- flex-auth (high, score=441.0): problem: schema thrash — Load the tool schemas you'll need once, up front
- infospace-bench (high, score=441.0): problem: schema thrash — Load the tool schemas you'll need once, up front
- ops-bridge (high, score=441.0): problem: schema thrash — Load the tool schemas you'll need once, up front
- activity-core (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- citation-evidence (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- infospace-bench (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- issue-facade (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- railiance-apps (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- state-hub (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- the-custodian (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- vergabe-teilnahme (high, score=290.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has not been read yet. read it first before writing to it.<>
- artifact-store (medium, score=78.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has been modified since read, either by the user or by a linter. read it again before attempting to write it.<>
- issue-facade (medium, score=78.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has been modified since read, either by the user or by a linter. read it again before attempting to write it.<>
- railiance-apps (medium, score=78.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has been modified since read, either by the user or by a linter. read it again before attempting to write it.<>
- state-hub (medium, score=78.0): problem: recurring error — Investigate recurring error on <tool_use_error>file has been modified since read, either by the user or by a linter. read it again before attempting to write it.<>
- artifact-store (medium, score=50.55): problem: budget overrun — Read narrowly — target the region you need, not whole large files
- vergabe-teilnahme (medium, score=12.0): problem: recurring error — Investigate recurring error on {
- ops-bridge (medium, score=10.0): problem: recurring error — Investigate recurring error on found errors ( fixed, remaining).
- net-kingdom (medium, score=6.0): problem: recurring error — Investigate recurring error on (note: edit also tried swapping \uxxxx escapes and their characters; neither form matched, so the mismatch is likely elsewhere in old_string. re-read the file a
- ops-bridge (medium, score=6.0): problem: recurring error — Investigate recurring error on found error ( fixed, remaining).
- agentic-resources (medium, score=4.0): problem: recurring error — Investigate recurring error on failed, passed in .00s
Fleet snapshot
- infra-overhead median: 0.167
- error rate: 0.957 · schema-thrash: 7
- success rate: 1.0 · tokens p50: 250725