Release v7.48.4

Changed

• Agents now choose how to build a Chronicle read model with one ladder that matches the Chronicle documentation: model-bound attributes first, fluent IProjectionFor<T> when the mapping needs structure, and a reducer when the logic reads better as code, as a normal choice rather than a last resort. (#660)
• Agents write Chronicle self-reducing read models (static Reduce methods on the read model, Chronicle 19.58.0 and later) as the default reducer form in .NET, use IReducerFor<T> when the fold needs injected services or must live apart from the model, and nominate a plain class only when the contract assembly cannot reference Chronicle. The guidance covers marker-free discovery on upgrade, near-miss warnings, replay hooks, ownership conflicts, testing, and that decision reads do not admit reducers. (#660)
• Arc guidance keeps the read model, its Reduce methods and its queries on one record, with RequireQueryAttribute and [Query] only for Arc versions before 22.90.0. (#660)