35 lines
1.9 KiB
Markdown
35 lines
1.9 KiB
Markdown
# Open issues in the old project (for reference, not to fix now)
|
|
|
|
These belong to `~/paseo/harness` and `~/paseo/projects/tuios_coding_harness`. They are
|
|
recorded so that nothing is lost if you go back, and so the new project does not repeat
|
|
them.
|
|
|
|
## Known broken or unfinished
|
|
|
|
- The task pane's check is not the check that was approved: the run still falls back to
|
|
guessing a test command, so a "pass" can mean "detection said so".
|
|
- Two implementations of the same jobs existed (approval, viewer, task starter, cards).
|
|
They disagreed, which produced repeated faults.
|
|
- A plan re-run re-planned itself and lost its dependencies.
|
|
- Task state was matched by folder-name similarity rather than by the task's own record.
|
|
- `bin/home`'s per-task list is view-only; starting a single task is blocked by
|
|
dependencies being absent from the stored plan.
|
|
- Worktree/merge/review path (`ocr`, serial merge) exists in pieces but has never run end
|
|
to end.
|
|
- Redaction of secrets on outbound provider requests is built but not connected.
|
|
- Mouse-1 is used only for routing failures; intake scoring was never built.
|
|
- Grid layout (50/50 by pane count) was deferred by you and never done.
|
|
- Session creation in TUIOS cannot be scripted: `tuios new` needs a terminal.
|
|
- Subagent models in this environment fail with a 404 (`claude-haiku-4.5` unavailable), so
|
|
delegated research silently returns nothing.
|
|
- The page notes and layout are correct as documents, but the layout has been lost twice
|
|
to TUIOS renumbering; repair now carries the project, but it is lightly tested.
|
|
|
|
## Decisions in the old project that are still good
|
|
|
|
- Approvals must be content-bound (a changed plan cannot ride an old approval).
|
|
- A task is finished when a command says so, not when an agent says so.
|
|
- One writer per fact; the queue belongs to the coordination layer.
|
|
- Untrusted repository text is data, never instructions.
|
|
- A secret must not leave the machine; redaction belongs on the request, not in a prompt.
|