codex-task-corpuslisted

# Codex Task Corpus Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined, otherwise the absolute path of this plugin's root directory. Use this skill when the question spans many persisted Codex tasks: the newest `N` chats, repeated work or failure patterns, cross-task context recovery, or a traceable capability-gap audit. Use `codex-log-reader` for one exact task and `codex-thread-supervisor` for a live task. This workflow gathers evidence; it does not authorize source edits, installation, publication, or telemetry. Read `$PLUGIN_ROOT/references/codex-task-corpus-contract.md` before filling the typed ledgers or making an aggregate coverage claim. ## Freeze The Corpus Create an ignored or otherwise private output directory. The helper reads only leading session metadata, excludes internal subagent rollouts and the current `CODEX_THREAD_ID` by default, keeps user-visible forks, and copies no messages or cwd values: ```bash python3 "$PLUGIN_ROOT/scripts/codex_log_reader.py" corpus \ --count 150 \ --cutoff 2026-01-31T18:00:00Z \ --output-dir ./tmp/codex-task-corpus \ --json ``` Pass `--exclude-thread-id <id>` when the current task id is known but not exported in the environment. Use `--cwd <path>` for a project-bounded corpus; the filter value is not emitted. Exact count is the default contract. If there are too few eligible tasks, increase `--sca