chore: remove committed PR previews

.claude/commands/commit.md

@@ -223,12 +223,14 @@ handoff:
    resolution / frame rate when needed.
 3. Upload the compressed recording to the GitHub PR as a PR body attachment or a
    clearly labeled attached `Preview` comment.
-   Do not commit one-off PR preview recordings. Only commit preview media when
-   the media itself is product documentation or an example asset that should
-   ship with the repository. If PR attachment upload is blocked by local browser
-   or extension permissions, commit a compressed asset under
-   `.github/pr-previews/` and link the GitHub-hosted raw/blob URL from the
-   preview comment.
+   Never commit one-off PR preview recordings, including under
+   `.github/pr-previews/`. Create them in a temporary or ignored local path,
+   upload them as GitHub attachments, verify the attachment, then delete the
+   local files. Only commit media that is itself product documentation or an
+   example asset intended to ship with the repository.
+   If browser or extension permissions block the attachment, stop and ask the
+   maintainer to enable file uploads; do not force-add the recording as a Git
+   fallback.
 4. Link/embed the GitHub-hosted recording in the PR body or preview comment.
 
 If there is no visual or interactive surface, add a short PR note explaining why

.codex/skills/openiap-workflows/SKILL.md

@@ -102,12 +102,12 @@ appropriate labels before merging.
 - For PRs with new features, visible behavior changes, UI changes, docs pages,
   example flows, or developer workflows, record the actual changed surface,
   compress the video to under 10 MB, and upload it to the GitHub PR as a
-  `Preview` comment or PR body attachment. Do not commit one-off PR preview
-  recordings; only commit media when the asset itself is part of product docs or
-  examples. If PR attachment upload is blocked by local browser or extension
-  permissions, commit a compressed asset under `.github/pr-previews/` and link
-  the GitHub-hosted raw/blob URL. Use the Codex Chrome Extension for
-  web/docs/dashboard previews when applicable.
+  `Preview` comment or PR body attachment. Never commit one-off preview media,
+  including under `.github/pr-previews/`; keep it in a temporary or ignored
+  local path and delete it after verifying the GitHub attachment. If browser or
+  extension permissions block the attachment, stop and ask the maintainer to
+  enable uploads instead of force-adding a Git fallback. Use the Codex Chrome
+  Extension for web/docs/dashboard previews when applicable.
 - Keep commits in Angular Conventional Commits format:
   `<type>(<scope>): <subject>`.
 - When creating branches for commit/push/PR workflows, follow

knowledge/_claude-context/context.md

@@ -1,7 +1,7 @@
 # OpenIAP Project Context
 
 > **Auto-generated for Claude Code**
-> Last updated: 2026-08-12T23:08:31.332Z
+> Last updated: 2026-08-13T01:31:14.251Z
 >
 > Usage: `claude --context knowledge/_claude-context/context.md`
 
@@ -1988,11 +1988,14 @@ Requirements:
   too large.
 - Upload the compressed recording to the GitHub PR as a PR body attachment or a
   clearly labeled attached `Preview` comment.
-- Do not commit one-off PR preview recordings. Only commit preview media when
-  the media itself is a product documentation or example asset that should ship
-  with the repository. If PR attachment upload is blocked by local browser or
-  extension permissions, commit a compressed asset under `.github/pr-previews/`
-  and link the GitHub-hosted raw/blob URL from the preview comment.
+- Never commit one-off PR preview recordings, including under
+  `.github/pr-previews/`. Create them in a temporary or ignored local path,
+  upload them as GitHub attachments, verify the attachment, then delete the
+  local files. Only commit media that is itself a product documentation or
+  example asset intended to ship with the repository.
+- If browser or extension permissions block an attachment, stop and ask the
+  maintainer to enable file uploads. Do not force-add the recording as a Git
+  fallback.
 - Link or embed the uploaded preview in the PR body or a clearly labeled
   `Preview` PR comment.
 - If the change has no visual or interactive surface, include a short note in

knowledge/internal/06-git-deployment.md

@@ -51,11 +51,14 @@ Requirements:
   too large.
 - Upload the compressed recording to the GitHub PR as a PR body attachment or a
   clearly labeled attached `Preview` comment.
-- Do not commit one-off PR preview recordings. Only commit preview media when
-  the media itself is a product documentation or example asset that should ship
-  with the repository. If PR attachment upload is blocked by local browser or
-  extension permissions, commit a compressed asset under `.github/pr-previews/`
-  and link the GitHub-hosted raw/blob URL from the preview comment.
+- Never commit one-off PR preview recordings, including under
+  `.github/pr-previews/`. Create them in a temporary or ignored local path,
+  upload them as GitHub attachments, verify the attachment, then delete the
+  local files. Only commit media that is itself a product documentation or
+  example asset intended to ship with the repository.
+- If browser or extension permissions block an attachment, stop and ask the
+  maintainer to enable file uploads. Do not force-add the recording as a Git
+  fallback.
 - Link or embed the uploaded preview in the PR body or a clearly labeled
   `Preview` PR comment.
 - If the change has no visual or interactive surface, include a short note in