Recover a brief written during a paused rebase

A governed wu:rebase can pause on a content conflict. While it is paused, wu:brief and wu:delegate stop before writing evidence or issuing a handoff receipt: their ledger commit would move the HEAD pinned by the pause.

For compatibility, an older or already-running brief path may have appended checkpoints after the pause saved its HEAD and before the current write guard applied. An authenticated owner can request the narrow reconciliation explicitly from the claimed worktree:

pnpm wu:rebase --id WU-XXX --reconcile-brief-evidence

The command accepts only a contiguous linear commit chain where each commit changes only that WU’s event ledger, appends one schema-valid wu:brief checkpoint, and preserves all preceding ledger bytes. It verifies the original recorded integration target and snapshots the branch and rebase refs, registered worktree, index, worktree, pause record, and files in the active rebase-control directory (including rebase-merge/onto, which holds the destination). An unrelated landing on the integration branch while the pause is open does not block reconciliation: the destination is pinned by the pause record and that file, not by the live tracking ref. It updates only the pause’s recorded HEAD. It does not continue or abort the rebase.

The event ledger proves the row has the shape written by wu:brief; it does not prove which process emitted it. The normal authenticated caller, owner, claim/worktree, receipt, expiry, addressee, replay, target, and staged-path checks remain in force for governed recovery.

If any source or WU document changed, the history is non-linear, an event was rewritten, the row is not a same-WU brief checkpoint, or any pinned state moved, reconciliation refuses without changing the pause. Use the ordinary governed --continue or --abort path instead; those paths retain their caller, claim, receipt, target, index, staged-path and pause checks. A genuine legacy claim without a pinned integration target can proceed only to the normal governed abort after reconciliation; continuation still requires the supported claim upgrade after abort. After a successful reconciliation, inspect the worktree and choose the normal guarded continuation or abort action; reconciliation itself never resumes the rebase.

The flag is available only when the canonical CLI and installed software-delivery pack include this producer change. This is a LumenFlow producer change; it does not assert Sidekick Cloud deployment or adoption by existing consumer checkouts. The owning workflow must still run the normal guarded command in each consumer checkout.