feat(idaa): enforce mandatory Novi UUID linkage for member content

CRITICAL IDENTITY FIX:
Ensures all member-generated content (Meetings, Posts, Comments) is explicitly linked to the creator's Novi UUID via 'external_person_id' at the moment of creation.

Changes:
- Added 'external_person_id' to creation payloads in Recovery Meetings and BB Posts.
- Implemented 'identity scavenging' from localStorage in submit handlers to prevent race conditions where Svelte stores are briefly null.
- Refactored Post Comment edit component to robustly initialize and save creator identity.
- Added 'The Novi UUID Rule' to IDAA documentation to mandate this pattern for future development.
- Added Playwright test to verify creation linkage and fixed a version-mismatch bug in the test auth helper.

Note: Archives and Archive Content are excluded as they do not require member ownership.

documentation/CLIENT__IDAA_and_customized_mods.md

@@ -219,6 +219,25 @@ If you need a compact checklist for re-creating this flow in another integration
 
 `novi_trusted_li` and `novi_admin_li` are managed in Aether site config (not in Novi directly).
 
+## Identity Linkage: The Novi UUID Rule (Triple Linkage)
+
+**CRITICAL ARCHITECTURAL STANDARD:**
+All member-generated content in the IDAA module MUST be explicitly linked to the member's Novi UUID via the `external_person_id` field. This linkage is the primary mechanism for ownership, edit permissions, and auditing.
+
+### 1. Mandatory at Creation
+Linkage MUST happen at the moment of initial object creation (POST). Shell records created without an `external_person_id` are considered orphaned and may be inaccessible to the creator.
+
+### 2. Triple Linkage Scope
+The following objects require mandatory `external_person_id` linkage:
+- **Recovery Meetings** (`ae_Event`)
+- **Bulletin Board Posts** (`ae_Post`)
+- **Post Comments** (`ae_PostComment`)
+
+### 3. Implementation Patterns
+- **Buttons:** Creation buttons (e.g., "Create New Meeting") must include `external_person_id: $idaa_loc.novi_uuid` in their initial `create_ae_obj` payload.
+- **Edit Forms:** Edit components must provide robust fallbacks to `$idaa_loc.novi_uuid` for new or incomplete records, ensuring identity is captured even if the initial creation call was narrow.
+- **Identity Sync:** Along with the UUID, `full_name` and `email` should also be synced from `$idaa_loc` to provide human-readable context in notifications and admin views.
+
 ### Permission Upgrade Rule
 ```
 // RULE: Only UPGRADE to Novi-based permissions, NEVER downgrade.