Merge master back into v3-ddd (post-squash sync of #10)

#10 squash-merged the v3-ddd line into master, so the branch history was
never ancestored — GitHub kept showing v3-ddd as ahead. This merge makes
v3-ddd a descendant of master. SKILL.md add/add resolved to master's
copy (the as-built banner).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011L6cwv6s34nJew65PC7jKN

Author: titustangible

.claude/skills/tangible-ddd/SKILL.md

@@ -13,27 +13,28 @@ Tangible DDD is organic. Every pattern was won through real problems, not textbo
 
 ---
 
-## ⚠️ Upcoming: 0.2.0 Event Taxonomy (DESIGNED, NOT YET BUILT)
+## ⚠️ 0.2.0 Event Taxonomy (BUILT — merged 2026-07-10)
 
-A hard-break redesign of the event system is fully specced. **Before writing any NEW
-integration event, listener, or await code — or implementing 0.2.0 itself — read:**
+A hard-break redesign of the event system, now merged (PR #9). Consumers
+(tangible-datastream, tangible-cred) have migration branches. **Before writing any
+NEW integration event, listener, or await code, read:**
 
 - `docs/integration-event-evolution.md` (handoff — start here)
 - `docs/superpowers/specs/2026-07-03-integration-event-taxonomy-and-await-mechanisms-design.md` (full spec)
 
-Key deltas vs. the v0.1 patterns documented below (which remain accurate for code
-as it exists today):
+Key deltas vs. the v0.1 patterns documented below (which describe the pre-0.2.0
+world and remain useful history, but the right column is now what's on disk):
 
-| v0.1 (below, as-built) | 0.2.0 (specced) |
+| v0.1 (below, legacy) | 0.2.0 (as-built) |
 |---|---|
 | `IntegrationEvent` = fat domain event, `scalarise()` flattens lossily | `IntegrationEvent` = **scalar-by-definition** (reversible ctor values only); strict `scalarise()` throws; total round-trip via `from_payload()` — typed events post-AS |
 | fat event crosses via entity→id flattening | fat moment implements `IAnnouncesIntegration::to_integration()` → hand-written scalar twin in `Integration\` sub-namespace (the 5 judgment lines: fact selection + naming) |
 | listeners = closures in `includes/hooks/integration/` | `IntegrationListener` classes in `Application\IntegrationListeners\` (auto-wired; `get_event_class()` + `get_command(): ?ICommand`) |
 | `AsyncWordpressActionHandler` for same-context deferred | **deprecated** — decomposes into `IntegrationListener` + Command (deferred work belongs under command_audit) |
 | `AwaitEvent` only (1-of-1) | `IAwaitMechanism` + `AwaitAll` (fan-in: expected ids, `key_by` static extractor on the process, mandatory wall-clock timeout); `#[Awaits]` class attribute replaces YAML `awaits:` |
 
-Even before 0.2.0 lands: **prefer scalar ctor params on new integration events** —
-they'll survive the migration unchanged.
+New integration events: **scalar ctor params, always** — the ctor is the wire
+schema (`integration_payload()` keys = ctor param names).
 
 ---