feat(context): reasoning-thread continuity, L3 doc filtering, and gate hardening

Threads reasoning_content across inference calls and journal renders, filters
markdown noise out of L3 repo-knowledge retrieval, adds PlanLinter H3 checks,
and tightens filesystem tool output/dir-listing behavior surfaced by prior
live QA (see project_readloop_campaign memory).

examples/workflows/prompts/task_planner.md

@@ -36,6 +36,12 @@ For `task_decompose`, provide:
   `affected_paths` (workspace-relative globs), and `depends_on` (refs to other tasks in this batch
   that must finish first).
 
+  **`affected_paths` globs must cover subdirectories recursively.** Use `**/*.tsx` instead of
+  `*.tsx`, `**/*.py` instead of `*.py`, etc. Sweep the actual directory tree with `list_dir` or
+  `shell find` before setting paths — if the target tree has subdirectories (e.g.
+  `components/ui/`, `components/layout/`), a non-recursive glob will jail the implementer to
+  only the top level and block writes to the real file locations.
+
 Keep the graph small. Over-splitting is worse than under-splitting — a session works one task at a
 time, and each child is a future claim. Aim for 2–5 children unless the request genuinely demands
 more.