Release v7.131.5

Changed

• The documentation skills now judge a page by what a reader who did not write it can understand and do. Each skill has a distinct role: writing and structure, engineering docs, examples, retrieval-friendly pages, and voice. Guidance asks for source-backed claims, runnable tasks with visible checkpoints and recovery paths, examples that state their source and what has been verified, and claim-preserving rewrites. (part of #973)
• A new reader-review reference describes an uncoached review by a fresh reader, the smallest repair for each confusion, and keeping comprehension, source, compile, runtime and deployed evidence separate. (part of #973)
• The documentation rule covers Platform and component naming, independently adoptable components, stable identifiers and a pragmatic use of Diátaxis. The write-documentation prompt reads the applicable skills before drafting. (part of #973)