parity-gap

# Parity Gap Bring `this program` (default: cwd) up to (and past) a `reference`. Map both sides, diff them, **confirm scope in rounds of 4 questions before writing anything**, then author tasks into `docs/todo.md`, via the `todo` skill if installed or directly otherwise. ## 1. Resolve the Inputs First - `this program` defaults to the working directory. Name another explicitly to override. - `reference` is one of: - a remote repository: clone it into a temp dir then treat as local codebase. - a local codebase (path on disk): read its tree, entrypoints, commands, modules. - a docs/spec/feature list (file or pasted text): treat every command, endpoint, flag, or behavior it describes as a reference feature. - If either is ambiguous (which repo? which spec?) or the reference can't be reached once identified (private, no network, no read access), ask anything and no guesses before mapping. ## 2. Map Each Side (Inline, Single-Pass) Map what each side exposes to a user; skip internals and file structure. The user-reachable surface: - commands / subcommands / flags - exported APIs, routes, endpoints - config keys, env vars - UI/TUI/CLI surfaces and the actions they expose - notable behaviors, formats, integrations Use `Grep`/`Read`/semantic code search inline. The reference is the spec side, so read it thoroughly; the program is the have side. If the reference is too big to hold inline, offload its mapping to a read-only exploration subagent (e.g. `Explore`) and diff from...