Implement the accepted Vit Store audit corrections#198

openedJul 18, 2026byAAviddaram

What to build

Coordinate the 26 accepted audit corrections as independently grabbable changes. Preserve Customer shopping, User dashboard, Order, Payment, Delivery zone, Messenger, deployment, and maintenance behavior except for each child’s exact correction.

Security and operations work must remain defensive: never expose credentials, Customer data, environment identifiers, or operational misuse detail. Use existing static/build checks and real browser, API, Worker, Messenger, or focused CLI proof with disposable data; do not add unit or integration tests. Coordinate with adjacent open issues without closing or modifying them.

Acceptance criteria

  • The 24 active corrections are completed in dependency order; the two deferred assistant corrections remain explicitly non-blocking until assistant production work resumes.
  • Each child has real-system proof and applicable existing static/build checks.
  • Each active correction begins with its bounded evidence check and stops for human input if consequential evidence is unavailable or ambiguous.
  • No rejected or discussion-only finding is included.

Blocked by

None — children carry their own dependencies.

Child issue index

Active (ready-for-agent)

Deferred (ready-for-human)

Implementation pass complete at v2 SHA e6c36879414326fc7f6edff2625616e733ad9e9b.

  • 18 accepted non-assistant corrections are merged and their child issues are closed.
  • Draft PRs remain intentionally unmerged for #200/#225, #205/#244, and #212/#234.
  • #200 and #205 need an approved authenticated disposable Admin User/session for required signed-in browser proof.
  • #212 needs an approved non-production QPay/database/KV environment for real provider proof.
  • #215 needs a decision on Admin route-generator normalization before stale-route deletion can proceed.
  • #222 needs an owner decision for the runnable Product import workflow and any private structured-log consumer.
  • #223 needs sanitized deployed migration-table/schema inventory before an append-safe repair can be designed.
  • #210 and #214 remain intentionally deferred with assistant work.

No remaining child issue is labeled ready-for-agent; the parent remains ready-for-human. Release QA and promotion should wait until the applicable blockers are resolved and the exact staging SHA can be frozen.