Release v3.1.2

Added

• A Cratis site reference for the documentation writing skill: which teaching components to use (YouWillLearn, Recap, client-language tabs), how to state an experimental product's maturity, how to state cross-product compatibility, what Prompter records as a documentation-gap signal, and who decides page structure.

Changed

• Tutorials start from the smallest safe setup and a convention-first snippet, and link the paradigm explanation (event sourcing, event modeling) without delaying the first success.
• Explanations of what happened after a code block must match the backend the reader actually built.
• AI-drafted narrative gets a revision pass against source evidence and voice before it ships.
• Coming-from-X pages follow a consistent shape: the reader's current code, the Cratis equivalent, and what changed. The other technology's code is accurate at a named version or labeled illustrative.
• Diagrams, use-case indexes and diagnostic documentation are asked for where they help, not on every page.
• Release notes state verified cross-product pairings, include a fix's root cause and regression guard as observable behavior, credit external contributors, and state a migration table's scope without claiming compatibility that was not assessed.
• Guidance on how a merged documentation change reaches cratis.io, and that restructuring navigation is not a side effect of writing one page.