feat(logging): build-config debug logging + task traceability #8

claude · 2026-06-04T17:27:45Z

claude commented

2026-06-04 17:27:45 +00:00

Summary

Build-configuration-driven logging so debugging is rich locally while the installed app stays quiet.

New ClaudeDo.Logging library: BuildConfig.IsDebug (runtime DebuggableAttribute check, no #if DEBUG), DefaultTaskIdEnricher, and LoggingSetup.Configure (the single shared Serilog setup both processes call).
Debug builds (Rider run button): Debug level, console + file. Release builds (installed app): Warning level, file only.
Worker + App/Ui now write ONE shared rolling file ~/.todo-app/logs/claudedo-.log (retain 2), each line tagged with a Process and SourceContext. The App/Ui were previously log-silent.
TaskId correlation rides Serilog LogContext: pushed in TaskRunner.RunAsync/ContinueAsync (Worker) and in WorkerClient.InvokeForTaskAsync (UI). Grep one TaskId to follow a task UI -> Worker -> UI.
IWorkerClient / WorkerHub contracts unchanged; only the concrete WorkerClient ctor gained an ILogger param, so test fakes are unaffected.

Test plan

dotnet build App + Worker (Release): 0 errors
Worker.Tests: 419 pass (incl. 4 new logging tests)
Manual (visual-verification gap): run App + Worker from Rider (Debug), confirm both log to one claudedo-*.log + console; run a task and confirm UI and Worker lines share the same [TaskId]
Manual: install Release build, confirm log is Warning+ only and no console output

Review notes (non-blocking)

BuildConfig.IsDebug uses GetEntryAssembly(), which is null under the test host -> the BuildConfigTests assertion is effectively a tautology. This is correct for production (entry assembly = the App/Worker exe) and the spec already accepted that the branch can't be flipped within one test run.
InvokeForTaskAsync's LogContext scope currently only decorates the single debug trace line; kept as a forward-looking hook for future UI log lines on that path.

See docs/superpowers/specs/2026-06-04-debug-logging-traceability-design.md and the matching plan in docs/superpowers/plans/.

🤖 Generated with Claude Code

## Summary Build-configuration-driven logging so debugging is rich locally while the installed app stays quiet. - New `ClaudeDo.Logging` library: `BuildConfig.IsDebug` (runtime `DebuggableAttribute` check, no `#if DEBUG`), `DefaultTaskIdEnricher`, and `LoggingSetup.Configure` (the single shared Serilog setup both processes call). - **Debug builds** (Rider run button): `Debug` level, console + file. **Release builds** (installed app): `Warning` level, file only. - Worker + App/Ui now write ONE shared rolling file `~/.todo-app/logs/claudedo-.log` (retain 2), each line tagged with a `Process` and `SourceContext`. The App/Ui were previously log-silent. - `TaskId` correlation rides Serilog `LogContext`: pushed in `TaskRunner.RunAsync`/`ContinueAsync` (Worker) and in `WorkerClient.InvokeForTaskAsync` (UI). Grep one TaskId to follow a task UI -> Worker -> UI. - `IWorkerClient` / `WorkerHub` contracts unchanged; only the concrete `WorkerClient` ctor gained an `ILogger` param, so test fakes are unaffected. ## Test plan - [x] `dotnet build` App + Worker (Release): 0 errors - [x] Worker.Tests: 419 pass (incl. 4 new logging tests) - [ ] **Manual (visual-verification gap):** run App + Worker from Rider (Debug), confirm both log to one `claudedo-*.log` + console; run a task and confirm UI and Worker lines share the same `[TaskId]` - [ ] **Manual:** install Release build, confirm log is `Warning`+ only and no console output ## Review notes (non-blocking) - `BuildConfig.IsDebug` uses `GetEntryAssembly()`, which is null under the test host -> the `BuildConfigTests` assertion is effectively a tautology. This is correct for production (entry assembly = the App/Worker exe) and the spec already accepted that the branch can't be flipped within one test run. - `InvokeForTaskAsync`'s `LogContext` scope currently only decorates the single debug trace line; kept as a forward-looking hook for future UI log lines on that path. See `docs/superpowers/specs/2026-06-04-debug-logging-traceability-design.md` and the matching plan in `docs/superpowers/plans/`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude added 8 commits 2026-06-04 17:27:45 +00:00

build(logging): scaffold ClaudeDo.Logging project da73324e3a

feat(logging): default TaskId enricher with passing tests b3b87df320

feat(logging): runtime Debug-build detection via DebuggableAttribute ab260ad0a6

feat(logging): shared LoggingSetup with build-config sink branching 7ce418d474

feat(logging): route Worker logging through shared LoggingSetup c592ca32fb

feat(logging): wire App/Ui logging to shared LoggingSetup 324f1d9c7c

feat(logging): tag Worker task execution with TaskId for traceability 075b6d13af

feat(logging): tag UI task actions with TaskId + debug trace lines 50c10b6e75

This pull request has changes conflicting with the target branch.