Lahfir 90d81604e1 fix(status): report tracing from the live writer, not the manifest alone ... status computed `tracing = context.trace_enabled() || manifest_trace_on`. The manifest-only OR re-overstated tracing after the writer failed to open (e.g. a best-effort --trace path that can't be created on a trace-enabled session): emits silently drop while status still reported "tracing": true. Report `context.trace_enabled()` alone — now honest about a failed writer via has_sink() — so status reflects whether bytes are actually being written. Guard: status_reports_tracing_false_when_writer_failed.		2026-07-01 05:34:18 -07:00
..
core	fix(status): report tracing from the live writer, not the manifest alone	2026-07-01 05:34:18 -07:00
ffi	fix(session): harden session-first trace against review findings	2026-06-30 22:18:05 -07:00
linux	refactor!: over-engineering audit cleanup (#64)	2026-06-24 14:31:17 -07:00
macos	feat(macos,core): harden adapter and core foundation with caller-controllable guardrails (#82)	2026-06-29 11:32:27 -07:00
windows	refactor!: over-engineering audit cleanup (#64)	2026-06-24 14:31:17 -07:00