chore(release): prepare 0.2.0

Every platform workspace package and every public @ekklesia/* package
declares 0.2.0, and the deploy README's image build example names it.
templates/module keeps its own version.

0.2.0, not 0.1.3: before 1.0 a minor version is the breaking one
(docs/development/releases.md, ADR 0054), and since 0.1.2 main has
broken modules, module authors, and operators:
- #64 (ADR 0048): one generic image; installed modules live outside it;
- #66, #72 (ADR 0049, 0050): modules install as Module Package v1, and
  move to the Module Database ABI;
- #71: the manifest v8 cutover; v7 manifests are refused;
- #79 (ADR 0053): the curated SDK drops defineModuleSchema and the
  legacy ModuleDatabase type;
plus #67 (AGPL), #74, #77 (licensing, native targets), and the public
package train (#80, #81). It is also the first package train to publish:
0.1.2 never will be.

Because 0.2.0 is outside ^0.1.0, the same change moves to ^0.2.0:
- the standalone fixture's @ekklesia ranges and its exact module-pack pin;
- the compatibility ranges of the modules built for this release: the
  template, the standalone fixture, and the native proof module;
- the test fixtures that model a module of the current release, or the
  current platform's versions;
- the module-development guide's examples, and the release guide, which
  now names what a minor bump moves.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/module-development/README.md

@@ -76,7 +76,7 @@ entrypoints. A module in its own repository depends on the published packages in
 > **Status:** the packages are published by release
 > ([ADR 0053](../architecture/decisions/0053-standalone-module-development-packages.md),
 > [Releases and the public package train](../development/releases.md)). The first published train
-> is the next platform release after 0.1.2.
+> is 0.2.0, the platform release after 0.1.2.
 
 A module does not need an Ekklesia checkout. Do not clone Ekklesia and put your module in its
 `modules/` directory: your module is its own repository, and it depends on Ekklesia's
@@ -131,17 +131,17 @@ import it yourself, because what it exports is the platform's, not a supported a
     "build": "tsc --project tsconfig.build.json && ekklesia-build-module-ui"
   },
   "dependencies": {
-    "@ekklesia/module-database": "^0.1.2",
-    "@ekklesia/module-sdk": "^0.1.2",
-    "@ekklesia/module-ui-sdk": "^0.1.2",
-    "@ekklesia/ui": "^0.1.2",
+    "@ekklesia/module-database": "^0.2.0",
+    "@ekklesia/module-sdk": "^0.2.0",
+    "@ekklesia/module-ui-sdk": "^0.2.0",
+    "@ekklesia/ui": "^0.2.0",
     "react": "19.2.8",
     "react-dom": "19.2.8"
   },
   "devDependencies": {
-    "@ekklesia/module-pack": "0.1.2",
-    "@ekklesia/module-ui-build": "^0.1.2",
-    "@ekklesia/typescript-config": "^0.1.2",
+    "@ekklesia/module-pack": "0.2.0",
+    "@ekklesia/module-ui-build": "^0.2.0",
+    "@ekklesia/typescript-config": "^0.2.0",
     "typescript": "7.0.2"
   }
 }
@@ -366,8 +366,8 @@ without executing module code:
   "name": "Calendar",
   "version": "0.1.0",
   "compatibility": {
-    "platform": "^0.1.0",
-    "moduleSdk": "^0.1.0"
+    "platform": "^0.2.0",
+    "moduleSdk": "^0.2.0"
   },
   "dependencies": {
     "modules": {