fix(aipah): require verified KTP before chatting ## Changes Require approved KTP/NIK verification in the shared Aipah access guard before users can chat, use voice, read conversation history, or access Aipah tools. Otherwise eligible unverified users can open the chat panel to read why verification prevents abuse and follow the "Verifikasi KTP" button to `/orientasi/identitas`. The message also explains that submitted verification must be approved. Closes #1934 ## Release impact Patch. Correct access enforcement and guidance in the existing Aipah flow. ## Migration notes All users, including selected users, staff, and admins, need both approved account registration and a verified linked personal identity before using Aipah. Existing unverified users must complete verification and wait for approval. The guard uses existing verification fields; no schema migration or new configuration is required. Admin configuration eligibility remains unchanged. ## Validation - UI policy scan against `d0356c1c38`: passed with zero violations. - ESLint on changed application files and the repaired launcher test: passed. - `pnpm check:react-doctor`: full project audit passed with zero errors or warnings and complete graph coverage. Reviewed the launcher test's unchanged module targets and updated only its stale loader checksum. - Graph-contract regression suite: all 10 tests passed. - JavaScript syntax and `git diff --check`: passed. - `node --import tsx --test --test-timeout=60000 components/aipah/launcher.test.mjs`: passed after defining the browser `self` global and waiting for access-state rendering and ActionForm's validated submit replay. - The exact eight-file `Check orientation connection recovery` command from the build workflow passed locally: 72 tests, zero failures. The previous CI run timed out in the native RSC footer subprocess after 30 seconds; that subprocess completed in 1.39 seconds in the local suite. No orientation code was changed. - Other regression coverage was added for the verification policy and access endpoint but has not been run locally. No full local build or dev server was run. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **New Features** * Aipah access now requires verified identity in addition to other eligibility requirements. * People who still need verification see guidance to complete KTP/NIK verification and can open the verification steps from the prompt. * **Bug Fixes** * Chat and its controls remain unavailable while verification is required. Access responses do not expose identity or registration details, and remain private and non-cacheable. <!-- end of auto-generated comment: release notes by coderabbit.ai -->