Advance app runtime ownership and modernization docs

AGENTS.md

@@ -30,11 +30,12 @@ Read these first:
 - Commit and push each verified successful progress slice.
 - Prefer larger coherent slices over tiny checkpoints, but keep docs/debt updated
   with each slice.
-- After a verified slice is committed and pushed, reset conversation context
-  before starting the next slice when practical, especially if the thread is
-  approaching automatic compaction. Record all needed resume state in committed
-  code/docs first so the next thread can restart from `AGENTS.md`, roadmap/debt,
-  and git history instead of relying on chat transcript context.
+- Treat automatic compaction as a failure mode to avoid. Keep active context
+  small, commit and push before the thread grows large, and reset conversation
+  context between verified slices when practical instead of carrying excess
+  history forward. Record all needed resume state in committed code/docs first
+  so the next thread can restart from `AGENTS.md`, roadmap/debt, and git
+  history instead of relying on chat transcript context.
 - Do not revert user changes. Unrelated untracked notes, such as
   `docs/human-review-notes.md`, should be left alone unless explicitly requested.
 - Use CMake as the source of truth. Legacy Visual Studio project files are not the
@@ -42,8 +43,9 @@ Read these first:
 - Use `apply_patch` for manual source/doc edits.
 - For delegated work, follow `docs/modernization/director-workflow.md`: the
   coordinator keeps integration locally, assigns direct worker tasks, uses
-  `gpt-5.3-codex-spark` workers by default, and gives them the exact project
-  context needed so they do not spend tokens re-reading repo docs.
+  `gpt-5.4-mini` workers by default, and gives them a minimal task packet with
+  only the build, test, and code-exploration context needed so they do not
+  spend tokens re-reading repo docs.
 
 ## Build And Test