Record debug evidence in one run-scoped capture session

This commit is contained in:
2026-11-22 02:49:48 +00:00
parent 584b041e57
commit 8680060400
10 changed files with 700 additions and 676 deletions

View File

@@ -1389,6 +1389,31 @@ counting, and evidence source order/window behavior.
## Stage 30: Build The Debug Recorder And Session Lifecycle
**Status:** Complete. Replaced summary/trace allocation and separate terminal
writers with one run-scoped recorder for incremental JSON/text evidence and one
terminal outcome. Allocation creates the absolute run directory and atomically
updates a relative latest link at start; completion never retargets it. Failed
starts retain an available directory rather than deleting captured data.
The recorder is concurrency-safe, retains callback errors for boundary checks,
preserves primary causes alongside capture failures, and finalizes once without
rewriting evidence on repeated calls. Finalization failures are errors, including
after artifact publication; a later presentation failure remains reportable.
Added reusable native debug/debug-dir input binding and selection, preserving
quiet/debug ordering, explicit false/empty values, configured/default roots,
invocation-relative overrides, and nonempty overrides over empty configuration.
Disabled capture performs no allocation or latest update. Removed the legacy
summary/terminal factories and routed run-path allocation/finalization through
the new lifecycle before engine/preflight and before successful presentation.
Real-filesystem lifecycle/concurrency/failure tests, isolated real-CommandKit
flag/selection tests, focused pipeline tests, selected vet/race checks, production
debug/bundle/pipeline/config builds, and git diff checks pass. Full CLI/pipeline
package checks remain blocked at setup by unmigrated imports of the removed
reporting package and old ConfigKit's YAML plugin/limit dependency; their results
are not claimed passing. Full native evidence/observation wiring remains Stage 31,
native run-handler composition remains Stage 33, and final publication/report
outcome integration remains Stage 34. Remaining obsolete fixtures are Stage 35
cleanup, not a reason to restore the old writers.
**Goal:** requested capture has one simple recorder and explicit failure semantics.
**Inspect/change:** `internal/core/debugbundle`, `internal/framework/debug`,