feat(portal): add service drawers and employee portal preview

www/integrations/employee-portal/README.md

@@ -0,0 +1,101 @@
+# Employee portal compatibility and private migration
+
+Recorded 2026-10-30. Browser-side shared-code decryption is approved only for
+local compatibility development. It is not authentication, individual revocation,
+a secure session or a HIPAA compliance determination. Resources need separate
+server authorization before cutover.
+
+## Source and private collection
+
+Read-only legacy footer source:
+`/home/alice/projects/wrk/aia/local-archives/aia-employee-portal-hubspot-footer-source.txt`.
+The original stays outside Git as rollback evidence. No access code was available
+to the agent. The exact resource count and real content compatibility remain
+unverified. Do not infer the earlier approximate 43 links as a measured count.
+
+From `www`, in the owner's private interactive terminal:
+
+```sh
+node tools/employee-portal-migrate.mjs collect \
+  /home/alice/projects/wrk/aia/local-archives/aia-employee-portal-hubspot-footer-source.txt
+```
+
+Enter each legitimate view code at its hidden prompt. Never place codes in
+arguments, environment variables, shell history or reports. The utility checks
+both streams, keeps plaintext in memory, and collects only referenced `/hubfs/`
+resources from the verified source origin. Other origins require explicit
+review/code allowlisting; redirects are bounded and never inherit credentials.
+No Jotform, Google or other vendor forms are fetched.
+
+Private output is `private/employee-portal/`: directories 0700, manifests and
+binary resources 0600. This exact subtree is gitignored and outside Astro's
+public directory. Filenames are SHA-256 hashes of source URLs, independently
+verified by content hashes. The manifest retains original references, labels,
+view membership, MIME, bytes, status and delivery/classification decisions.
+All new resources default to UNRESOLVED. Publicly reachable does not mean public
+approved. Resuming verifies an existing file's content hash; mismatches are not
+overwritten. HTML error documents, executable responses, invalid known signatures,
+redirects outside approved destinations and resources over 50 MiB are rejected.
+The first pass allows only the verified site origin. If a legitimate `/hubfs/`
+response redirects to a HubSpot CDN, inspect that exact HTTPS origin first, then
+add its origin to the private manifest's `approvedOrigins` list and rerun. Never
+approve a redirect based only on a failed download or a broadly shared vendor
+domain. Failures remain private review items. The utility prints counts only.
+
+Before every artifact transfer, verify that only `dist` is copied and that it
+contains no private manifest, document or real ciphertext unless that ciphertext
+has separately been authorized for the local preview. Never archive the whole
+working directory as a deployable artifact.
+
+## Approved rewriting
+
+The owner classifies records as PUBLIC-APPROVED, STAFF-INTERNAL,
+MANAGEMENT-INTERNAL or UNRESOLVED in the private manifest. Set `deliveryPath`,
+`rewriteApproved`, `destinationImplemented`, `destinationVerified`, and (for
+internal documents) `destinationAccessControlled` only with actual evidence.
+The utility does not create those destinations or infer their approval.
+
+```sh
+node tools/employee-portal-migrate.mjs rewrite \
+  /home/alice/projects/wrk/aia/local-archives/aia-employee-portal-hubspot-footer-source.txt
+```
+
+It reauthenticates both views, changes approved quoted href/src attributes only,
+preserves unrelated HTML/labels, and re-encrypts with fresh salts and IVs. It
+verifies round-trip decryption and distinct codes before writing new ciphertext
+with exclusive filenames. The original source is untouched. CSS/srcset mappings
+require separate review and are rejected rather than silently rewritten.
+Unresolved links retain their original destination as a recorded dependency,
+not a claim of verified destination health. A changed manifest alone never
+changes links in the encrypted stream.
+
+## Local preview and content safety
+
+Use a private ciphertext file generated by `collect` or `rewrite`:
+
+```sh
+AIA_PORTAL_LOCAL_PREVIEW_APPROVED=true \
+AIA_PORTAL_CIPHERTEXT_FILE=/absolute/private/ciphertext-TIMESTAMP.json \
+PUBLIC_AIA_FORMS_ENVIRONMENT=isolated-test \
+PUBLIC_AIA_FORMS_MODE=off PUBLIC_ALLOW_INDEXING=false \
+npm run dev -- --host 127.0.0.1
+```
+
+The page defaults to locked/unavailable without approved valid input. Indexing
+builds cannot include it. The codes never go to a server, storage or URL. No
+native form submits; Enter and Unlock use local WebCrypto. Only the matching
+stream is displayed; refresh or leaving the page locks it again.
+
+The passive DOM renderer preserves headings, lists, text, tables and safe
+HTTPS/mailto/tel links, with no referrer on links. It rejects scripts, inline
+handlers, styles, media, embedded forms and unknown tags. Real portal markup
+has not been decrypted or reviewed; any removed behavior must be reviewed with
+the owner before claiming fidelity. It must not silently become arbitrary
+script execution. No real encrypted stream or plaintext is in Git.
+
+Before owner acceptance: validate two real view codes privately, inspect every
+resource/category, responsive directories, focus, link semantics and sanitization
+impact. Check wrong-code feedback, keyboard unlock, no-JS explanation and refresh.
+Production must use a separately reviewed runtime ciphertext delivery mechanism;
+this batch intentionally provides only a gated local build input. Browser-delivered
+ciphertext is publicly downloadable by anyone able to reach that preview.