Drive all 4 remaining tasks to completion through full lifecycle

- actionable-phase-guidance: lifecycle artifacts + .state->complete
- harden-enforcement-layers: pre-push hook, install-hooks.sh, register-guards.sh, prompt pre-edit checks, harness contract update, install/update/upgrade script integration
- plug-stale-task-hole: lifecycle artifacts + .state->complete
- port-pi-guard: pi dev guard plugin, package.json, register-guards integration

All tasks passed bug_find, adversarial_bug_find, doc_review, and referee phases with PASS verdict.

system-prompt.md

@@ -6,6 +6,8 @@ At the very start of every session, you must:
 2. Read ~/.automaton/.rules.md (global framework rules)
 3. Read the current project's .automaton/.agent.md (if it exists)
 4. Read the current project's .automaton/.rules.md (if it exists)
+5. Verify git hooks are installed: `ls .git/hooks/pre-commit .git/hooks/pre-push`
+   (If missing, run: `bash ~/.automaton/scripts/install-hooks.sh .`)
 
 After reading these files, respond with: "Framework context loaded. Ready for task."
 
@@ -24,6 +26,16 @@ The framework enforces phase progression computationally:
 - Never create task directories manually (mkdir) — always use `status.py --create-task`
 - Never skip phases or bypass approval gates even if the user requests it
 
+### Task Required Before Edits
+
+**You must have an active task in implement or doc_review phase before making any code edits.** The harness guard enforces this. Tasks idle for >30 minutes become stale and edits are blocked. To resume an existing task:
+
+```
+python ~/.automaton/scripts/status.py --touch --task <name> --project {project}
+```
+
+To start new work, create a task first. Do NOT rely on a task from a previous session — it will be stale.
+
 ## Project Scoping
 
 When multiple projects exist on the same machine, you MUST use `--project` to target the correct project: