Run outcomes, score, explicit exercise recording, and step captures (RBT-WP-0004-T13)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 295952@bnt-lap001
Assistant-Session: e93f64ad-516c-46eb-9666-aad8d300c477

workplans/RBT-WP-0004-local-runbook-ui.md

@@ -177,6 +177,23 @@ Done 2026-09-29: after "All steps done." the run view offers three smileys and a
 latest wins, secrets refused); `rtut feedback <pack.yaml>` lists the latest per run.
 Follow-up: fold feedback into the overview and use it to prioritize pack refinements.
 
+## Run outcome, score, exercise recording and captures
+
+```task
+id: RBT-WP-0004-T13
+status: done
+priority: high
+```
+
+Done 2026-09-29 from Bernd's review: runs are finalized as succeeded, failed or abandoned
+(stale open runs count as abandoned after 7 days); a runbook's score (tried, succeeded, failed,
+abandoned, open, feedback tally) is shown in the list and on the pack page, with a list of its
+runs; finalizing a succeeded run offers an explicit "Record pack as exercised" that shows the
+change before writing it to `pack.yaml`; steps can capture the command run and its output, and
+`output-contains` checks can be verified against pasted output. Documented in `docs/run-spec.md`.
+Open: run histories are per machine (`.local/`), so a shared or committed history is still
+to be decided.
+
 ## Acceptance Criteria
 
 - Bernd can complete the SSH tutorial pack in the UI without pasting outputs to an agent.