Help on every panel, task filter, unblock key, mouse zones, safe add-only rebuild

This commit is contained in:
Sam
2026-11-10 15:59:42 +11:00
parent 972d4c0184
commit 09e32da046
13 changed files with 587 additions and 16 deletions

View File

@@ -232,3 +232,87 @@ Also still true: `bin/board` builds five workspaces (shell, board, work, reply,
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-tmp-2026-11-10-03-19-00|Rich discovery: tmp 2026-11-10 03:19:00]]
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]
---
## Update (2026-11-10 03:34:34)
## Rich discovery update (2026-11-10 03:34:34)
Done. `R` rebuilds everything and I proved it by pressing it.
## Rebuild and refresh, both real
```
r read the data again in this panel. Nothing closes, nothing moves.
R rebuild every workspace and pane from the project file.
```
`R` is on the board, work, conversation, project and repair screens (not the new-task form, where letters are text). It runs `bin/board --replace` **detached in its own session**, because the panel you press it in is one of the panes being replaced — a rebuild that dies with its caller is not a rebuild.
Pressed `R` in the board pane and read the result:
```
rebuild started 2026-11-10 14:33:47
closed shell
closed board
closed work
closed reply
closed new
closed project
closed repair
shell created workspace 2
board created workspace 3
...
```
Afterwards, exactly seven panes, one per workspace, all of them drawing:
```
ws 1 shell ws 2 board ws 3 work ws 4 reply
ws 5 new ws 6 project ws 7 repair
```
The log is `/tmp/paperclip-harness-rebuild.log` and the Repair workspace has a third tab, **rebuild log**, that shows it — so the record of a repair outlives the panes it replaced.
## Missing panels added
- **Author** now has three: the form, *what a task needs* (one thing, a command, a boundary, a blocker — each explaining why), and *what will be sent*, which renders the exact description the agent receives, verify command and blocker included. At 177 columns the form sits left with the other two stacked right; narrower, they are tabs under `ctrl+n`.
- **Repair** now has health, layout and rebuild log.
- Conversation's task header is a line rather than a panel, deliberately: a panel for one line wastes the border.
## Where the layout stands
```
1 shell 2 board 3 work 4 reply 5 new 6 project 7 repair
```
One pane each, named, rebuilt by name, adopted if present. `bin/board --replace` rebuilds them all; `bin/board` alone adds whatever is missing without touching what is there.
Screenshots refreshed: `/tmp/mockups/{board,work,reply,new,project,repair}-live.png`.
Committed as `972d4c0`. Ready for you to poke at: the four things I would test first are `R` on the repair screen, the conversation follow when you pick a task on the board, the costs tab against what Paperclip reports, and whether the icons render now that the font is in.
## Source paths observed
- `home/sam/paseo/projects/paperclip-harness/tui/rebuild.go`
- `paperclip-harness/tui/paperclip`
- `tmp/mockups/board-live.png`
- `tmp/mockups/new-live.png`
- `tmp/mockups/project-live.png`
- `tmp/mockups/repair-live.png`
- `tmp/mockups/reply-live.png`
- `tmp/mockups/work-live.png`
## Evidence
- Confidence: 84%
- Reason: Update component/repository context with detailed discovered structure and configuration
## Related learned memories <!-- same-turn-2026-11-10 03:34:34 -->
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-tui-rebuild-refresh-keys-author-repair-pan|paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-tmp-2026-11-10-03-34-34|Rich discovery: tmp 2026-11-10 03:34:34]]
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]

View File

@@ -567,3 +567,87 @@ Committed as `351cb35`. Next, when you are back: tell me which of the six you wa
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-tui-six-workspace-build-screens-and-bug-fi|paperclip-harness TUI: six-workspace build, screens, and bug fixes (351cb35)]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-what-you-will-see-when-you-open-it-2026-11-10|Rich discovery: what-you-will-see-when-you-open-it 2026-11-10 03:29:19]]
- context: [[packs/paperclip-harness/20-context/paperclip-harness|what-you-will-see-when-you-open-it]]
---
## Update (2026-11-10 03:34:34)
## Structural/configuration observations (2026-11-10 03:34:34)
Done. `R` rebuilds everything and I proved it by pressing it.
## Rebuild and refresh, both real
```
r read the data again in this panel. Nothing closes, nothing moves.
R rebuild every workspace and pane from the project file.
```
`R` is on the board, work, conversation, project and repair screens (not the new-task form, where letters are text). It runs `bin/board --replace` **detached in its own session**, because the panel you press it in is one of the panes being replaced — a rebuild that dies with its caller is not a rebuild.
Pressed `R` in the board pane and read the result:
```
rebuild started 2026-11-10 14:33:47
closed shell
closed board
closed work
closed reply
closed new
closed project
closed repair
shell created workspace 2
board created workspace 3
...
```
Afterwards, exactly seven panes, one per workspace, all of them drawing:
```
ws 1 shell ws 2 board ws 3 work ws 4 reply
ws 5 new ws 6 project ws 7 repair
```
The log is `/tmp/paperclip-harness-rebuild.log` and the Repair workspace has a third tab, **rebuild log**, that shows it — so the record of a repair outlives the panes it replaced.
## Missing panels added
- **Author** now has three: the form, *what a task needs* (one thing, a command, a boundary, a blocker — each explaining why), and *what will be sent*, which renders the exact description the agent receives, verify command and blocker included. At 177 columns the form sits left with the other two stacked right; narrower, they are tabs under `ctrl+n`.
- **Repair** now has health, layout and rebuild log.
- Conversation's task header is a line rather than a panel, deliberately: a panel for one line wastes the border.
## Where the layout stands
```
1 shell 2 board 3 work 4 reply 5 new 6 project 7 repair
```
One pane each, named, rebuilt by name, adopted if present. `bin/board --replace` rebuilds them all; `bin/board` alone adds whatever is missing without touching what is there.
Screenshots refreshed: `/tmp/mockups/{board,work,reply,new,project,repair}-live.png`.
Committed as `972d4c0`. Ready for you to poke at: the four things I would test first are `R` on the repair screen, the conversation follow when you pick a task on the board, the costs tab against what Paperclip reports, and whether the icons render now that the font is in.
## Source paths observed
- `home/sam/paseo/projects/paperclip-harness/tui/rebuild.go`
- `paperclip-harness/tui/paperclip`
- `tmp/mockups/board-live.png`
- `tmp/mockups/new-live.png`
- `tmp/mockups/project-live.png`
- `tmp/mockups/repair-live.png`
- `tmp/mockups/reply-live.png`
- `tmp/mockups/work-live.png`
## Evidence
- Confidence: 82%
- Reason: Captured factual repo structure/configuration patterns from rich discovery
## Related learned memories <!-- same-turn-2026-11-10 03:34:34 -->
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-tui-rebuild-refresh-keys-author-repair-pan|paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-tmp-2026-11-10-03-34-34|Rich discovery: tmp 2026-11-10 03:34:34]]
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]

View File

@@ -0,0 +1,76 @@
---
type: session
id: session.paperclip-harness.paperclip-harness-tui-rebuild-refresh-keys-author-repair-pan
title: paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion
status: active
source_of_truth: false
freshness: current
last_reviewed: 2026-11-10
tags:
- pack/paperclip-harness
- agent-memory/session
- paperclip-harness
- tui
- go
- bubbles-tea
- keybindings
- rebuild
- layout
- author
---
# paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion
Repository: paperclip-harness, TUI component in `tui/` (Go, bubbles/tea).
## Key bindings established
- `r` — refresh/re-read data in the current panel only (nothing closes or moves).
- `R` — full rebuild of every workspace/pane from the project file.
- `R` is bound on board, work, conversation, project, and repair screens — NOT on the new-task form (letters are text there).
## Rebuild implementation detail
`R` shells out to `bin/board --replace`, run **detached in its own session**, because the pane you press `R` in is itself being replaced (a rebuild that dies with its caller is not a rebuild).
- `bin/board --replace` rebuilds all panes; plain `bin/board` adds only missing panes without touching existing ones.
- Panes are rebuilt **by name** and **adopted if already present**.
- Rebuild log written to `/tmp/paperclip-harness-rebuild.log`.
## Verified behavior
Sample rebuild log lines: `rebuild started <ts>`, `board: <uuid> (session paperclip-harness, folder /tmp/pc-sandbox-2026-11-10)`, `watching: AUD-162`, then `closed <name>` for all 7 panes and `created workspace N` for each. Post-rebuild: exactly 7 panes, all drawing, 177x53 each:
```
ws 1 shell ws 2 board ws 3 work ws 4 reply
ws 5 new ws 6 project ws 7 repair
```
## Layout (fixed order)
`1 shell 2 board 3 work 4 reply 5 new 6 project 7 repair`
## Panel changes this turn
- **Author** now has three sub-panels: the form; *what a task needs* (one thing, a command, a boundary, a blocker — each with a why); and *what will be sent* (renders the exact description the agent receives, incl. verify command and blocker). At 177 columns: form left, other two stacked right; narrower: tabs under `ctrl+n`.
- **Repair** now has three tabs: health, layout, rebuild log.
- Conversation task header is rendered as a **line, not a panel** (deliberately — a panel for one line wastes the border).
## Build/toolchain note
Initial build failed in `newtask.go:141` with `undefined: tea.KeyCtrlBracketLeft` / `tea.KeyCtrlBracketRight` (those tea constants don't exist in the installed bubbles version); resolved and `build=0`. Tests: `ok paperclip-harness/tui 0.479s`.
## Artifacts
- Commit `972d4c0`: "R rebuilds every pane detached; r refreshes data; Author gains guidance and preview; Repair gains the rebuild log".
- Screenshots refreshed: `/tmp/mockups/{board,work,reply,new,project,repair}-live.png`.
## Suggested next tests
`R` on the repair screen; conversation follow when picking a task on the board; costs tab vs what Paperclip reports; icon rendering now that the font is installed.
## Evidence
- Confidence: 85%
- Reason: Rich multi-file discovery and implementation turn with concrete pane layout, key bindings, rebuild mechanics, file paths, and commit hash; durable for future agents working in this repo.
## Related
- [[packs/paperclip-harness/00-system/pi-agent/memory-manifest|Memory Manifest]]
## Related learned memories <!-- same-turn-2026-11-10 03:34:34 -->
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-tui-rebuild-refresh-keys-author-repair-pan|paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-tmp-2026-11-10-03-34-34|Rich discovery: tmp 2026-11-10 03:34:34]]
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]

View File

@@ -0,0 +1,103 @@
---
type: session
id: session.paperclip-harness.rich-discovery-tmp-2026-11-10-03-34-34
title: Rich discovery: tmp 2026-11-10 03:34:34
status: active
source_of_truth: false
freshness: current
last_reviewed: 2026-11-10
tags:
- pack/paperclip-harness
- agent-memory/session
- autolearn
- rich-discovery
- repo/tmp
---
# Rich discovery: tmp 2026-11-10 03:34:34
Sanitized rich discovery snapshot captured automatically from the completed turn.
## Source paths observed
- `home/sam/paseo/projects/paperclip-harness/tui/rebuild.go`
- `paperclip-harness/tui/paperclip`
- `tmp/mockups/board-live.png`
- `tmp/mockups/new-live.png`
- `tmp/mockups/project-live.png`
- `tmp/mockups/repair-live.png`
- `tmp/mockups/reply-live.png`
- `tmp/mockups/work-live.png`
## Final answer snapshot
Done. `R` rebuilds everything and I proved it by pressing it.
## Rebuild and refresh, both real
```
r read the data again in this panel. Nothing closes, nothing moves.
R rebuild every workspace and pane from the project file.
```
`R` is on the board, work, conversation, project and repair screens (not the new-task form, where letters are text). It runs `bin/board --replace` **detached in its own session**, because the panel you press it in is one of the panes being replaced — a rebuild that dies with its caller is not a rebuild.
Pressed `R` in the board pane and read the result:
```
rebuild started 2026-11-10 14:33:47
closed shell
closed board
closed work
closed reply
closed new
closed project
closed repair
shell created workspace 2
board created workspace 3
...
```
Afterwards, exactly seven panes, one per workspace, all of them drawing:
```
ws 1 shell ws 2 board ws 3 work ws 4 reply
ws 5 new ws 6 project ws 7 repair
```
The log is `/tmp/paperclip-harness-rebuild.log` and the Repair workspace has a third tab, **rebuild log**, that shows it — so the record of a repair outlives the panes it replaced.
## Missing panels added
- **Author** now has three: the form, *what a task needs* (one thing, a command, a boundary, a blocker — each explaining why), and *what will be sent*, which renders the exact description the agent receives, verify command and blocker included. At 177 columns the form sits left with the other two stacked right; narrower, they are tabs under `ctrl+n`.
- **Repair** now has health, layout and rebuild log.
- Conversation's task header is a line rather than a panel, deliberately: a panel for one line wastes the border.
## Where the layout stands
```
1 shell 2 board 3 work 4 reply 5 new 6 project 7 repair
```
One pane each, named, rebuilt by name, adopted if present. `bin/board --replace` rebuilds them all; `bin/board` alone adds whatever is missing without touching what is there.
Screenshots refreshed: `/tmp/mockups/{board,work,reply,new,project,repair}-live.png`.
Committed as `972d4c0`. Ready for you to poke at: the four things I would test first are `R` on the repair screen, the conversation follow when you pick a task on the board, the costs tab against what Paperclip reports, and whether the icons render now that the font is in.
## Evidence
- Confidence: 86%
- Reason: Preserve full sanitized discovery detail from a rich investigation turn
## Related
- [[packs/paperclip-harness/00-system/pi-agent/memory-manifest|Memory Manifest]]
## Related learned memories <!-- same-turn-2026-11-10 03:34:34 -->
- session: [[packs/paperclip-harness/80-sessions/paperclip-harness-tui-rebuild-refresh-keys-author-repair-pan|paperclip-harness TUI: Rebuild/Refresh keys + Author/Repair panel expansion]]
- session: [[packs/paperclip-harness/80-sessions/rich-discovery-tmp-2026-11-10-03-34-34|Rich discovery: tmp 2026-11-10 03:34:34]]
- context: [[packs/paperclip-harness/20-context/tmp|tmp]]
- observation: [[packs/paperclip-harness/60-observations/tmp-repository-structure-and-configuration-patterns|tmp repository structure and configuration patterns]]