Release: Operating Model Drift Tracking

Forgeflow 4.3.56 adds the Phase 3 project operating-model trend loop. The operating model now records compact append-only history, project trends show advisory drift, and learning status treats the model as a local guidance signal.

Drift History

• /forgeflow-project-model appends compact history records under .forgeflow/<project>/context/operating-model-history.jsonl.
• Snapshots normalize domains, high-care files, risk zones, and validation patterns so ordering churn does not create false drift.
• The latest JSON and Markdown model artifacts remain the current-state source for context-pack injection.

Project Trends

• /forgeflow-trends now includes an Operating Model Drift section.
• Drift reports added and removed domains, high-care files, risk zones, and validation patterns.
• Invalid or unsafe history surfaces as invalid and recommends forgeflow-project-model --refresh.

Learning Signal

• /forgeflow-learning-status includes project-operating-model as a local advisory signal.
• The signal uses the history artifact timestamp for age and reinforcement decay.
• Drift remains advisory only and does not block work by itself.

Validation

• Full scripts/forgeflow/test-*.js suite
• node scripts/forgeflow/test-build-project-operating-model.js
• node scripts/forgeflow/test-show-project-trends.js
• node scripts/forgeflow/test-show-learning-status.js
• node scripts/forgeflow/smoke-check.js --mode source --json
• node scripts/forgeflow/render-release-readiness.js --json
• git diff --check