git-branch-redo-from-scratchlisted

# Redo from scratch Throw the implementation away and write it again, without losing what the original learned. Argument: $ARGUMENTS — a PR number, a branch, a statement of what should change about the approach, or nothing. Four references carry the parts that must not drift: - `references/rebuild-contract.md` — the contract, the coverage ledger, reconciliation, and what counts as done. - `references/branch-safety.md` — the gates, the backup, recovery, and the push. - `references/commit-messages.md` — style discovery, intent recovery, and the privacy gate. - `references/rebase-toolkit.md` — per-commit verification with no editor. ## Core principle The old branch is the specification, not the source. A redo that reads the old implementation line by line and retypes it has reproduced the shape it was called in to replace. Work from what the branch had to *achieve*; consult how it achieved it only when the requirement is ambiguous. ## Boundary the `git-branch-soft-reset-and-recommit` skill keeps the net change identical and rebuilds only the history. Reach for it when the code is right and the commits are wrong. This skill is the opposite trade: the history and the code are both replaced, and the net change may differ. That makes it strictly riskier, so it earns its safety from the contract rather than from a tree comparison. ## Phase 1 — Establish the contract before anything else Per `rebuild-contract.md`. Identify trunk's tests, the tests this branch add