docs(agent): stability+usefulness survey #71 — 2 PROPOSED items
All checks were successful
Check / eval (push) Successful in 2m58s
All checks were successful
Check / eval (push) Successful in 2m58s
Research iteration (LOOP §1). Findings: the state-file path is robust; the real stability hole is the eval-only automated lock-bump gate (#14) with no binary cache, whose true fix is the KVM-blocked #20. Usefulness: the capture suite lacks a screenshot annotate step. Filed 2 PROPOSED — an interim build-tier lock gate (no KVM) and a satty annotate step. V0 (docs-only). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -17,6 +17,26 @@ Template:
|
||||
|
||||
---
|
||||
|
||||
## 2026-07-08 — Stability + usefulness survey → 2 PROPOSED (iteration #71)
|
||||
- **Task:** Bernardo asked to find the next tasks that make the distro more
|
||||
stable + more useful. Research iteration (LOOP §1: write up PROPOSED).
|
||||
- **Did:** mapped the module/pkg surface + HARDWARE-QUEUE. Findings:
|
||||
(stability) the state-file path is robust (friendly JSON errors, validate
|
||||
cmd, atomic rebuild on corruption — not a gap); the real hole is the
|
||||
automated lock-bump channel (#14) pushing to `main` on **eval-only** with
|
||||
**no binary cache**, so untested runtime/build breakage compiles straight
|
||||
onto users — the true fix is #20 (VM-suite-in-CI, `[human]`, KVM-runner-
|
||||
blocked). (usefulness) the capture suite is rich but has no screenshot
|
||||
**annotate** step (no satty/swappy); clipboard/emoji/colorpicker/OCR/
|
||||
recording all already ship. Filed 2 PROPOSED: an interim build-tier lock
|
||||
gate (no KVM needed, raises the floor until #20) and a satty annotate step.
|
||||
- **Verified:** V0 (docs-only; flake check was green in #70, tree unchanged).
|
||||
- **Pending:** Bernardo to triage the 2 PROPOSED into tiers, and — the
|
||||
highest-leverage stability action — decide whether to unblock #20 (register
|
||||
a KVM runner) so the lock-bump channel gets a real runtime gate.
|
||||
- **Next suggestion:** if #20 stays blocked, the interim build-tier gate is
|
||||
the cheapest stability win; satty is the cheapest usefulness win.
|
||||
|
||||
## 2026-07-08 — QA sweep: clean tree, no actionable drift (iteration #70)
|
||||
- **Task:** QA sweep — headless-actionable queue is empty (NEXT is all
|
||||
`[human]`/`[blocked:hw]`/V3-visual: #29 hw, #28 icon-weight [human]+visual,
|
||||
|
||||
Reference in New Issue
Block a user