Release v6.3.0

Changed

• The Screenplay skills now describe Screenplay 4.31.0. Every example in them compiles with that version with zero diagnostics, and both complete examples pass the reference runner.
• Reaction triggers can declare the views an automation decides from: reads <View> [as <alias>] [by <trigger value>]. The skills cover:
  • the alias rules, which are the same as for commands (PLAY0410–PLAY0412);
  • by naming a trigger value (PLAY0442);
  • clock triggers reading whole views only (PLAY0443);
  • the @reads escape (PLAY0175, PLAY0444);
  • for each <View> being reserved;
  • trigger reads, like command reads, giving no runtime protection yet.
• Model authoring explains how the ESM version (v1, v2 or v3) follows from what a model uses. It separates four states: parsed, bound, reference-executed and target-executed. A table checked against the binder lists what binds, what binds only as opaque code, what binds but the reference execution plan refuses, and what blocks binding.
• Model authoring covers code attachments (loading, content hashes, source maps) and describes how comments are kept and reviewed.
• Command guidance covers read aliases, validation severity, the matches email pattern, authorization order, one require per policy, what produces can bind, and unique constraints with their lifecycle forms.
• Projection guidance follows how Chronicle interprets projections: an unkeyed from routes by event source, every runs for a level's from and join events, and join, all and auto-map behave as Chronicle lowers them. It also covers bodied reducers as opaque code and projection variants.
• Specification guidance is rewritten for given caller, then denied, when append, scenarios without a when, subset versus exactly comparisons, events in any order, and typed values. It includes one complete example whose six specifications pass the reference runner.
• Query and screen guidance states what from parameters and observable guarantee, which query shapes bind, how to specify query authorization, and how UI interactions (behavior, on, uses) differ from application triggers.
• Captures and reactions guidance scopes the unknown-trigger warning and describes reaction code as an attachment.
• Decision 0006 is shown as shipped in 4.31.0. Decisions 0007–0014 are marked as not yet available.

Fixed

• Removed the advice that reads plus concurrency protects a decision. The executable model rejects both (PLAY0271).
• Removed the projection-level key from the examples. It routes nothing (PLAY0381).
• Binding no longer implies the reference runner will run a model. The skills list the projection constructs the reference execution plan refuses: a projection-level remove via join, all beside removals, children or nested, join/children/remove via join inside nested, and event-context values other than the event source identity. One of these stops every specification in the model.
• The variant example keys everything by the event source and explains that sibling removal always uses the event source identity.
• A read model now needs one unambiguous identifying by property, not exactly one keyed query. Several keyed queries over the same property bind.
• Screen file references are described as UI realization files that are never loaded or checked, not as attachments.
• Replaced the fixed list of "40 unsupported constructs" with the current executable limits.
• Removed the claim that a reaction cannot declare the state it consults.