feat(standards): add versioning + changelog standard, release templates, and Drone version guard

Add lib page 11 (SemVer contract, pre-1.0 rule, tag==version invariant, Keep a Changelog), the releasing wiki runbook, and canonical release templates (CHANGELOG.md, VERSION). Vendor them into the MCP bundle as templates/release + release.json and expose registry://release with list/get tools. Add a changelog component to the app template. Enforce the tag<->version contract in both Drone shapes: Type A check-version and the backfill loop verify pyproject version; Type B adds a VERSION guard step.

standards/src/templates/release/CHANGELOG.md

@@ -0,0 +1,36 @@
+# Changelog
+
+All notable changes to this project are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+### Changed
+
+### Deprecated
+
+### Removed
+
+### Fixed
+
+### Security
+
+<!--
+On release, promote the entries above into a new heading with today's date and
+leave a fresh, empty [Unreleased] section:
+
+## [0.1.0] - YYYY-MM-DD
+
+### Added
+- Initial release.
+
+Then update the compare links below. See the standard:
+Versioning & Changelog (registry://release).
+-->
+
+[Unreleased]: <repo-url>/compare/0.1.0...HEAD
+[0.1.0]: <repo-url>/releases/tag/0.1.0

standards/src/templates/release/VERSION

@@ -0,0 +1 @@
+0.0.0