2.9 KiB
2.9 KiB
Session Log
2026-03-10
- Closed: Upload transport timeout tuning — upload route now logs explicit error categories distinguishing client abort, upstream timeout, and socket reset.
- Research: Investigated external agent standards applicable to zlh-agent. No formal standard maps cleanly — agent is purpose-built (embedded process manager + filesystem authority inside LXC, internal-only caller). Key findings: health probe split (/healthz liveness vs /readyz readiness) is a common convention but not required given single-caller architecture; graceful shutdown (SIGINT/SIGTERM, 10s timeout) is correct; structured lifecycle logging already solid; Go 1.21 slog exists if log unification is ever wanted. No open threads opened from this — no gaps requiring action.
- Grind repo updated to reflect current platform state:
- README.md — added Current Platform Capabilities section (March 2026)
- Agent_Endpoint_Specifications_Phase1.md — created; full route reference including updated /status crash metadata fields
- Session_Summaries/2026-03-01_Upload-Pipeline-Filesystem-Consolidation.md — created; includes upload transport fix (502 root cause + resolution)
- Frontend/TerminalView_Component.md — created; includes reconnect behavior (1–5s backoff, no page refresh required)
- ZeroLagHub_Quick_Status_Feb2026.md — created; reflects March 2026 operational state
- Session_Summaries/2026-03-10_Agent_Observability_Update.md — created; structured logging, crash metadata fields, ReadinessTimeout constant, crash semantics unchanged
2026-03-14
Goal: Stabilize dev container provisioning across agent, portal, and artifact server.
Scope:
- catalog-driven runtime installs
- dotnet runtime support
- dev workspace environment
- portal provisioning updates
Explicit non-goals:
- platform architecture changes
- container orchestration changes
Canonical refs used:
- ZeroLagHub knowledge base
- dev runtime provisioning spec
Work completed:
Agent:
- switched dev runtime validation to artifact catalog
- runtime installs moved to
/opt/zlh/runtimes - implemented runtime install guards
- implemented dev user environment
- updated dev shell to run as
dev - added dotnet runtime provisioning
- added optional code-server provisioning
Portal:
- added dotnet runtime
- added enable code-server option
- enabled Files tab for dev containers
- dev file uploads now current-directory based
API:
- added
enable_code_serverfield to dev provisioning payload
Artifact Server:
- runtime artifacts verified
- dotnet installer aligned with artifact fetch model
Issues discovered:
- code-server artifact contains repository source
- installer expects packaged release
Resolution: Artifact server must provide compiled code-server release archive.
Current system state:
- dev runtime provisioning operational
- dotnet runtime operational
- portal provisioning operational
- code-server blocked by artifact packaging