20 lines
1.2 KiB
Markdown
20 lines
1.2 KiB
Markdown
# Recorded human decisions in run detail
|
|
|
|
RunDecisionNotice reuses pendingDecision and HumanDecisionAction. A standard
|
|
Material card or Cupertino section names the recorded checkpoint and offers
|
|
Decide. The existing native prompt owns option/feedback/confirmation/refusal
|
|
semantics; export/resource waits do not become invented human checkpoints.
|
|
Accepted server detail flows through the same lifecycle/list update as Cancel.
|
|
|
|
New actual-screen tests failed before wiring and now pass on both hosts: recorded
|
|
instructions, selection sends nothing, exact run/stage/option and trimmed feedback
|
|
only on confirmation, accepted result removes the card. Integrated614 tests pass;
|
|
analysis and normal web build are clean.
|
|
|
|
Real normal-app browser fixture passes28 captures, including actual Cupertino
|
|
waiting card and prompt, Material card/prompt/accepted result, Cancel/Keep and
|
|
the existing history/reconnect/Settings checks. The fixture records one exact
|
|
decide_run for its synthetic run5; opening/Cancel send nothing. Card and prompt
|
|
PNGs inspected in approved temp/decision-wired-browser. No production decision
|
|
was answered; mobile and live authenticated mutations remain unverified.
|