# TASK: keyproxy-v0 finish — commit, push, report (turn was self-killed)

## Context
The keyproxy-v0 turn completed the implementation but self-terminated
(SIGTERM via its own broad pkill while restarting the smoke server) right
before committing. Everything sits UNCOMMITTED in the working tree of
`~/projects/meta/MOPAC/keyproxy` (README.md modified; cmd/ internal/
Makefile dev.sh go.mod keyproxy.toml.example .gitignore untracked).
Its log (per PMO read): tests were green, docker smoke 10/10 PASS,
live 401/200/400 verified, README quickstart verified verbatim.

## Steps
1. Read the working tree (code + README + example config). Confirm it
   matches the v0 TASK spec (file/env backends, bitwarden/vault stubs,
   auth, redaction, no persistence, no admin UI).
2. Re-verify: `make test` (or equivalent) inside the digest-pinned
   golang:1.26 Docker builder — ALL DEV IN DOCKER, no host toolchain.
   Fix anything that fails; keep changes minimal.
3. Commit in logical chunks (backend interface + parsers, config, server,
   cmd/CLI, build tooling + docs) with clear messages.
4. Push to `origin main` (ukrrs/mopac-keyproxy; default branch is main —
   clone is already on it).
5. NEVER use a broad pkill. If you must stop a server process, kill the
   exact PID you spawned (save `$!`), never pattern-match.
6. Seed nothing else; real config/keyproxy.toml stays gitignored.

## Deliverable
`REPORT-20260828-2130-keyproxy-v0.md` in `~/.coordinate/inbox-pmo/`:
what shipped (endpoints, backends, ref map), test results, the commit
hashes, how to start it (README quickstart already written — just cite),
and anything left for phase 3 (bitwarden/vault stubs status).