# Vertical Full-Stack Sprint Delivery

Use this workflow when a sprint is defined as a complete vertical PR rather than separately approved backend, API/UI, and release packages.

## Core rule

Backend, API/UI, verification, UAT, review, documentation, commit, push, and remote verification are internal phases of one sprint. Do not stop for new approval between them unless the user explicitly inserted an approval gate or a concrete external blocker prevents continuation.

## Sequence

1. **Preserve the exact starting tree**
   - Verify worktree, branch, HEAD, status, and `git diff --check`.
   - Preserve an existing uncommitted diff when it is the declared working basis.
   - Do not repeat an already settled contract analysis.

2. **Implement one vertical user outcome**
   - Include additive migration, backend/service behavior, API/OpenAPI, complete affected frontend flow, focused tests, and canonical documentation when relevant.
   - Defer adjacent redesigns, optimizations, and later-phase features.

3. **Verify efficiently**
   - Run focused tests during development.
   - Run each complete relevant suite once near the end, not after every small edit.
   - Run typecheck/build, lint/compile, migration, OpenAPI, auth/write-security, secret, and Git-safety gates as applicable.

4. **Run synthetic responsive UAT**
   - Use an isolated runtime and synthetic data outside the repository.
   - Exercise the actual workflow, duplicate-action protection, stale-state invalidation, active/history reads, read-only boundaries, localized errors, and no-overflow behavior.
   - Verify desktop, tablet landscape, and narrow mobile viewports.
   - If the active browser cannot resize, a same-origin fixed-size iframe can create a real CSS viewport: verify iframe `innerWidth`, root `scrollWidth/clientWidth`, interact via `contentDocument`, and take visual screenshots. Prefer a normal viewport-capable harness when available.

5. **Perform exactly one final review**
   - Review the complete diff after main suites and UAT evidence exist.
   - Fix only justified sprint-relevant findings; defer larger extensions.
   - Do not start a second general review loop. After fixes, rerun focused affected checks and only relevant release gates.

6. **Complete delivery**
   - Update the existing canonical handoff/decision record instead of creating parallel documentation.
   - Include purpose, data/API contract, migration, security boundaries, UAT result, and rollback guidance.
   - Commit using repository convention, push only the declared branch, and verify upstream/local/tracking/remote SHA equality, `ahead/behind = 0/0`, and a clean tree.

## Blocker discipline

- Elapsed turn time is never itself a blocker.
- Test failures, review findings, incomplete implementation, and remaining work are normal work.
- Report a technical blocker only with a concrete tool/provider/gateway/runtime error or exception that prevents the required path after safe alternatives are exhausted.
- Do not return a progress-only final response; continue through Definition of Done.

## Reporting

Return one compact evidence-based sprint report after completion: delivered behavior, exact gates/UAT, review disposition, commit/remote verification, clean-tree evidence, and exactly one next vertical sprint when requested. Avoid long lists of intentionally unperformed actions.