agent-exec transport c4e7bcc1003fb3b60d968183cc9674cd/2e81d2e9845e

AGENT-EXECUTION.md

@@ -18,8 +18,8 @@ increment host fallback authorizations. Safe exhaustion without an emergency
 candidate ends `unavailable` or `blocked`, and that result does not authorize
 the host to write the unit. The legacy value `all-unavailable` remains
 parseable and likewise grants no host write authority. Cursor uses
-`cursor-agent-stable`. `model: auto` lets each CLI use its configured default
-model; PI therefore uses the operator-selected MiniMax default. The
+`cursor-agent-stable`. `model: auto` lets a CLI use its configured default
+model; any other value is passed to that CLI as its model selector. The
 `integration` block declares the host-exempt paths and the transport, admission,
 and cleanup entry points.
 
@@ -60,7 +60,7 @@ profiles:
   pi:
     adapter: pi
     executable: pi
-    model: auto
+    model: minimax-cn/MiniMax-M3
     enabled: true
 
   codex:
@@ -78,3 +78,38 @@ integration:
   cleanup:
     command: make task-finish
 ```
+
+## Model preferences (project choice)
+
+Generic rules for bounded packets, context budgeting, phase handoff and
+requested-versus-effective model identity live in the shared
+[standards/agent-execution.md](deps/development-guidelines/standards/agent-execution.md)
+and [workflows/handoff.md](deps/development-guidelines/workflows/handoff.md);
+project procedure is in
+[policy/delivery.md](policy/delivery.md#有界单元包上下文与阶段交接). This
+section records only this project's choices.
+
+- Planning, design and implementation plans: Codex or Claude when available,
+  in the host or a fresh CLI session. This is a preference, not a routing role.
+- Bounded implementation, repair and test units: the existing normal
+  candidates in the configured role order above. Requested models:
+  - PI: `minimax-cn/MiniMax-M3`, passed as `--model provider/id`. PI
+    actual events have reported `minimax-cn` / `MiniMax-M3` and the local
+    offline catalog lists that profile; each run still records the effective
+    model from that run's events.
+  - Cursor: `auto` (Cursor Auto).
+  - agy: Gemini 3.8 Flash is requested, but its exact selectable model ID and
+    effective identity are `NOT_VERIFIED` (the `agy` models query needs a
+    login that was not available). The profile therefore stays `model: auto`
+    until an observed model ID exists; do not claim Gemini 3.8 Flash is active.
+- Assigning a different candidate or model to a unit needs a concrete,
+  task-specific reason recorded in the task record, and stays within the
+  existing roles and candidate lists. It is not a silent permission or routing
+  change. Role lists, attempt limits, timeouts, output limits, the single
+  Codex emergency attempt, stage isolation and `fallback_to_host: never` are
+  unchanged by these preferences.
+- A requested model is prompt/config intent. Only the model reported in a
+  run's actual event envelope counts as effective; when the CLI does not report
+  it, record `not-observable`. Unknown context capacity, a missing agy login
+  or missing automatic compaction are recorded facts, not global fail-closed
+  conditions.