docs: record long-task governor verification workflow
This commit is contained in:
@@ -76,6 +76,20 @@ If using `scripts/long_task_governor_wrapper.mjs`, map wrapper output into this
|
||||
- **externalized_trigger**: cron reminder / forced checkpoint
|
||||
- **final_handoff_path**: Telegram button-path only if owner judgement is needed; otherwise direct summary
|
||||
|
||||
## Verification notes
|
||||
|
||||
For this slice, keep verification short and explicit:
|
||||
- **wrapper fixture runner**: `node scripts/long_task_governor_wrapper_fixture_runner.mjs`
|
||||
- **force-recall smoke test**: `node scripts/long_task_governor_force_recall_smoke.mjs`
|
||||
- capture the output in task notes when this launch template or its linked workflow changes
|
||||
|
||||
## Current non-goals
|
||||
|
||||
This template does not yet imply or provision:
|
||||
- auto-send messages
|
||||
- bound cron / reminder wiring
|
||||
- gateway-level blocking or hard enforcement beyond the current preflight wording
|
||||
|
||||
## Rule of use
|
||||
|
||||
If you cannot fill this template honestly, the task is probably not ready to launch in silent mode.
|
||||
|
||||
Reference in New Issue
Block a user