Cleanup pane, Pi session tools, review from the UI, project registry, needs panel acts
This commit is contained in:
Sam
@@ -2554,3 +2554,120 @@ Committed as `f949345`; `docs/RUNS-AND-MERGE.md` now carries the explanation of
|
||||
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-each-of-those-was-a-real-defect-not-misunders|Rich discovery: each-of-those-was-a-real-defect-not-misunderstanding-on-your 2026-11-11 02:28:06]]
|
||||
- context: [[packs/paperclip-harness/20-context/each-of-those-was-a-real-defect-not-misunderstanding-on-your|each-of-those-was-a-real-defect-not-misunderstanding-on-your]]
|
||||
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|each-of-those-was-a-real-defect-not-misunderstanding-on-your repository structure and configuration patterns]]
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Update (2026-11-11 02:40:13)
|
||||
|
||||
As of this turn in the paperclip-harness repo: 13 tasks exist in the project, only 1 open — AUD-162 'Tree render check' in todo, a leftover test task from the first day. All others done, including AUD-168, AUD-169, AUD-170, AUD-171 created earlier the same day.
|
||||
|
||||
Environment caveat: `~/.pi/paperclips` holds 37 sessions, 21 of them from a closed project's tests. This path is Pi history and must never be touched by cleanup tooling.
|
||||
|
||||
Build/validation: `go build` returned build=0 after the footer change; commit 0476afc; the eight workspaces were rebuilt and are running.
|
||||
|
||||
## Detailed observations from completed turn
|
||||
|
||||
Footers are now short and comma-separated, with `n p` in:
|
||||
|
||||
```
|
||||
Work n p task, [ ] tab, ↑↓ scroll, enter log, o pick, m merge, t tools, r refresh, R rebuild
|
||||
Board ↑↓ move, enter open, a assign, u unblock, t tools, / filter, ? keys, tab panel, r refresh
|
||||
Agents [ ] tab, enter open, p P w pause/resume/wake, r refresh, ? keys
|
||||
Repair [ ] tab, R rebuild, ↑↓ scroll, r recheck, q quit
|
||||
Reply enter reply, s status, ↑↓ scroll, r refresh, R rebuild, q quit
|
||||
New task tab field, enter next/create, ctrl+n tab, esc cancel
|
||||
```
|
||||
|
||||
## What is left — `docs/NEXT.md`
|
||||
|
||||
In order of usefulness:
|
||||
|
||||
1. **`Repair>cleanup`** — the pane you asked for: sessions with pane count and age, kill only what you tick, refuse attached ones and refuse `paperclip-harness`, and never touch `~/.pi/paperclips` (that is your history). Still 37 sessions, 21 of them from the closed project's tests; nothing killed.
|
||||
2. **A Pi session browser** — cheapest first: a `t` entry opening `~/.pi/paperclips` in Yazi, and one running `pi --resume`. A transcript tab later only if browsing files feels like a detour.
|
||||
3. **`Project>projects`** — a registry of adopted projects (id, folder, host, session) with a switch key. A project on `.27` shows as `on .27`, not offered.
|
||||
4. **Start a review from `Work>review`** — `v` runs `bin/review <task> --post` in the background, tab follows the log, exactly as merge does now.
|
||||
5. **The old `office` scaffold** — `settings.toml`, a file per role, `verify.sh`, page notes, writing only what is missing. The cheapest remaining gap in the project layer.
|
||||
6. **`Board>needs` acting on a card** — unblock, assign, open in Reply, from the card itself.
|
||||
7. **Spend chart** in `Project>overview`, in Go, next to the runs sparkline.
|
||||
8. **Memory per agent** — read-only row showing whether an agent uses engram or headroom, before any switch.
|
||||
9. **MOUSE-1** — key present, software absent; triage only, never a gate.
|
||||
|
||||
## Unproven, worth a test
|
||||
|
||||
- opening a project **on another machine** (`bin/office --host`) — written, never exercised;
|
||||
- **clicking** a task row with the mouse — zones wired, nobody has clicked;
|
||||
- `R` from a pane that is not at its expected size;
|
||||
- a task whose blocker is still **open** — does the agent stay away until it closes?
|
||||
|
||||
## Paperclip tasks in this project
|
||||
|
||||
Thirteen tasks, **one open**: `AUD-162`, a leftover test task in `todo` from the first day. Everything else is `done` — including the four you created today (`AUD-168`, `AUD-169`, `AUD-170`, `AUD-171`).
|
||||
|
||||
Committed as `0476afc`; the eight workspaces were rebuilt and are running. My suggestion for the next session: build `Repair>cleanup` first, since you have a concrete pile of junk to clear and it is a read-then-confirm operation with no risk to the Pi history.
|
||||
|
||||
## Evidence
|
||||
|
||||
- Confidence: 80%
|
||||
- Reason: Factual counts, task state, and the never-touch path caveat are durable operational facts.; enriched with final-answer detail because persistence should be reusable
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Update (2026-11-11 02:40:13)
|
||||
|
||||
## Structural/configuration observations (2026-11-11 02:40:13)
|
||||
|
||||
Footers are now short and comma-separated, with `n p` in:
|
||||
|
||||
```
|
||||
Work n p task, [ ] tab, ↑↓ scroll, enter log, o pick, m merge, t tools, r refresh, R rebuild
|
||||
Board ↑↓ move, enter open, a assign, u unblock, t tools, / filter, ? keys, tab panel, r refresh
|
||||
Agents [ ] tab, enter open, p P w pause/resume/wake, r refresh, ? keys
|
||||
Repair [ ] tab, R rebuild, ↑↓ scroll, r recheck, q quit
|
||||
Reply enter reply, s status, ↑↓ scroll, r refresh, R rebuild, q quit
|
||||
New task tab field, enter next/create, ctrl+n tab, esc cancel
|
||||
```
|
||||
|
||||
## What is left — `docs/NEXT.md`
|
||||
|
||||
In order of usefulness:
|
||||
|
||||
1. **`Repair>cleanup`** — the pane you asked for: sessions with pane count and age, kill only what you tick, refuse attached ones and refuse `paperclip-harness`, and never touch `~/.pi/paperclips` (that is your history). Still 37 sessions, 21 of them from the closed project's tests; nothing killed.
|
||||
2. **A Pi session browser** — cheapest first: a `t` entry opening `~/.pi/paperclips` in Yazi, and one running `pi --resume`. A transcript tab later only if browsing files feels like a detour.
|
||||
3. **`Project>projects`** — a registry of adopted projects (id, folder, host, session) with a switch key. A project on `.27` shows as `on .27`, not offered.
|
||||
4. **Start a review from `Work>review`** — `v` runs `bin/review <task> --post` in the background, tab follows the log, exactly as merge does now.
|
||||
5. **The old `office` scaffold** — `settings.toml`, a file per role, `verify.sh`, page notes, writing only what is missing. The cheapest remaining gap in the project layer.
|
||||
6. **`Board>needs` acting on a card** — unblock, assign, open in Reply, from the card itself.
|
||||
7. **Spend chart** in `Project>overview`, in Go, next to the runs sparkline.
|
||||
8. **Memory per agent** — read-only row showing whether an agent uses engram or headroom, before any switch.
|
||||
9. **MOUSE-1** — key present, software absent; triage only, never a gate.
|
||||
|
||||
## Unproven, worth a test
|
||||
|
||||
- opening a project **on another machine** (`bin/office --host`) — written, never exercised;
|
||||
- **clicking** a task row with the mouse — zones wired, nobody has clicked;
|
||||
- `R` from a pane that is not at its expected size;
|
||||
- a task whose blocker is still **open** — does the agent stay away until it closes?
|
||||
|
||||
## Paperclip tasks in this project
|
||||
|
||||
Thirteen tasks, **one open**: `AUD-162`, a leftover test task in `todo` from the first day. Everything else is `done` — including the four you created today (`AUD-168`, `AUD-169`, `AUD-170`, `AUD-171`).
|
||||
|
||||
Committed as `0476afc`; the eight workspaces were rebuilt and are running. My suggestion for the next session: build `Repair>cleanup` first, since you have a concrete pile of junk to clear and it is a read-then-confirm operation with no risk to the Pi history.
|
||||
|
||||
## Source paths observed
|
||||
|
||||
- `pause/resume/wake`
|
||||
|
||||
## Evidence
|
||||
|
||||
- Confidence: 82%
|
||||
- Reason: Captured factual repo structure/configuration patterns from rich discovery
|
||||
|
||||
## Related learned memories <!-- same-turn-2026-11-11 02:40:13 -->
|
||||
|
||||
- context: [[packs/paperclip-harness/20-context/paperclip-harness-tui-key-hint-footer-convention-and-planned|paperclip-harness TUI key-hint footer convention and planned work]]
|
||||
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|paperclip-harness task state and session inventory]]
|
||||
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-pause-2026-11-11-02-40-13|Rich discovery: pause 2026-11-11 02:40:13]]
|
||||
- context: [[packs/paperclip-harness/20-context/paperclip-harness|pause]]
|
||||
|
||||
Reference in New Issue
Block a user