Finish Feature (any stack)

Companion: /start-feature. Tracking + this repo's ids/labels: docs/project-tracking/GITHUB-PROJECTS.md.

Run in order. Repo / test command / label values come from this repo's GITHUB-PROJECTS.md config block. Nothing here is stack-specific — it drives .NET, Next.js, or any repo with a test command.

1. Suites green — state the counts

Run this repo's Test command from the GITHUB-PROJECTS.md config block — for example:

dotnet test                    # Blazor / .NET repo
npm test && npm run build      # Next.js repo (typecheck/build counts too)

Report exact counts (and a clean typecheck/build where that's the gate). Name any pre-existing failures with evidence. Failing tests / build = not finished.

2. Rebase onto the fresh default branch

git fetch origin and rebase (or merge) onto origin/<default-branch>. Re-verify build/tests if it moved.

3. Spec + issue reflect shipped vs remaining

• Update docs/specs/<slug>.md status if present.
• Remaining work → follow-up issues on the board (not prose-only).
• Do not claim Complete on unit tests alone when a live / integration retest is owed.

4. One changelog fragment

Write docs/project-tracking/changelog.d/YYYY-MM-DD-<slug>.md. Never edit CHANGELOG.md on the feature branch.

5. Open the PR

• Done-done: PR body includes Closes #<issue>.
• Live retest owed: use Refs #<issue>; after merge move to Verifying; close → Done only after live confirmation.
• Structure: Summary · Remaining / deferred (linked issues) · Verification · Operator actions.
• Do not merge from the task branch unless the operator asks.

Honesty bar

Report failed tests, skipped steps, and "not live-verified" plainly.