Cleanup confirms and refreshes; projects switch sessions in place; explain verify.sh, headroom and Mouse-1

This commit is contained in:
Sam
2026-11-11 15:57:42 +11:00
parent 36abdc1f84
commit e02b39943d
13 changed files with 662 additions and 7 deletions

View File

@@ -0,0 +1,92 @@
---
type: observation
id: observation.paperclip-harness.paperclip-harness-cleanup-navigation-and-ui-conventions
title: paperclip-harness cleanup/navigation and UI conventions
status: active
source_of_truth: false
freshness: current
last_reviewed: 2026-11-11
tags:
- pack/paperclip-harness
- agent-memory/observation
- paperclip-harness
- ui-conventions
- safety
- office
---
# paperclip-harness cleanup/navigation and UI conventions
paperclip-harness tabular list conventions (from cleanup column and costs work):
- List selection is rendered with '▸' on the current row; ticked/selected-for-action rows show '*'.
- Navigation keys ↑/↓ move list selection, not body scroll; space toggles tick; x acts (closes ticked items after confirmation).
- Destructive actions must refuse protected sessions and attached/on-another-machine sessions, printing an explanatory line rather than failing silently.
- Cost bars scale to the largest spender and reuse already-fetched numbers; avoid new API calls for display-only features.
- bin/office adoption semantics: only create missing files (.harness/verify.sh, .harness/NOTES.md); never overwrite existing ones.
- Agents>settings should only state what it has read (extensions + memory from agent command/global Pi settings), not infer choices.
## Detailed observations from completed turn
The cleanup column navigates now, and the remaining list is finished except the one item that needs a decision from you.
## Cleanup navigation
The bug was that `↑`/`↓` scrolled the body, never the selection. They now move through the list, the chosen row shows `▸`, and a ticked row shows `*`:
```
session panes last used state
▸ paperclip-harness 10 11 Nov 15:04 this project's session
tuios coding harness 4 11 Nov 15:03 attached, or on another machine
* office-test-1 26 10 Nov 11:24 ticked for closing
```
`space` ticks, `x` closes the ticked ones after asking, and protected or attached sessions are refused with a line saying why.
## The rest of the list
**7. Costs as a chart** — `Project>costs` now draws each task's spend against the largest, using the figures already loaded, so no extra API calls:
```
task state cents runs share of the largest
AUD-163 done 3 3 ████████████████████████
AUD-164 done 2 2 ████████████████
AUD-159 done 1 1 ████████
```
**5. The `office` scaffold** — `bin/office` now writes what is missing, never overwriting: `.harness/verify.sh` (with a comment explaining how to replace it, and what happens if you do not) and `.harness/NOTES.md` for the person. Adopting a folder no longer leaves it without a place to say what "finished" means.
**8. Memory per agent, read-only** — `Agents>settings` ends with a line read from the agent's command and the global Pi settings:
```
memory and extensions
extensions: the global set · memory: pi-memctx
```
It states only what it has read. When you want to decide which agent uses engram or headroom, that line is where the answer will go — but the switch itself needs your input on what "using headroom" should mean for an agent that runs for ninety seconds.
## What is left, honestly
- **MOUSE-1** — key present, software not installed. Policy from the old project stands: triage only, never a gate. It needs the software before it needs a screen.
- **Switching projects** — the list is there; actually switching means tearing down these panes and building another project's, and a project on `.27` cannot be opened from `.13` at all. That is a design decision for you, not a missing key.
- **Memory switches** — awaiting your call on what they control.
Everything else in `docs/NEXT.md` is now marked done. Committed as `36abdc1`; the eight workspaces were rebuilt and are running on the new build.
## Evidence
- Confidence: 85%
- Reason: Durable UI and safety conventions evidenced by the implemented behavior.; enriched with final-answer detail because persistence should be reusable
## Related
- [[packs/paperclip-harness/00-system/pi-agent/memory-manifest|Memory Manifest]]
## Related learned memories <!-- same-turn-2026-11-11 04:06:03 -->
- observation: [[packs/paperclip-harness/60-observations/paperclip-harness-cleanup-navigation-and-ui-conventions|paperclip-harness cleanup/navigation and UI conventions]]
- decision: [[packs/paperclip-harness/50-decisions/paperclip-harness-ui-six-workspaces-spec-first-four-panel-li|Deferred agent memory switch (engram vs headroom) pending user definition]]
- action: [[packs/paperclip-harness/40-actions/2026-11-10-wrote-docs-ui-layout-md-and-three-live-layout-mockups|Implemented cleanup navigation, cost bars, office scaffold, and per-agent memory read-out (commit 36abdc1)]]
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-cleanup-column-navigation-fix-cost-bars-of|paperclip-harness: cleanup-column navigation fix, cost bars, office scaffold, per-agent memory line]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-omni-2026-11-11-04-06-03|Rich discovery: omni 2026-11-11 04:06:03]]
- context: [[packs/paperclip-harness/20-context/omni|omni]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|omni repository structure and configuration patterns]]

View File

@@ -2746,3 +2746,74 @@ Committed as `3ec960e`; `docs/NEXT.md` updated with what is done and what remain
- context: [[packs/paperclip-harness/20-context/config|.config]]
- runbook: [[packs/paperclip-harness/70-runbooks/tmp-deployment-operations|.config deployment operations]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|.config repository structure and configuration patterns]]
---
## Update (2026-11-11 04:06:03)
## Structural/configuration observations (2026-11-11 04:06:03)
The cleanup column navigates now, and the remaining list is finished except the one item that needs a decision from you.
## Cleanup navigation
The bug was that `↑`/`↓` scrolled the body, never the selection. They now move through the list, the chosen row shows `▸`, and a ticked row shows `*`:
```
session panes last used state
▸ paperclip-harness 10 11 Nov 15:04 this project's session
tuios coding harness 4 11 Nov 15:03 attached, or on another machine
* office-test-1 26 10 Nov 11:24 ticked for closing
```
`space` ticks, `x` closes the ticked ones after asking, and protected or attached sessions are refused with a line saying why.
## The rest of the list
**7. Costs as a chart** — `Project>costs` now draws each task's spend against the largest, using the figures already loaded, so no extra API calls:
```
task state cents runs share of the largest
AUD-163 done 3 3 ████████████████████████
AUD-164 done 2 2 ████████████████
AUD-159 done 1 1 ████████
```
**5. The `office` scaffold** — `bin/office` now writes what is missing, never overwriting: `.harness/verify.sh` (with a comment explaining how to replace it, and what happens if you do not) and `.harness/NOTES.md` for the person. Adopting a folder no longer leaves it without a place to say what "finished" means.
**8. Memory per agent, read-only** — `Agents>settings` ends with a line read from the agent's command and the global Pi settings:
```
memory and extensions
extensions: the global set · memory: pi-memctx
```
It states only what it has read. When you want to decide which agent uses engram or headroom, that line is where the answer will go — but the switch itself needs your input on what "using headroom" should mean for an agent that runs for ninety seconds.
## What is left, honestly
- **MOUSE-1** — key present, software not installed. Policy from the old project stands: triage only, never a gate. It needs the software before it needs a screen.
- **Switching projects** — the list is there; actually switching means tearing down these panes and building another project's, and a project on `.27` cannot be opened from `.13` at all. That is a design decision for you, not a missing key.
- **Memory switches** — awaiting your call on what they control.
Everything else in `docs/NEXT.md` is now marked done. Committed as `36abdc1`; the eight workspaces were rebuilt and are running on the new build.
## Source paths observed
- `omni/deepseek/deepseek-v4-flash`
## Evidence
- Confidence: 82%
- Reason: Captured factual repo structure/configuration patterns from rich discovery
## Related learned memories <!-- same-turn-2026-11-11 04:06:03 -->
- observation: [[packs/paperclip-harness/60-observations/paperclip-harness-cleanup-navigation-and-ui-conventions|paperclip-harness cleanup/navigation and UI conventions]]
- decision: [[packs/paperclip-harness/50-decisions/paperclip-harness-ui-six-workspaces-spec-first-four-panel-li|Deferred agent memory switch (engram vs headroom) pending user definition]]
- action: [[packs/paperclip-harness/40-actions/2026-11-10-wrote-docs-ui-layout-md-and-three-live-layout-mockups|Implemented cleanup navigation, cost bars, office scaffold, and per-agent memory read-out (commit 36abdc1)]]
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-cleanup-column-navigation-fix-cost-bars-of|paperclip-harness: cleanup-column navigation fix, cost bars, office scaffold, per-agent memory line]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-omni-2026-11-11-04-06-03|Rich discovery: omni 2026-11-11 04:06:03]]
- context: [[packs/paperclip-harness/20-context/omni|omni]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|omni repository structure and configuration patterns]]