Logs Audit Extensions

To generate TDD compliance audit reports from agent session logs, use the deep audit extension to conditionally load TDD compliance templates and parse local transcript telemetry for tool counts and file mutations.

The best way to extract file mutation telemetry without token bloat is running a deterministic local script that parses the agent transcript for tool counts, commands, and file read/mutation data.

Yes, the logs audit extension automatically detects Strict TDD methodology, including RED/GREEN cycle markers, from active project metadata to conditionally inject the appropriate compliance audit template.

You append methodology-specific compliance sections to a deep log report by running the deep audit command, which loads just-in-time reference materials at the correct workflow stage based on detected plan methodology.

You need specialized compliance evidence for agent runtime transcripts when a session uses a specialized planning approach like Strict TDD, requiring deeper verification than generic log reporting provides.

You can use generic log reporting for TDD sessions, but it produces unverifiable compliance output; deep audit extensions append specialized TDD compliance sections and parse transcript telemetry for auditable results.