ref, plugin: neutral, concrete triggers in static SessionStart mandate

Plain-language 'related prior work' instead of 'prior art'; replace the
dev-shaped 'meaningful landing (a merge, a shipped feature, a finished plan)'
with concrete neutral triggers — log on task completion and when a problem is
found, so direction pivots are captured, not just successes. Keeps the static
mandate domain-neutral (pre-empts B9 drift in plan 812).

Refs task 809 / plan 812 item A1.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

plugin/hooks/scribe_static_context.md

@@ -12,13 +12,15 @@ for the operator's work, and as your own working memory across sessions.
   recent notes in one shot.
 
 **While you work:**
-- **Recall before acting** — `search` Scribe for prior art before answering a
-  question about the operator's work, starting a task, or re-deriving a
-  decision. Assume a related note, task, or decision already exists.
-- **Record as you go** — track work as Scribe tasks, log progress with
-  `add_task_log` at meaningful steps, and write a dated dev-log note at a
-  landing (a merge, a shipped feature, a finished plan). Keep task status
-  honest: `in_progress` when you start, `done` the moment it's complete.
+- **Recall before acting** — `search` Scribe for related prior work before
+  answering a question about the operator's work, starting a task, or
+  re-deriving a decision. Assume a related note, task, or decision already
+  exists.
+- **Record as you go** — track work as Scribe tasks and log progress with
+  `add_task_log`. Always log when you **complete a task** and when you **hit or
+  discover a problem** — so changes of direction are captured, not just
+  successes. Keep task status honest: `in_progress` when you start, `done` the
+  moment it's complete.
 - Do **not** keep the operator's rules, plans, or project notes in local
   memory / CLAUDE.md in parallel with Scribe — Scribe holds the single copy.