Release v1.5.0

Ante can now run as the onboarding service for a single Screenplay application, configured from one contract instead of hand-written Ante:* settings.

Added

• Ante:Onboarding configuration contract: host store, public and application URLs, sign-up creating or joining a tenant, allowed invitation types, grantable personas, locales, legal terms and mounted secrets, mapped onto the existing Ante:* settings when Ante:Onboarding:Enabled is true (#205)
• Legal terms read from files (Ante:Legal:Source=Files), versioned by content so editing a mounted file publishes a new version without a restart
• Secrets read from a mounted folder with one file per setting, so signing keys never pass through the command line
• Development mode for cratis run: a development signing key is generated and kept outside source control, and Ante refuses development mode for production-like environments or public URLs
• InvitationRejected generation 4 with the reasons PersonaNotGrantable and InvitationTypeNotAllowed, published only when the onboarding contract restricts personas or invitation types

Changed

• Hosts that enable persona or invitation-type restrictions must observe InvitationRejected generation 4 before upgrading Ante; hosts that do not use the onboarding contract see no change