Add ruler decision system (CK-lite) to MVP scope

[Copilot]

Extends MVP with policy-based ruler decisions that indirectly affect village populations/stability and army morale/loyalty through mechanical modifiers. Positioned as "CK-lite" - explicitly excludes dynasties, diplomacy, and narrative mechanics.

MVP.md Changes

New Feature: Section 7 - Ruler Decision System

• 3 policy categories × 3 options each (Economic, Military, Population)
• Mechanical effects: stability modifies soldier generation, morale modifies combat, loyalty affects desertion
• Delayed consequences (5-10 tick delay), gradual stat recovery/decay to baseline
• Policy decision cooldown: 15 ticks between changes

Example policy effects:

Heavy Taxation: +20% income, -10% stability
Aggressive Training: +10% morale, -5% loyalty
Growth Focus: +15% population growth, -5% stability

Updated sections:

• Implementation roadmap: Added to Phase 3
• Technical requirements: New endpoints (POST /api/decision, GET /api/ruler-stats), enhanced models (Army + morale/loyalty, Village + stability/population)
• Success metrics: Added strategic depth (10-15% outcome variance) and decision impact (visible changes within 10 ticks)
• Out of scope: New subsection listing 12 excluded CK features (dynasties, diplomacy, succession, etc.)
• Effort estimate: 155-210 hours (was 130-185)

TICKETS.md Changes

New Ticket 7: Implement Ruler Decision System

• Acceptance criteria: RulerDecision model, policy state tracking, stat calculations, recovery/decay logic, 12+ unit tests
• Frontend: Policy UI, realm stats panel, visual indicators for affected entities
• Estimated 3 agent sessions

Updated Ticket 8 (Polish): Added ruler policy balancing and testing tasks

Implementation order: Total 18-23 sessions (was 16-20)

Design Constraints

System-driven mechanics only:

• ✅ Policy modifiers affect game stats
• ✅ Single ruler with periodic decisions
• ❌ No narrative events, dialogue, or story text
• ❌ No dynasties, succession, or character relationships
• ❌ No diplomacy, councils, or intrigue mechanics

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update MVP.md to Include Ruler Decisions and Population-Based Strategy</issue_title>
<issue_description>Modify the existing MVP.md document to incorporate a lightweight ruler decision system

The update should:

• Preserve all existing MVP scope and features
• Add a new section describing a single-ruler decision layer
• Define how ruler decisions indirectly affect:
  • village populations and stability
  • army morale and loyalty
• Emphasize policy-based decisions, delayed consequences, and system-driven outcomes
• Clearly position this system as CK-lite, explicitly excluding dynasties, diplomacy, or narrative-heavy mechanics
• Integrate the new system into the existing implementation roadmap and success metrics

The result should be a cohesive, high-level MVP document that explains how character-driven decisions enhance the current territory and army mechanics without expanding scope beyond MVP.

Also update TICKETS.md.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Update MVP.md to Include Ruler Decisions and Population-Based Strategy #17

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.