Release v7.48.0

Summary

Agents now choose how a write-side rule holds in Arc + Chronicle, and stop presenting plain reads, validators or concurrency: true as enforcement.

Added

• A shared reference on choosing how a rule holds, reached from the decision-read, command, validation, constraint, read-model, reducer and Screenplay consistency skills. It contains:
  • routing steps and a decision matrix by rule shape, with what never to use and what is too much
  • plain reads by backing, and constraint limits
  • Arc and Chronicle traps, costs, and a checklist for generated code (#661)
• Evaluation cases for the common traps (#661):
  • a plain or passive read used as a guard
  • a validator used as a guard
  • concurrency: true
  • rules that span two keys
  • uniqueness through a constraint
  • refused decision-read shapes
  • unit-of-work commit timing in ASP.NET Core
  • when not to use decision reads

Changed

• The rules and skills no longer recommend a passive read model for command-side decisions without saying it guards nothing. Passive is current, not protected (#661)
• Corrected guidance (#661):
  • which command property Arc uses as the event source
  • when ARCCHR0002 fires
  • that [RemoveConstraint] also releases a [Unique] event type
  • what a decision guard detects when another writer has no guard
  • what an empty protected commit validates