Add lighthouse showcase pack (v0.1 runnable, v0.2 draft); fix manual-check cycle and blocked-step feedback (RBT-WP-0004-T05)
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
This commit is contained in:
parent
f9fb9008bf
commit
b47c948a7e
8 changed files with 387 additions and 12 deletions
|
|
@ -95,6 +95,21 @@ state_hub_task_id: "dae5a6fe-9f1f-553a-8b73-f47ab6d91b59"
|
|||
Port the four validating packs to v0.2 where it helps, and add v0.2 test packs with
|
||||
alternatives, gates and actors.
|
||||
|
||||
## Showcase pack as acceptance test
|
||||
|
||||
```task
|
||||
id: RBT-WP-0002-T07
|
||||
status: progress
|
||||
priority: medium
|
||||
```
|
||||
|
||||
`runbooks/showcase-lighthouse/` is a harmless interactive-fiction runbook (poem, story,
|
||||
scratch logbook under /tmp/rtut-*). `pack.yaml` (v0.1) runs today and is the test bed for
|
||||
UI refinement. `pack.v0.2.draft.yaml` expresses the same story in the proposed v0.2 model
|
||||
(stages, parallel steps, alternatives, gates, actors, datapoints, artefacts, irreversible
|
||||
confirmation). The draft is checked for internal consistency by tests. When v0.2 is adopted
|
||||
the validator must accept it unchanged, or the proposal changes.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- Every pack in this repo and in `net-kingdom` validates.
|
||||
|
|
|
|||
|
|
@ -73,12 +73,12 @@ diff from RBT-WP-0003-T04.
|
|||
|
||||
```task
|
||||
id: RBT-WP-0004-T05
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "d635f972-0377-5581-a8fe-c01ef89559cd"
|
||||
```
|
||||
|
||||
Defects found in review: a ticked manual check shows "passed" while the step stays
|
||||
Done 2026-09-29 against the lighthouse showcase (tested over HTTP; a browser pass by Bernd is still the real check). Defects found in review: a ticked manual check shows "passed" while the step stays
|
||||
`running`, and unticking changes nothing; blocked steps show no Start button and no
|
||||
reason. Make the cycle explicit (check, record, mark done), and show what a blocked
|
||||
step is waiting for.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue