docs: clarify rehearsal evidence boundaries
This commit is contained in:
@@ -223,13 +223,14 @@ Then switch back to replay/deep-linked states.
|
||||
|
||||
| Path | Operator action | Expected evidence |
|
||||
|---|---|---|
|
||||
| Submitted | Select issue rows, enter a comment, choose `Submit`. | The same run ID reaches `submitted`, report Markdown, created issues, and a completed trace. |
|
||||
| Revision requested | Enter a revision comment, choose `Request revision`. | The same run ID shows `Revision requested` in the UI, protocol evidence remains `cancelled`, the report says `Revision Requested`, no issues are created, and the trace contains `revision_requested` followed by `end_cancelled`. |
|
||||
| Submitted | Select issue rows, enter a comment, choose `Submit`. | The prepared recording reaches `submitted` with run ID `run_recorded_lda_report`, report Markdown, a created issue, and a completed trace. |
|
||||
| Revision requested | Enter a revision comment, choose `Request revision`. | The prepared recording shows `Revision requested`, protocol evidence remains `cancelled`, the report says `Revision Requested`, no issues are created, and the trace contains `revision_requested` followed by `end_cancelled`. Current recording uses run ID `run_recorded_lda_report_revision`; do not describe it as the same run until that recording is corrected. |
|
||||
| Replay fallback | Stop the server or force replay before loading the presentation. | The replay badge and canonical operation, output, and trace evidence remain available without port debugging. |
|
||||
|
||||
`Request revision` is an intentional negative branch, not a terminal UI stop
|
||||
action. It resumes the same persisted run with an explicit negative decision
|
||||
and demonstrates the workflow's negative outcome.
|
||||
action. The live workflow contract resumes the persisted run with an explicit
|
||||
negative decision. The current prepared replay demonstrates the negative
|
||||
outcome with a separate recorded run identity, which is a known factual gap.
|
||||
|
||||
### If asked why the demo is prepared
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ rehearsal pass.
|
||||
|---|---|---|---|---|---|
|
||||
| PASS | 1280x720 | replay | `/present#scene/agent-handoff/request` | Open the request route and click `Send`. | The prepared conversation appears with the user request, assistant narration, and four discovery tool calls; no run is claimed. |
|
||||
| PASS | 1280x720, 1024x768 | replay | `/present#scene/typed-human-boundary/approval` | Open the approval route. | The input files, typed interrupt payload, proposed issue, resume comment, `Submit`, and `Request revision` controls are visible. The footer reports `Run paused - review required`. |
|
||||
| PASS | 1280x720 | replay | `/present#scene/prepared-lifecycle/{discover,draft,validate,artifact,deployment}` | Open each Scene 9 beat directly. | The phase rail advances through Discover, Draft, Validate, Artifact, and Deployment; staged chat groups and factual evidence change with each beat. |
|
||||
| PASS | 1280x720 | replay | `/present#scene/run-from-deployment/operation` | Open the Scene 10 operation beat. | `workflow.runs.start` is shown as interrupted with deployment, run ID, and `issue_review` boundary; the prepared-workflow action is available in the footer. |
|
||||
| PASS | 1280x720 | replay | Scene 11 -> Scene 12 | Click `Submit`. | The route changes to `resume`; the output shows `submitted`, `approved: true`, selected issue `risk-1`, and a created issue. |
|
||||
| FACTUAL | 1280x720 | replay | Scene 11 -> Scene 12 | Reload approval and click `Request revision`. | The route changes to `resume` and shows `cancelled`, `approved: false`, no selected issues, and a revision report. The replay uses `run_recorded_lda_report_revision`, so it does not preserve the submitted branch's run ID despite the same-run wording. |
|
||||
| PASS | 1280x720, 1024x768 | replay | `/present#scene/resume-output-evidence/trace` | Open the trace beat after the decision branches. | Recorded execution frames render, including `review_issues` interrupt/continuation and `end_cancelled`; the UI exposes the evidence inspector. |
|
||||
|
||||
Reference in New Issue
Block a user