fix(odd): synchronize visible todo projection

assets/orchestrator-memory.md

@@ -14,7 +14,7 @@ On resume, use `mem_context`, then project/feature-scoped `mem_search`, and `mem
 
 Before implementation or resume, the parent reads both the actual file and full observation, reconciles them, and passes the locator and relevant context; workers read the document before edits. Small work without a document still receives its authorized scope and checks.
 
-The existing `todo` tool is an optional session/UI projection, not a third authority. Rebuild it from reconciled feature progress when useful; its replay or completed-list clearing must not delete or replace the durable file or Engram copy. Small/read-only work does not acquire an ODD artifact merely because the UI displays tasks.
+The existing `todo` tool is the required session/UI projection for substantial ODD, not a third authority. After reconciling and writing the durable file and Engram copy, create or rebuild the visible `todo` list from the same feature tasks before the first source write; after every task transition and material plan change, update both durable copies and the visible projection in the same turn; its replay or completed-list clearing must not delete or replace the durable file or Engram copy. If the projection is unavailable, record that limitation without pretending it is synchronized. Small/read-only work does not acquire an ODD artifact or todo list merely because the UI can display tasks.
 
 ### SDD phases
 

extensions/gentle-ai.ts

@@ -1388,8 +1388,8 @@ Organic Driven Development (ODD) is the predefined workflow of this orchestrator
 2. **Explore.** Explore existing code and requirements first, proportionately to the request, before proposing or writing anything.
 3. **Resolve uncertainty.** Recommend optional research only for a named uncertainty; ask one focused user question only for a real unresolved product decision, then stop and wait; use at most one scoped read-only assumption challenge for a high-consequence unproven premise.
 4. **Classify.** The work is substantial when exploration yields two or more meaningful implementation steps, or progress worth recovering after an interruption. Small, understood work stays small and creates no durable task artifacts.
-5. **Track before the first write.** For substantial authorized implementation, create \`odd/tasks/<feature-name>.md\` and its Engram mirror \`odd/<feature-name>/tasks\` automatically, before the first source write, without asking permission for tasks or storage. Tell the user in one line which feature document was created and how many tasks it holds.
-6. **Implement task by task.** Route each task through the orchestrator's Work Routing Ladder, with the configured TDD mode and applicable checks. Check an item off only after its outcome and checks were observed; update the file and the mirror after each task.
+5. **Track before the first write.** For substantial authorized implementation, create \`odd/tasks/<feature-name>.md\` and its Engram mirror \`odd/<feature-name>/tasks\` automatically, then create or rebuild the visible \`todo\` list from the reconciled feature tasks, all before the first source write and without asking permission for tasks or storage. Tell the user in one line which feature document was created and how many tasks it holds.
+6. **Implement task by task.** Route each task through the orchestrator's Work Routing Ladder, with the configured TDD mode and applicable checks. Check an item off only after its outcome and checks were observed; update the file, mirror, and visible \`todo\` projection after every task transition and material plan change.
 7. **Close.** Report the verified outcome, every failed, skipped, or pending check, and the next step. Native review applies only at the deliverable boundary and only under the user-owned RDD switch.
 Resume an interrupted feature with \`mem_context\`, then project- and feature-scoped \`mem_search\`, then \`mem_get_observation\` for the full document, then the task file itself; reconcile before continuing the next unfinished task. Detail for steps 3–7: \`orchestrator-delegation.md\` and \`orchestrator-memory.md\`.
 

odd/tasks/odd-todo-and-thinking-visuals.md

@@ -0,0 +1,61 @@
+# Feature: ODD todo continuity and calm Thinking labels
+
+## Objective
+Keep Pi's visible `todo` list synchronized with every substantial ODD feature, and make collapsed `Thinking…` labels static pink instead of globally animated blue.
+
+## Problem / Why
+- ODD creates durable `odd/tasks/<feature>.md` and Engram progress, but the current contract calls the visible `todo` projection optional. The list can therefore remain absent or stale while work proceeds.
+- `pi-pretty` writes a global hidden-thinking label. Its best-effort per-row patch can miss the host's actual component class, causing every historical `Thinking…` row to animate. Its session-derived accent can also render blue instead of following Gentleman-Cute's rose palette.
+
+## Authorized scope
+- ODD orchestration contract and focused contract tests.
+- Gentle Pi's `pi-pretty` wrapper, Gentleman-Cute theme, and focused tests.
+- This feature document and its Engram mirror.
+- Preserve unrelated in-progress `sdd-trigger-boundary` edits.
+
+## Constraints
+- The feature file and Engram copy remain durable authorities; `todo` is the required session/UI projection for substantial ODD only.
+- Keep exactly one visible todo task `in_progress`; update it at task boundaries and whenever the plan changes.
+- Do not depend on Pi private component internals for per-row animation.
+- Preserve working/editor animation; disable only collapsed Thinking-label animation.
+- No commit, push, PR, release, or remote mutation.
+
+## Tasks
+- [x] **T1 — Make ODD todo projection mandatory.** Added RED contract assertions, then required creating/rebuilding the visible `todo` list when substantial ODD tracking starts and synchronizing it after every task/progress change.
+- [x] **T2 — Make Thinking labels static pink.** Added RED focused assertions, disabled `pi-pretty`'s global Thinking shimmer in the Gentle Shell wrapper without leaking environment state, and mapped Gentleman-Cute `thinkingText` to `softRose`.
+- [x] **T3 — Verify focused behavior.** ODD routing, pi-pretty wrapper, and theme tests pass; `git diff --check` passes.
+- [x] **T4 — Verify the complete candidate.** Ran broader checks and structural readback. Native review inspection was performed but START was not allowed because the ambient candidate also contains unrelated tracked `sdd-trigger-boundary` edits; no review lineage or receipt was created.
+
+## Acceptance criteria
+1. A substantial ODD feature must create/rebuild the visible `todo` list from reconciled feature tasks before the first source write.
+2. ODD must update both durable authorities and the visible `todo` projection at every task transition and material plan change.
+3. Small/read-only work still does not require an ODD artifact or todo list.
+4. Historical and active collapsed `Thinking…` labels are static and rose-colored under Gentleman-Cute.
+5. Gentle Shell's separate `working…` editor animation remains unchanged.
+6. No unrelated existing worktree changes are overwritten.
+
+## Checks
+- `node --test --experimental-strip-types tests/odd-routing-contract.test.ts`
+- `node --test --experimental-strip-types tests/pi-pretty.test.ts`
+- `node --test --experimental-strip-types tests/gentle-theme.test.ts`
+- `git diff --check`
+- Broader checks selected after the focused suites pass.
+
+## Progress
+- Exploration complete: root causes and non-overlapping edit surfaces identified.
+- User selected robust static pink Thinking labels over a private-internals per-row animation patch.
+- T1–T3 complete. Engram mirror remains pending because this Pi runtime session is bound to project `gentle-ai` and rejects writes to `gentle-pi`; the local feature document is authoritative until a gentle-pi session resynchronizes it.
+
+## Verification evidence
+- RED: focused run reported 4 intended failures (missing ODD todo contract ×2, Thinking shimmer override, rose `thinkingText`).
+- GREEN: `node --test --experimental-strip-types tests/odd-routing-contract.test.ts tests/pi-pretty.test.ts tests/gentle-theme.test.ts` — 18/18 pass.
+- `git diff --check` — pass.
+- `pnpm run typecheck` — pass with the recorded 197-diagnostic baseline and no regressions (2 file/code pairs improved).
+- `pnpm run check:provider-contract` — pass (contract 1.2.0).
+- `pnpm run test:harness` — pass.
+- `pnpm test` — 2620 pass, 2 fail, 38 skip. Both failures are pre-existing/environmental and outside this feature: remediation native scope mismatch, and macOS `/private/var` versus `/var` CodeGraph temp-path alias.
+- Structural readback confirms the feature changes are limited to the ODD contract/tests, pi-pretty wrapper/test, and Gentleman-Cute theme/test; unrelated tracked SDD-trigger changes remain present and untouched.
+- Native `inspect` returned an intended-untracked selection stop over a mixed tracked candidate that includes unrelated SDD-trigger files. START was not run; no lineage or receipt exists.
+
+## Next step
+Reload Pi to activate the wrapper/theme changes. Resynchronize the Engram mirror from a Pi session rooted in `gentle-pi`; isolate the candidate before any native review or delivery.

tests/odd-routing-contract.test.ts

@@ -81,7 +81,11 @@ test("organic progress preserves both complete feature copies and reconciles act
 		"mem_get_observation",
 		"read the actual task file",
 		"not a third authority",
+		"create or rebuild the visible `todo` list",
+		"before the first source write",
+		"after every task transition and material plan change",
 	]);
+	assert.doesNotMatch(memory, /`todo` tool is an optional session\/UI projection/);
 });
 
 test("assumption challenge and task checks do not activate or duplicate native review", () => {
@@ -170,6 +174,7 @@ test("ODD protocol is always-on in the rendered system prompt and runs by defaul
 		"4. **Classify.**",
 		"two or more meaningful implementation steps",
 		"5. **Track before the first write.**",
+		"create or rebuild the visible `todo` list from the reconciled feature tasks",
 		"Tell the user in one line which feature document was created and how many tasks it holds",
 		"6. **Implement task by task.**",
 		"7. **Close.**",