Release v4.141.0

Summary

Concepts marked pii or secret now reach the executable model as ESM v13, so renderers can realize personal-data and secret protection from it instead of refusing the whole application.

Added

• Concept compliance markers (pii, pii special <category>, pii criminal, secret, secret scope subject|namespace|global) bind into the executable model as ESM v13, as an optional compliance member on the concept that applies wherever the concept is used (part of #141)
• Only models that use a marker select ESM v13; models without markers keep their exact executable-model bytes and revision (part of #141)
• ESM v13 golden vector and concept compliance canonical corpus for consumers to verify against (part of #141)
• Concept documentation on when to mark a concept as personal data or a secret, when not to, the refusals below and how to test a protected model (part of #141)

Changed

• Models with protected concepts now bind and run their specifications instead of failing with PLAY0268; markers do not change reference-evaluator outcomes, and free-text reasons stay report-only (part of #141)
• PLAY0268 now refuses compliance on enum concepts and on concepts used as event-source or stream identities, and refuses an event that holds a personal or subject-scoped secret value together with an explicit subject mark until subject lineage is admitted (part of #141)
• The MCP readiness text and editor hover documentation describe concept compliance as executable in ESM v13 (part of #141)