plan-verifylisted

# Verify a plan's implementation Establish, with evidence, whether a plan has been implemented fully (everything it promised) and correctly (it works, it is tested, its guarantees hold). This is a read-only review: it reports, and it never edits, fixes, reverts or updates the plan's status. The summary is written for a non-technical reader; the technical report follows for the engineer. ## Resolve the plan, the implementation location and the scope Take the plan path or name, and any scope hint ("commits since v1.3.0", "the uncommitted work", "the work in this task", "in worktree checkout-flow", "allow environment bootstrap"), from the user's invocation or an unambiguous target already supplied in the task. The implementation is not assumed to live in the current directory. The work may have happened in a linked worktree (a sibling directory on its own branch), in a submodule, or in a submodule's worktree, while the task sits in the main checkout, or the reverse. Map the workspace first with plain Git, then resolve both locations explicitly and state them in a one-line assumption. Do not promise access the environment does not have; report what could not be inspected. - **Workspace map.** The repository containing the current directory; whether it is the main checkout or a linked worktree, and every worktree of that repository (`git worktree list --porcelain` lists all of them from any one, main first); the superproject, if any (`git rev-parse --show-superproject-wor