session-audit
Triggers: /session-audit, "session audit", "auditar sesión", "audita la sesión", or automatically as the mandatory pre-close step (before mem_session_summary) when a session is being closed.
Purpose
Produce objective, cited findings on where a session violated the rules, and ROUTE each one
to the place it will actually be acted on: a GitHub issue in agent-config for
configurator-scoped findings, the project's own backlog for project-scoped ones. The audit is
done by an independent sub-agent — never by the acting session agent — because the acting
agent is blind to its own blind spots (judge-and-party).
The auditor remains read-only: it reports, it never fixes, and it never files anything itself. The ORCHESTRATOR routes what the auditor returns. Filing an issue is capture with a durable, actionable sink — not self-correction — so independence is preserved intact.
Findings are NOT accumulated on disk. Recurrence is visible through duplicate GitHub issues
sharing a byte-identical [rule:<rule-id>] title prefix: the same rule violated twice reads
as two adjacent issues in the list, with no filter and no synthesis step required.