fix(forms): close completed drawers and restore portal styling

www/integrations/employee-portal/README.md

@@ -93,6 +93,24 @@ 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.
 
+### Scoped presentation correction, 2026-10-30
+
+The renderer now maps only `hs-button`, `content-button`, or
+`portal-resource-button` anchor tokens, or exact inline AIA orange background
+colors (`#ffbd59` / `#ff914d`), to the local `portal-resource-button` class.
+It does not copy the original style or arbitrary classes. These are narrow
+compatibility candidates, not a claim that encrypted real views have been
+inspected. HTTPS/mailto/tel links retain the existing safe URL checks; contact
+links receive a local dark-orange accent for readable contrast. Table scope
+and bounded numeric row/column spans are preserved. All other executable or
+unapproved attributes remain removed.
+
+Scoped typography, spacing, lists, table rules and keyboard focus apply to both
+unlocked streams. Synthetic staff/management fixtures exercise these mappings
+at 320/390/768/1440px. Owner must inspect the real views privately to confirm
+legacy button recognition and source fidelity; if a different class is used,
+provide sanitized class semantics rather than decrypted content or credentials.
+
 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.