MAS-WP-0005-T07: v0.2 draft bundle; mas_core accepts v0.1 and v0.2 statutes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 252470@bnt-lap001
Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241

workplans/MAS-WP-0005-spec-errata-v0-1-1.md

@@ -223,7 +223,7 @@ statute and the case-insensitive ticket service. Then re-run a smoke test
 
 ```task
 id: MAS-WP-0005-T07
-status: progress
+status: done
 priority: medium
 ```
 
@@ -234,6 +234,23 @@ integration section) and the SCP-7 statute field
 `mas_core` accepts statutes with `mas_version` 0.1 and 0.2, each validated
 against its own schema. Discovery accepts both.
 
+- 2026-10-18 done:
+  - `mas-v0.2-spec/` draft: §6.3 stand-ins with the matching order, §8
+    `resource_id_case`, §11 fields, §12.1 destination transforms, §12.2
+    informative integrations (IONOS, Google Groups), and §13 length after
+    transforms;
+  - schema v0.2 (`mas_version` 0.2, `alternate_syntax`,
+    `equivalence.resource_id_case`), an example statute and the CHANGELOG.
+    The grammar is unchanged; stand-ins are not canonical syntax.
+  - `mas_core`: one schema validator per version (`SUPPORTED_VERSIONS`);
+    `Statute` carries `mas_version`, `alt_resource`, `alt_interaction`
+    and `resource_id_case`; inheritance uses `dataclasses.replace`;
+    discovery accepts 0.1 and 0.2.
+  - Tests that used 0.2 as the "unsupported" example now use 0.3. 155
+    tests pass.
+  - The draft keeps 25 "v0.1" mentions for rules that are unchanged; align
+    the wording when v0.2 is finalized.
+
 ## v0.2 receiving side: stand-ins and resource_id_case in policy
 
 ```task