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

This commit is contained in:
jester 2025-12-21 23:01:45 +00:00
parent a2a23d1e1d
commit 62f2867ec7

View File

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