[Post-release] Track accepted release follow-up risks

[JoelA510]

Summary

Track accepted non-blocking risks left after release hardening. These are not release blockers and should be handled as narrow follow-up work.

Follow-ups

• Spanish human review: es.json remains machine-translated and review-required; do not market Spanish support until native-speaker review is complete.
• Legacy E2E curation: keep npm run test:e2e:release, npm run test:e2e:mobile, and npm run test:e2e:a11y as release gates while stale broad legacy scenarios are curated.
• Bundle/chunk warning: production builds pass, but Vite still reports a large chunk warning; address in a dedicated performance/chunking PR if needed.
• Dependency-order enforcement: dependency-order completion prompts are not currently trusted release behavior; future work must enforce this below UI at DB/API layers before it becomes a release gate.

Source

Recorded from docs/testing/release-readiness-ledger.md after PR #260.