docs: preserve Confidence Engine methodology continuity

docs/task-context-packs.md

@@ -5,11 +5,15 @@
 ## Pack 1 — Engine Experiment Work
 
 ### Always read
-- `docs/current-project-state.md`
+- `docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md` (methodology continuity — required before any reasoning development)
+- `docs/current-handoff.md` (current state, Git checkpoint, experiment log)
 - `docs/current-working-principles.md`
 - `.claude/architecture-guardrails.md`
 - `docs/current-implementation-verification.md`
 
+### First document to read for Confidence Engine reasoning work:
+**`docs/Confidence_Engine_Return_to_Origin_Methodology_Context_2026-08-18.md`** — the durable methodology anchor. Do not load experiment apparatus before this document. A new session must understand the method before examining recent technical experiments.
+
 ### Then read only when relevant
 - the specific implementation file;
 - its focused tests;
@@ -22,7 +26,8 @@
 ### Stop and ask or record a gap when
 - current documentation and source disagree;
 - the task requires an undocumented contract;
-- the experiment begins expanding into several capabilities.
+- the experiment begins expanding into several capabilities;
+- you cannot describe the reasoning operation in Confidence Engine methodology terms (could a trained human facilitator perform it without an LLM?).
 
 ### Live experiment execution route