hardenlisted

# Stage 6G: Error Handling, Network Failures, and Edge Cases Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/harden-detailed-guide.md` for the complete hardening procedures, teammate spawn prompts, error pattern catalogs, and report templates. Lead a multi-agent error resilience hardening project. Systematically review the COMPLETE product for error handling gaps, network failure scenarios, race conditions, and edge cases that individual feature implementations may have missed. **Stage Sequence** (recommended ordering): Stage 5B → 6A/6B/6C (parallel) → 6E (Code Refactoring) → 6F (Seed Data) → **6G (this stage)** → 6D (Documentation) → 6H (Pre-Launch) → 6V → 6R → 6P/6P-R → 7 (Deploy) ## Rate Limiting Scope Boundary (6A vs 6G) > **Cross-stage coordination**: Before implementing data-mutation rate limiting, read `./plancasting/_audits/security/report.md` from Stage 6A to verify which endpoints are already rate-limited (auth endpoints). Implement only DATA-MUTATION rate limiting here — auth endpoint rate limiting was handled in 6A. Stage 6A implements rate limiting for **AUTH endpoints** (login, signup, password reset, forgot password / password reset initiation, MFA, session management, password change, email verification, invitation acceptance). Stage 6G (this stage) implements rate limiting for **DATA-MUTATION endpoints** (create, update, delete operations, file uploads, user profile updates). Verify 6A's auth-endpoint rate limiting before implementing to avo