Release v4.100.0

Summary

Personal data and operational secrets are now marked with plain keywords after a concept's type, and can state what GDPR and Chronicle need: a special category or criminal-offence data for personal data, and an encryption scope for secrets.

Added

• pii special <category> marks GDPR Art. 9(1) special-category data (health, genetic, biometric, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, sex life or sexual orientation), and pii criminal marks Art. 10 criminal-offence data (part of #557)
• secret scope subject|namespace|global states the Chronicle encryption scope for an operational secret (part of #557)

Changed

• Personal data is marked with the keyword pii after the concept type (concept Email : String pii); personal is accepted as the same marker. Operational secrets are marked with secret, because "sensitive" reads as GDPR special categories (part of #557)
• An unknown compliance marker is an error instead of being ignored (part of #557)

Deprecated

• @pii, @sensitive and sensitive (including sensitive reason) still compile, with an information diagnostic and a repair for the line or the whole document that keeps every reason (part of #557)