[joshrotenberg]

Adds docs/working-an-issue.md: the procedure an operator follows to take one GitHub issue to a ready pull request, with the code change made by an agent running in the server. It addresses next increment 3 in docs/dogfooding.md (isolated-worktree writes, then an end-to-end write task).

Changes

• docs/working-an-issue.md: roles, eleven steps with the exact commands, and a friction log. Each friction entry names the step, the observation and the candidate response (procedure change, server fix, or optional helper).
• docs/runs/2026-11-01-codex-wrapper-153/: run record for feat: read the --output-last-message file back for the caller codex_wrapper_ex#153 (config, both prompts, both agent reports, summary with durations and usage, final diff). Provider session IDs are omitted.
• docs/dogfooding.md: a row for the run.

What the first run showed

One Codex workspace_write route implemented the issue in two turns on one session (174 s, then 19 s). The final diff is the agent's with no operator edits, and every CI gate passed on the host. The procedure was corrected where the run differed from the draft:

• the prompt states what the Codex sandbox blocks (network, Mix's TCP lock, ps);
• result has to be polled;
• native CLI probes are an operator step.

Server and helper candidates from the friction log, none implemented here:

• a wait on result;
• @path for string parameters in mix gen_agent_server.ops;
• MIX_OS_CONCURRENCY_LOCK=0 in the Codex child env for write routes;
• the model name in results;
• current core and adapter requirements in mix.exs.