2 Commits

Author	SHA1	Message	Date
Claude	2556b8ab49	docs: Add simplified Rails Engine migration approach ... RECOMMENDED APPROACH: 12-14 weeks instead of 22 weeks KEY SIMPLIFICATIONS: - Use JSON storage for game state (already in that format) - 3 database tables instead of 10+ - game_instances (with player_state JSONB) - scenarios (with scenario_data JSONB) - npc_scripts (Ink JSON) - 6 API endpoints instead of 15+ - Bootstrap game - Load room (when unlocked) - Attempt unlock - Update inventory - Load NPC script (on encounter) - Sync state (periodic) VALIDATION STRATEGY: - Validate unlock attempts (server has solutions) - Validate room/object access (check unlocked state) - Validate inventory changes (check item in unlocked location) - NPCs: Load Ink scripts on encounter, run conversations 100% client-side - NPC door unlocks: Simple check (encountered NPC + scenario permission) WHAT WE DON'T TRACK: - Every event (client-side only) - Every conversation turn (no sync needed) - Every minigame action (only result matters) - Complex NPC permissions (simple rule: encountered = trusted) BENEFITS: - Faster development (12-14 weeks vs 22 weeks) - Easier maintenance (JSON matches existing format) - Better performance (fewer queries, JSONB indexing) - More flexible (easy to modify game state structure) - Simpler logic (clear validation rules) Updated README_UPDATED.md to recommend simplified approach first. Complex approach documentation retained for reference.	2025-11-20 08:21:08 +00:00
Claude	f2d1341b4f	docs: Update Rails Engine migration plans for current codebase ... Updated migration plans to reflect significant codebase evolution: NEW SYSTEMS DOCUMENTED: - NPC system (fully implemented with NPCManager, conversation state, events) - Event system (80+ events across codebase) - Global game state management (window.gameState.globalVariables) - Multiple scenarios (24 total, up from 1 originally planned) KEY UPDATES: - UPDATED_MIGRATION_STATUS.md: Comprehensive status of what's changed - What's implemented vs what still needs server-side integration - Updated timeline: 22 weeks (was 18 weeks) - New database schema requirements - Updated risk assessment - CLIENT_SERVER_SEPARATION_PLAN.md: Added 3 new systems - System 5: NPC System (hybrid approach confirmed) - System 6: Event System (selective logging) - System 7: Global Game State (server as source of truth) - Updated migration checklist: 9 phases (was 7) - Updated timeline: 18-22 weeks - README_UPDATED.md: New master index document - Quick start guide - Document index - What's changed summary - Timeline breakdown - Architecture decisions - Success metrics MIGRATION APPROACH: - Hybrid NPC approach: Scripts client-side, validation server-side - Selective event logging: Critical events only - State sync: Server as source of truth, client cache for performance - Incremental rollout with dual-mode support TIMELINE: 22 weeks (~5.5 months) - Added 4 weeks for NPC, Event, State integration - Original: 18 weeks → Updated: 22 weeks (+22%) All plans are complete, self-contained, actionable, and feature-focused. Ready for team review and implementation.	2025-11-20 07:42:23 +00:00