Delivery roadmap

This page indexes delivered capabilities. Current priorities, progress and blockers belong to the canonical plan; completed demo evidence belongs to VIN-155, and new catalog handoffs belong to VIN-288.

Completed foundation

• Authentication repairs, secure hashing, active-user checks and admin-only product writes.

• Precise GBP pricing, bounded product validation and database constraints.

• Reproducible Docker/PostgreSQL setup, migrations and safe demo/admin bootstrap.

• VINDOR Next.js catalog and product pages with filtering, responsive design and state handling.

• OpenAPI documentation, generated frontend types and Postman onboarding.

• Complete registration → login → profile → logout journey, desktop/mobile verification and account onboarding (#27).

• Backend/frontend CI, coverage, integration/browser checks and dependency auditing.

• Contributor/security guidance, development skills, ownership and naming conventions.

• Persistent signed-in cart API with ownership, stock-aware quantities, exact totals and database constraints (#71 / PR #79).

• Signed-in cart storefront: add/update/remove controls, persistence and account isolation with desktop/mobile verification and customer walkthrough (#72 / PR #80).

• Public-demo abuse throttling: fixed-window 429s on auth/write endpoints with documented limits and headers (#109, eviction follow-up #115).

• Development auto-delivery from verified main revisions, mirroring the production gate (#108, hostname fix #113).

• Application observability: Sentry error/tracing SDKs in the API and storefront with scrubbing and quota guardrails (#121, backend #122, frontend #123); development monitoring is verified under VIN-121 and joined traces under VIN-223. Production activation is outside that rollout.

• Typed SQLAlchemy 2.0 models across the API with identical schema (no migration change), plus the framework audit (#132/#133); its refresh-import and infrastructure-provider classifications were corrected during the September 19 audit.

• Owned order drafts and immutable GBP snapshots (VIN-118 / PR #177), followed by atomic placement with stock protection and customer-scoped idempotency (VIN-119 / PR #181).

• Cart fixture/actionability corrections (PR #187), followed by demonstrated mutation-deadline and offline-recovery fixes (VIN-89 / PR #252). Hosted persistence, recovery and account isolation passed for reviewed release a03545d; see cart boundaries and retained limits.

Retrospective record

The foundation above was completed before the Kanban board was created. The board-only card Delivered foundation — retrospective summary has been archived; this section preserves its historical context rather than representing it as an implementation ticket.

It covered the authentication/catalog foundation, reproducible local setup, VINDOR storefront, OpenAPI onboarding, full-stack CI and Wiki. The card referenced merged PRs #1–5, #7–8, #12–20 and #23; consult the repository PR history for individual changes. This is a retrospective baseline, not a claim that the remaining shopping journey is complete.

Current delivery plan

VIN-120 checkout, confirmation and history merged in PR #188, with passing CI and completed Codex/CodeRabbit reviews. VIN-30 hosted sandbox payments, inventory expiry and exactly-once release are implemented in PR #194, merged as 0e89efd. Hosted sandbox acceptance is complete; VIN-30 is Done. The Codex status-indicator follow-up remains deferred under VIN-38.

The single portfolio completion plan and checklist owns the sequence, progress and blockers. VIN-155 / ISSUE #155 is the completed-demo evidence index; new work uses its own epic. The board owns workflow state. This Wiki does not maintain a duplicate checklist.

Issue keys use VIN plus the actual GitHub issue number. VIN-158 / ISSUE #158 is limiter identity work; PR #163 implements its authenticated-write slice. See Testing and delivery for naming.

Azure and broader enterprise expansion remain deferred. Merged SDKs and skills are distinguished from operational verification and completed parent acceptance.

Additional controls such as static backend typing, code scanning and required-check rules should address a demonstrated need and arrive in focused PRs. Legacy AWS infrastructure is reference material, not the approved hosting path.

Background context: portfolio objective and implementation roadmap.

Delivered catalog release

The owner selected a workspace/home-office catalog of up to 100 products, with roughly 60 as a planning target. VIN-288 links the five catalog stories and their dependencies. The first unblocked story was full-catalog queries in VIN-289. That backend story is now delivered in PR #307, with development query verification recorded on VIN-289. VIN-287 is delivered in PR #309: the storefront uses server-rendered pages, URL filters, and share/return navigation. VIN-290's category browsing is merged in PR #316 (4dad3b0). Shoppers can keep search and sort while choosing one workspace category. That journey was checked on the development storefront. VIN-291 is delivered in PR #320 (c4b05b3): a product keeps one local photograph when it is renamed, and the page shows optional material and millimetre facts. That was checked on the development storefront. VIN-292 is delivered in PR #324 (9653a91): the development catalog was imported on 8 October 2026 to 60 products after backup backup_vin292_20261008T183008Z, and one fictional sandbox purchase was paid. VIN-288 is delivered. The parent epic is closed and Done. VIN-293 is delivered in PR #334 (7958b0e): Sign in to add returns to that product with its collection filters. The development journey was checked, and production is on the same revision. The versioned plan update merged in PR #301.

Use the Customer features view for the shopping roadmap and the Technical improvements view for security, monitoring, CI and feature-flag discovery. Priorities and acceptance stay on the source issues rather than a second checklist here.

Catalog administration (VIN-295) is explicitly deferred; single-shop versus separate-shop discovery remains open. VIN-300 saves later account recovery and purchase-support work. These are new roadmaps, not extra requirements for the completed demo.

Ticket execution

PR #191 delivered the deliver-ticket workflow. Fresh repository tasks read the saved execution mode through AGENTS.md. Mode changes require an explicit owner request; the workflow does not install scheduled wakeups.

PR #192 also delivered connector-facing review guidance: inspect related entry points and consolidate root causes. This guides review behavior without guaranteeing exhaustive or single-round approval.

Payment and monitoring acceptance are verified. Use the canonical plan for the next story and current progress; payment evidence preserves the earlier checkpoint.

Telemetry scope

The monitoring runbook explains delivered checkout/webhook/inventory signals, privacy allowlists and joined development traces. Expected declines are separate from technical failures; sampled traces are not total traffic or a percentile baseline. New signals require serialized-envelope verification. Optional browser LCP/INP/CLS belongs to VIN-204, not another portfolio completion gate. No extra vendor, Collector or paid service is included.