grocery-app/docs/PLANS.md

Planning Template

Use this template for multi-step features, refactors, risky bugfixes, or DB work. Keep plans short and update them as evidence changes.

Goal

• What user-visible or operator-visible outcome should be true?

Context

• Relevant files, routes, data tables, docs, tests, and prior decisions.
• Current behavior and desired behavior.

Constraints

• External DB only; migrations go in packages/db/migrations.
• No cron, workers, or background jobs.
• RBAC must be enforced server-side.
• No secrets, receipt bytes, or full invite codes in logs.
• Preserve current behavior outside the target area.

Milestones

1. Recon and evidence.
2. Minimal design.
3. Implementation slice.
4. Tests and verification.
5. Documentation update.

Validation

• Commands to run.
• Manual checks needed.
• Negative cases to cover.

Rollback

• Files or migrations that would need reverting.
• Data or operator action needed, if any.

Open Questions

• Only questions that materially affect architecture, runtime behavior, public APIs, data storage, security, deployment, package manager, or dependency footprint.