feat: add documentation maintenance rules to steering, update migration number to 036

.kiro/steering/development-process.md

@@ -98,3 +98,18 @@ Ingestion jobs MUST include `source_id`, `source_type`, `ticker`, `company_id`,
 - Do NOT create large summary/success markdown files after each step
 - Keep notes short, concise, and organized under `docs/notes/`
 - If a note isn't useful for future reference, don't write it
+
+## Documentation Maintenance on Feature Changes
+When implementing a feature or fix that introduces an impactful change, update the relevant documentation as part of the same commit or task. "Impactful" means any change that affects how someone installs, deploys, configures, operates, or understands the system. Specifically:
+
+- **New database migrations**: Update `docs/architecture-data-pipeline.md` or `docs/api-reference.md` if new tables, views, or endpoints are added. Update `project-context.md` steering file with the new migration number.
+- **New API endpoints**: Update `docs/api-reference.md` with the endpoint path, method, parameters, and response shape.
+- **New services or service changes**: Update `docs/architecture-docker-compose.md` and `docs/docker-deployment.md` if a new service is added or an existing service's configuration changes.
+- **Helm chart changes**: Update `docs/helm-reference.md` if new values, services, or config options are added.
+- **New environment variables or secrets**: Update `docs/LOCAL_DEV_SETUP.md` and the project-context steering file.
+- **Install/deploy script changes**: Update `deploy-docker.sh`, `docs/docker-deployment.md`, or the relevant runme scripts if the deploy process changes.
+- **Frontend route or page additions**: Update `docs/api-reference.md` (if it covers UI routes) and ensure the nav item is documented.
+- **README.md**: Update the top-level `README.md` when a major new capability is added (new signal layer, new dashboard section, new trading feature).
+- **Steering files**: Update `.kiro/steering/project-context.md` when migration numbers advance, new services are added, or key conventions change.
+
+The goal is that someone reading the docs can always understand the current state of the system without reading the source code. When in doubt, update the doc.

.kiro/steering/project-context.md

@@ -81,13 +81,14 @@ When a full reset is needed:
 ## Database Migrations
 - Located in `infra/migrations/001_*.sql` through `030_*.sql`
 - Applied automatically by `runmefirst.sh` in sorted order
-- Next migration number: **031**
+- Next migration number: **036**
 - Key migrations:
   - 016: Global news interpolation (global_events, macro_impact_records, exposure_profiles, trend_projections)
   - 017: Competitive intelligence (competitor_relationships, competitive_signal_records)
   - 024: Trend history time-series table
   - 026: AI agents management (ai_agents, agent_performance_log)
   - 027: Agent variants (agent_variants table for A/B testing)
+  - 035: Model validation (prediction_snapshots, prediction_outcomes, signal_evidence_links, model_metric_snapshots, v_prediction_performance, v_source_performance)
 
 ## Key Conventions
 - All services use `services/shared/config.py` for configuration via env vars