Update OPEN_THREADS.md - Reflect devcontainer provisioning resolution, artifact naming fix, and new open items

OPEN_THREADS.md

@@ -1,39 +1,49 @@
 # Open Threads – zlh-grind
 
-This file tracks items that are **not finished**.
+This file tracks items that are unresolved, under investigation, or explicitly deferred.
-
-Rules:
-- Add items when we intentionally pause work
-- Remove items when complete
-- Keep it short and actionable
 
 ---
 
-## Active
+## Devcontainer provisioning failures
-
+- **Status:** RESOLVED (design-level), implementation pending
-### 1) API ↔ Agent payload contract: `container_type` wire key
+- Root cause identified as agent execution model:
-- Agent `state.Config` expects `container_type` (snake_case).
+  - installers require `RUNTIME_VERSION`
-- Recent API refactors introduced `ctype` / `containerType` variants.
+  - shared installer logic (`common.sh`) must execute in same shell as runtime installer
-- Decision: update API payload builders to emit `container_type` to avoid template rebuilds.
+- Action:
-
+  - update agent to concatenate embedded scripts into single bash invocation
-Status: IN PROGRESS (API patch + deploy)
+  - ensure env injection before execution
 
 ---
 
-### 2) Devcontainer artifact 404 (Node runtime)
+## Artifact naming / layout drift
-- Dev containers attempt to download artifacts like:
+- **Status:** RESOLVED
-  - `/devcontainer/node/24/node-v24.12.0-linux-x64.tar.xz`
+- Artifact store standardized to simplified naming (`<runtime>-<version>`).
-- Artifact server Caddy currently rooted at `/opt/zlh/zpacks` only.
+- Installer logic updated to support `ARCHIVE_PREFIX` to handle cases like Java (`jdk-*`).
-- Need: expose devcontainer runtime artifacts under the same root OR adjust artifact path strategy.
-
-Status: OPEN
 
 ---
 
-### 3) zlh connector / gitea MCP tool not functioning in ChatGPT
+## Version-aware markers for devcontainer runtimes
-- Connector appears enabled but tool calls are not available / not executing.
+- **Status:** OPEN
-- Workaround: manual zip transfer + offline review.
+- Current marker logic does not distinguish between installed runtime versions.
-
+- Follow-up:
-Status: OPEN
+  - consider writing installed version metadata to marker file
+  - enable clean upgrades (e.g., node 24 → 25)
+
+---
+
+## Agent execution abstraction cleanup
+- **Status:** OPEN
+- Embedded script execution lacks explicit contract for:
+  - env overlay
+  - timeout
+  - structured error classification
+- Deferred to next sprint after installer stabilization.
+
+---
+
+## API → agent contract enforcement
+- **Status:** OPEN
+- API must continue enforcing runtime + version explicitly.
+- Agent must remain sole translator of intent → execution environment.
 
 ---