Files

Sam 3ec960e349 Cleanup pane, Pi session tools, review from the UI, project registry, needs panel acts

2026-11-11 14:16:12 +11:00

4.1 KiB

Raw Blame History

type: session id: session.paperclip-harness.rich-discovery-pause-2026-11-11-02-40-13 title: Rich discovery: pause 2026-11-11 02:40:13 status: active source_of_truth: false freshness: current last_reviewed: 2026-11-11 tags: - pack/paperclip-harness - agent-memory/session - autolearn - rich-discovery - repo/pause

Rich discovery: pause 2026-11-11 02:40:13

Sanitized rich discovery snapshot captured automatically from the completed turn.

Source paths observed

pause/resume/wake

Final answer snapshot

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:

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.
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.
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.
Start a review from Work>review — v runs bin/review <task> --post in the background, tab follows the log, exactly as merge does now.
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.
Board>needs acting on a card — unblock, assign, open in Reply, from the card itself.
Spend chart in Project>overview, in Go, next to the runs sparkline.
Memory per agent — read-only row showing whether an agent uses engram or headroom, before any switch.
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: 86%
Reason: Preserve full sanitized discovery detail from a rich investigation turn

packs/paperclip-harness/00-system/pi-agent/memory-manifest

4.1 KiB Raw Blame History