docs: record bounded local coding runtime diagnosis

.project-docs/30-worklog/tasks/20261014-diagnose-coding-runtime-8b41c9e2.md

@@ -0,0 +1,48 @@
+# Task: Diagnose unavailable local programming runtime
+
+## Identity
+
+- Task ID: 20261014-diagnose-coding-runtime-8b41c9e2
+- Mode: Feature
+- Branch: codex/20261014-diagnose-coding-runtime-8b41c9e2-diagnose-coding-runtime
+- Worktree: /Users/chillishark/Makelore 麦洛/.codex-worktrees/makelore/20261014-diagnose-coding-runtime-8b41c9e2
+- Base commit: f34e651774beb6a2a213b5711f2ffb887d22d4b7
+- Owner: codex
+- Status: Ready for Integration
+
+## Scope
+
+- Diagnose the current trial Code runtime-unavailable notice using source, immutable runtime artifacts and bounded application startup diagnostics; explain what is actually known and the evidence gap.
+
+## Intent And Constraints
+
+- This request asks why; no product/source fix, app restart, user worker, paid model call, UI mutation, profile/credential/chat-history read or deployment. Isolated owned checkout based on the just-published f34e651. Read only startup diagnostics and runtime dependency metadata. Preserve current runtime and all peer/primary work.
+
+## Outcome
+
+- Direct failure stage identified: the Pi Agent Server starts and reaches server.ready, then the managed session-open path fails and cleans up with open_failure. The original exception is not retained by current diagnostics, so the specific underlying cause cannot honestly be identified from existing evidence. No runtime or product changes made.
+
+## Verification
+
+- No tests or paid/provider invocation required for this read-only diagnosis. Source trace independently reviewed; current native-launch.log has three server.ready→open_failure cycles, no diagnostic field/original stack, and later background_sleep events do not prove recovery. Actual Main/server artifacts match active436 manifest. Pi0.84.2 files/modules/required API exports are present and resolve in the actual retained runtime; Node version meets its engine. E2E=1 is real but does not disable coding composition/Pi. No secrets/profile state read.
+
+## Follow-ups
+
+- For a repair continuation, capture a bounded sanitized original exception at the managed session-open boundary, reproduce the failing initialization without a paid prompt, then fix its actual cause and verify the real Code session. Avoid guessing a model/network cause, blindly reinstalling dependencies or treating E2E as a disable flag. This diagnostic checkout is retained ready for that same issue; no source fix or publication was requested.
+
+## Promotion Candidates
+
+- None recorded.
+
+## Project Context Loaded
+
+- Task ID20261014-diagnose-coding-runtime-8b41c9e2, Feature, branch/worktree/basef34e651 exactly verified through official start/status;69 peers assessed through only their Scope/Intent/Promotion sections. Two old placeholder scopes remain unknown; no concrete conflict with read-only diagnosis.
+- Loaded startup/memory-index and own record; canonical project-positioning/current-state/decision/system/business/evidence/reflection/commitment/stale documents are byte-identical to350f7d7 already read in this conversation. Product goal and Main-owned auth/runtime/project boundaries remain; Pi0.84.2 is the only supported coding runtime. No old provider/runtime fallback or credential handling change.
+- Gate Passed for bounded diagnosis. Plan: trace public error→actual prepare/open stage, independently check retained artifacts/dependencies and sanitized existing startup events, report supported facts and missing evidence.
+
+## Evidence And Boundary
+
+- `electron/coding-runtime/conversation-service.ts:88–114` maps ordinary exceptions without publicError to503 CODING_RUNTIME_UNAVAILABLE. `electron/api/routes/coding-route-errors.ts:39` supplies the fixed Chinese message. Snapshot417–428/prepare753–788 opens the runtime even before sending a prompt.
+- `electron/coding-runtime/pi/runtime.ts:238` managed opener includes provider projection/resources/extensions and SDK session opening;487–491 cleanup reasonopen_failure rethrows without preserving the raw error in current application logs. Existing server.ready events prove server startup/import but not successful thread/session initialization.
+- Current stage native-launch.log contains E2E startup atline4; Main575 creates coding composition regardless. E2E alters startup effects/background idle timing, not a blanket Pi disable. Actual runtime/server/Main hashes match the active436 source; development resolves Pi CLI via snapshot node_modules→primary, not packaged resources/pi-runtime. Pi package/version,7server module paths and6required APIs are present. These checks do not prove every generated session/resource/configuration is valid.
+- Read-only independent source and artifact reviewers agree: log evidence does not distinguish the original provider/configuration/extension/session exception. Specific diagnosis requires new sanitized exception evidence; do not call a hypothesis the proven root cause.