audit

dynos-work: Audit

Runs the full audit-to-done pipeline: audit → repair loop → DONE.

Command Funnel (applies to every command in this skill)

Every deterministic step below runs through the plugin CLI. Resolve it once at the start of the skill and substitute the ABSOLUTE path literally into each command you run (permission prefix-matching operates on literal command text):

PLUGIN_ROOT="${CODEX_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"
if [ -z "$PLUGIN_ROOT" ]; then
  echo "Set CODEX_PLUGIN_ROOT or CLAUDE_PLUGIN_ROOT to the dynos-work plugin root." >&2
  exit 2
fi
DYNOS="${PLUGIN_ROOT}/bin/dynos"   # resolve once; use the absolute path in every command

"$DYNOS" ctl <subcommand> wraps hooks/ctl.py; "$DYNOS" hook <script> ... wraps helper scripts (router, lib_tokens, build_prompt_context, ...) with PYTHONPATH handled internally. A permissions-ON user can allow the single <plugin-root>/bin/dynos prefix once instead of approving every call.

JSON payloads (classification, execution-graph, repair-log) are piped to the ctl wrapper over stdin with --from - and a heredoc — NEVER staged at /tmp or any raw filesystem path (the write policy denies those, by design). Temp files, when genuinely needed, belong in .dynos/task-{id}/_scratch/.

All repair-log persistence must go through "$DYNOS" ctl write-repair-log ... --from .... Do not hand-write .dynos/task-{id}/repair-log.json.

Ruthlessness Standard

• Missing evidence is a finding.
• Partial compliance is non-compliance.
• Cosmetic fixes do not count as repairs.
• If a path is unverified, treat it as suspect.
• Prefer surfacing a real risk over preserving a comforting narrative.
• If two interpretations exist, audit the harsher one until disproved.
• Do not let a clean summary hide a dirty edge case.

What you do

Step 0 — Contract validation

After finding the active task, validate that all required inputs from the execute skill are present:

"$DYNOS" ctl validate-contract --skill audit --task-dir .dynos/task-{id}