feat: add correlated runtime logging and operational diagnostics - #279
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
odek | 811d681 | Commit Preview URL Branch Preview URL |
Sep 28 2026, 07:26 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operational failures and delegated work were spread across surface logs, stderr, and runtime event handlers. Add an opt-in
~/.odek/runtime.logthat brings agent activity and application failure diagnostics into one structured, metadata-only JSONL stream.docs/LOGGING.md.Validation: full CLI suite passed; scoped race tests and actual subagent subprocess tests passed; local full lint and govulncheck passed. Runtime logger statement coverage is 95.9%; subagent logging, diagnostic routing, error classification, and early logging policy have 100% coverage in targeted runs. One initial CLI run hit a temporary-directory teardown race and passed isolated rechecks plus the full rerun. A broader local LLM-client run exceeded its 180-second timeout in the existing speech-provider retry test; focused tests for the changed auxiliary-call paths passed. Full CI is the merge gate.
Logging remains disabled by default. Startup/service-wide records have process correlation without fabricated session IDs. Diagnostics remain best effort, with stderr as the fallback when logging itself fails.