Skip to content

fix: add structured logging for 5 audit gaps#255

Open
ronniegeraghty wants to merge 1 commit into
mainfrom
ronniegeraghty/audit-logging
Open

fix: add structured logging for 5 audit gaps#255
ronniegeraghty wants to merge 1 commit into
mainfrom
ronniegeraghty/audit-logging

Conversation

@ronniegeraghty
Copy link
Copy Markdown
Owner

Summary

Closes 5 logging gaps identified in the codebase audit (plan/codebase-audit.md).

Changes

  1. Run-completion slog message (P1) — engine.go: Added slog.Info("Evaluation run complete", ...) with run_id, pass/fail/error counts, and duration after the evaluation loop finishes.

  2. Config resolution logging (P1) — run.go: Added slog.Info("Configs loaded", ...) with source path, count, and config names after configs are resolved.

  3. Workspace recovery warnings (P1) — workspace.go: Added slog.Warn for 4 previously silenced errors in recoverMisplacedFiles() (junk dir delete, cross-FS copy, cross-FS remove, file cleanup).

  4. Report write path context (P2) — engine.go: All 3 slog.Error("Failed to write...") calls now include the output directory path. Added slog.Debug for successful writes.

  5. Skill installation logging (P2) — fetcher.go: Added slog.Info("Remote skill installed", ...) after successful npx skills add.

Testing

  • Build passes for all changed packages
  • go test ./hyoka/cmd/... passes
  • Pre-existing test failures in eval (TestBuildSessionConfig_SystemPromptWired) and pairwise (undefined fields) are unrelated

- Add slog.Info for evaluation run completion with counts and duration
- Add slog.Info for config resolution with source path and config names
- Add slog.Warn for workspace recovery failures (3 silenced errors)
- Add file path context to report write error logs
- Add slog.Info for remote skill installation completion

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant