Complete

Step 1 - log the work

Follow reference/completion-recovery.md to capture the source tree and compact archive annotation before any logging edits. Preserve the exact verified spec prefix, its UTF-8 byte length and SHA-256, branch, original HEAD, and local base. Record the reference's narrow absentOptional proof before creating any optional findings/review stub on an older installation; tree absence alone is insufficient. Prepare the entire archive, including the sections below and any generated try guide, before placing it at its absent destination. An existing matching archive enters recovery; never overwrite it or append duplicate sections.

Check whether the spec is a feature, fix, or rollback. A fix is marked Type: Fix and has no build-plan number. A rollback is marked Type: Rollback and records the exact target feature, archive, commit, and parent.

• Feature - use the verified spec's frozen **Build attempt:** and stable ID, following ../feature/reference/build-history.md. Attempt 1 keeps blueprint/history/features/NN-name.md; N > 1 uses NN-name--build-N.md. Validate the attempt against prior immutable builds and completed reversals; never increment it at completion or resume. For an older active spec without the field, derive 1 only with no prior builds, or derive the next attempt only from unambiguous prior builds and their proven completed reversals. Keep those reviewed spec bytes and the existing branch unchanged; otherwise stop. An existing matching archive and its annotation freeze the recovery destination. Check the feature off in blueprint/build-plan.md (and its parent item once all sub-items are checked). Then recompute the overview fingerprint using /overview's checkbox-normalized hash contract and replace only the existing blueprint:source-hash value. Do not regenerate or rewrite the overview body. This keeps completion progress from looking like plan drift and migrates older exact-byte fingerprints.
• Fix - archive it to blueprint/history/fixes/name.md. A fix isn't a build-plan item, so there's nothing to check off.
• Rollback - archive it to blueprint/history/rollbacks/YYYY-MM-DD-<exact-target-archive-stem>.md, using the spec's exact Target archive filename without .md, including any build suffix. Preserve the original completed feature archive. Create blueprint/history/rollbacks/ first if an older Blueprint installation does not have it yet. Uncheck the exact target item in blueprint/build-plan.md and its parent when applicable, then append a concise note to the target line with the rollback date and archive path. Keep the feature number stable. If the user later decides the feature is permanently abandoned rather than pending rebuild, that roadmap decision is a separate plan edit.

Archive resolved findings. If blueprint/context/findings.md holds any findings, include a ## Findings section in the prepared archive with every closed, accepted, or invalid entry at its final status (accepted entries keep their recorded reason). Prefix feature IDs with the normalized stable ID and, for N > 1, -build-N: feature 12's first F-03 becomes 12/F-03, while attempt 2 becomes 12-build-2/F-03. Derive N from the verified spec/history proof, never arbitrary filename text. Fixes and rollbacks use their archive filename as the prefix. An entry carried forward from earlier work archives with the item that resolved it; its Found line preserves where it came from. Only closed, accepted, and invalid entries are resolved for archival. A fixed entry is not resolved at any severity: never append it to the archive or remove it from the live ledger.

Archive independent review. When a current passed receipt exists, include a ## Independent review section in the prepared archive with the receipt fields, commands, safe evidence references, findings, and remaining risk from blueprint/context/review.md. Preserve the full target and base SHAs, spec hash, the original Spec snapshot field when present, base ref, builder adapter and model, requested reviewer, model, and execution, actual reviewer adapter, model, and execution, Check result, fresh-context declaration, and review time. Do not archive a stale, pending, changes-requested, or malformed record.

Validate and place the fully assembled archive first. Complete only the exact plan/overview changes above and any approved consumed-prototype cleanup below. Read the archive back and confirm that its spec, findings, and review match their inputs before resetting live evidence. Reset the active spec last.

Discard consumed prototypes. If this feature built the look from prototypes/

• its Design reference pointed there and an early step ported prototypes/theme.css into the app - delete the prototypes/ folder now. The tokens live in the real stylesheet and the HTML mockups were always throwaway; fold the deletion into this feature's commit. Skip this if the feature didn't consume prototypes.

Then remove only the archived entries from the ledger. Entries with open, fixed, or unverified status stay in the ledger with their IDs so they are never silently dropped. A fixed P2/P3 finding does not block completion, but it must remain verbatim for a later /audit re-review. When no open, fixed, or unverified entries remain, reset the ledger to exactly this stub, and create it the same way if the file is missing (an older install):

# Findings

> **Generated file.** The findings ledger: review findings raised by `/audit`
> against the work in progress, each with a durable ID, severity (P0-P3), and
> status. `/implement` marks repaired findings `fixed`, a later `/audit` pass
> moves them to `closed`, and `/complete` refuses to land while any P0 or P1
> finding is `open` or `fixed`, then archives resolved findings with the work
> and resets this file.

_No findings recorded. `/audit` appends findings here when it finds them._

Then reset blueprint/context/review.md to exactly this stub, creating it when an older installation does not have it:

# Independent Review

> **Generated file.** Holds the active independent-review request or latest
> receipt for the current work item. `/audit independent current` prepares a
> handoff against an approved checkpoint, a fresh reviewer context completes it,
> and `/complete` refuses stale, pending, or changes-requested review state.

_No independent review requested. Run `/audit independent current` to prepare one._

Keep every unresolved entry in the ledger. Do not replace it with the empty stub while it still contains any open, fixed, or unverified finding. After archiving resolved findings, replace blueprint/context/current-feature.md with the canonical stub below. Do not paraphrase it or substitute an abbreviated "no work" stub. Before committing, read the file and confirm it exactly matches:

# Current Feature

> **Generated file.** Holds the one feature, fix, or rollback being built in this checkout. Run
> `/feature <number-or-name>` to spec a build-plan feature, or `/fix "<bug>"` for
> an ad-hoc fix. Use `/rollback <completed-feature>` to plan a safe reversal.
> Build one thing at a time in this checkout; `/complete` archives it under
> `blueprint/history/` and resets this file.

_Nothing in progress. Run `/feature`, `/fix`, or `/rollback` to start._

When no open, fixed, or unverified ledger entries remain, confirm blueprint/context/findings.md exactly matches the canonical Findings stub above. Otherwise, preserve the remaining entries without rewriting them. Confirm blueprint/context/review.md exactly matches the canonical Independent Review stub above.

Don't commit yet; the next step makes one work commit covering the code and these documentation changes. The archive is the build history.

Step 2 - make the work commit

Show the complete product and logging diff with the proposed commit message, then obtain explicit commit approval. Only then stage the reviewed branch work (any uncommitted step work plus the Step 1 logging changes) and make one conventional work commit (for example feat: <feature>, fix: <name>, or revert: roll back <feature>). Verify, or the fallback build and tests, must pass first.

Step 3 - land the work

Follow only the configured path.

Local merge

With git.landing: "local-merge":

1. Confirm the recorded local default branch has not advanced and the final work commit is unchanged. Squash-merge into that default branch only with the user's explicit go-ahead, so the work lands as one clean commit regardless of how many checkpoints the branch carried.
2. Verify the resulting default-branch commit, parent, archive, and full tree using reference/completion-recovery.md, then perform approved branch cleanup.
3. Stop and ask whether to push the local default branch to its upstream. The merge approval does not count as push approval.
4. Push the default branch only after a separate explicit yes in the current chat. If the repo has no remote or upstream, say so instead of guessing.

Pull request

With git.landing: "pull-request":

1. Require a selected configured remote, a known remote default branch, and an available authenticated hosting CLI or API. Prefer the work branch's configured upstream remote; otherwise use the only unambiguous remote or ask the user to choose. Confirm the exact work commit and branch are unchanged. Do not fall back to a local merge or direct default-branch push when any prerequisite is missing.
2. Show the target remote and base branch, exact branch to push, proposed pull request title, and concise body. State that the pull request must use squash merge to preserve Blueprint's one-work-item, one-default-branch-commit history.
3. Obtain one explicit approval for the feature-branch push and pull request creation. Configuration never supplies this approval. Only after approval, push that branch with upstream tracking and open the pull request against the confirmed default branch.
4. Verify that the pull request head is the exact final work commit and report its URL plus check status. Never merge the pull request, enable auto-merge, delete the remote branch, or push the default branch from this approval.
5. Stop with the work ready for provider review and squash merge. If /complete is resumed after the provider reports it merged, follow reference/completion-recovery.md; verify the exact pull request and squash commit before reporting completion or offering local branch cleanup.

Then point the user at /feature, /fix, or /rollback for the next thing.

Finish with a concise How to try it note for the completed work. For a rollback, explain how to confirm the removed behavior is gone and name one unaffected regression path. If the manual path is more than a couple of steps, tell the user to run /check guide latest; that command can read the archived feature after current-feature.md is reset.

Rules

• The work item is the unit of history: one squashed feature, fix, or rollback commit on the default branch, even if the branch carried several checkpoint commits.
• A rollback preserves the original feature archive and adds a separate rollback archive. Never rewrite history to make the feature look as if it never existed.
• Don't merge unfinished or failing work. The documented Verify command, or the fallback build and tests, must pass first.
• Never merge while a P0 or P1 finding is open or fixed in the ledger. The recorded ways past the gate without code are accepted (only by the user's explicit decision, with their reason) or invalid (only from re-examination evidence or the user's explicit call); both travel into the archive, never a silent drop.
• Never merge with a required or explicitly initiated independent review that is missing, pending, changes-requested, malformed, or stale. The user may explicitly cancel a manual review before completion, but the agent never resets or waives it on the user's behalf.
• Merging and pushing are the user's calls. Local landing needs explicit merge approval, then separate default-branch push approval. Pull-request landing needs explicit branch-push and pull-request approval, and never includes merge approval.
• Never treat /complete, configuration, or "looks good" as permission to push, open a pull request, enable auto-merge, or merge.
• One item per completion. If a parent feature still has unchecked sub-features, leave the parent unchecked.

Formatting

Format the output to match the project's conventions in blueprint/context/ai-interaction.md: concise, scannable markdown, with lists for enumerations and tables for matrices rather than dense paragraphs.