nio-reportlisted

# Nio — Execution Report Display recent agent execution events from the Nio audit log. This is the focused `report` capability of the Nio framework. > **Passive invocation.** If the user asks what Nio blocked/confirmed recently, to see the audit log / recent activity, or for a diagnostics summary, you MUST read and format the audit log as below. **This skill uses the Read tool only — there is no script to run.** Do not attempt to invoke any `report.js` / `report-cli.js` — none exist. The only action is: read `~/.nio/audit.jsonl` with the Read tool, parse each line as JSON, and format the output as shown below. ## Log Location The audit log is stored at `~/.nio/audit.jsonl` (or `$NIO_HOME/audit.jsonl`). Each line is a JSON object with an `event` discriminator field: `guard` (one per tool-call evaluation), `session_scan`, `lifecycle`, `diagnostic`. A `diagnostic` entry carries `source` (one of `config`, `oauth`, `llm`, `external_analyser`, `collector`, `scanner`, `hook`), `kind`, `severity`, `component`, `message`, optional `hint`. Aggregate diagnostics by `(source, kind, component, config_path)` into a Diagnostics summary section. Old-format lines (no `event` field) are guard entries with `event_type: "pre"`. ## How to Display 1. Read `~/.nio/audit.jsonl` using the Read tool 2. Parse each line as JSON 3. Filter by `event` type — guard entries in the main table, scan entries in a separate section 4. Show recent events (last 50 by default) 5. If any events have `initiati