Log grind repo documentation update 2026-03-10
This commit is contained in:
parent
9f01809f1a
commit
0a57635065
@ -6,3 +6,10 @@
|
|||||||
|
|
||||||
- Closed: Upload transport timeout tuning — upload route now logs explicit error categories distinguishing client abort, upstream timeout, and socket reset.
|
- 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.
|
- 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
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user