diff --git a/docs/runbooks/silent-long-task-launch-template.md b/docs/runbooks/silent-long-task-launch-template.md
index ce6bbb7..2bd1a84 100644
--- a/docs/runbooks/silent-long-task-launch-template.md
+++ b/docs/runbooks/silent-long-task-launch-template.md
@@ -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.
diff --git a/skills/long-task-governor/SKILL.md b/skills/long-task-governor/SKILL.md
index c3ae63f..ad5f8c6 100644
--- a/skills/long-task-governor/SKILL.md
+++ b/skills/long-task-governor/SKILL.md
@@ -172,6 +172,20 @@ If using the wrapper MVP:
 - `silentLaunchOk = false` means you must not proceed as silent
 - `handoff.mode = button_path` means prepare Telegram button-path early
 
+### Verification notes for this slice
+
+Keep verification lightweight and reproducible:
+- **wrapper fixture runner**: run `node scripts/long_task_governor_wrapper_fixture_runner.mjs`
+- **force-recall smoke test**: run `node scripts/long_task_governor_force_recall_smoke.mjs`
+- record the command output in the task checkpoint or PR notes when this skill changes
+
+### Current non-goals for this slice
+
+This slice documents decisioning and preflight guidance only. It does **not** yet include:
+- auto-send messages
+- bound cron / reminder wiring
+- gateway-level blocking or hard enforcement beyond the current preflight wording
+
 ---
 
 ## 6. No-fake-progress rule