docs: bump foundation-000 and account-001 plans to v2.0.0, sync STATUS.md

[singyichen]

Summary

• Bump specs/foundation/000-foundation/plan.md to v2.0.0: full alignment with plan-template v1.13.6 (DB index analysis, state transitions, transaction boundaries, Pydantic 2b tables, frontend layout analysis, screen × API mapping, i18n key lists, Route → Controller boundary in flow diagram)
• Bump specs/account/001-login-email-password/plan.md to v2.0.0 (status Draft → plan-ready): same template alignment, plus module-first architecture (app/modules/auth/) with Repository layer and i18n-key-based exception design
• Sync specs/STATUS.md: foundation-000 note updated to plan v2.0.0; changelog entries added; repaired corrupted table rows (merged row and a stray duplicate account-001 row)

Changed Files

File	Change
specs/foundation/000-foundation/plan.md	plan v1.0.3 → v2.0.0 (template v1.13.6 alignment)
specs/account/001-login-email-password/plan.md	plan v1.0.0 → v2.0.0 (template v1.13.6 alignment, plan-ready)
specs/STATUS.md	version notes + changelog sync, table corruption repaired

Test Plan

• Docs-only change — no backend/frontend tests required per pr-flow
• Cross-reference review: plan frontmatter versions match plan changelogs and STATUS.md notes
• STATUS.md table renders correctly (corrupted rows repaired)

🤖 Generated with Claude Code

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[amazon-q-developer]

This PR successfully synchronizes the planning documentation for foundation-000 and account-001 with plan-template v1.13.6. The version bumps to v2.0.0 are properly reflected across STATUS.md and both plan documents, with consistent changelog entries. All documentation updates improve structure and completeness without introducing any defects.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Code Review

This pull request updates the implementation plans for the foundation-core and email/password login features to version 2.0.0, aligning them with the latest plan-template. The updates introduce comprehensive system architectures, database index strategies, UI component breakdowns, and structured task generation strategies. The review feedback highlights two key areas for improvement: first, replacing the deprecated, timezone-naive utcnow with timezone-aware defaults (such as func.now()) for the user model's timestamp fields; second, resolving a task duplication in app/core/security.py by scoping the login plan's security task to only cover JWT creation and decoding, as bcrypt hashing is already handled in the foundation plan.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.