B-KZ79-pumice-vacuous-e2e-and-red-check
Two pre-existing pumice frontend-gate problems, found while migrating its admin markdown renderer (PR 7 of the markdown-editing program) and deliberately not fixed there. (1) VACUOUS SUITE. In apps/pumice/src-nuxt, ‘bun run test:e2e’ exits 0 while asserting nothing: every test in tests/e2e/capture-appearance.e2e.ts is gated behind test.skip(!process.env.CAPTURE_SHOTS,…), so a normal run reports ‘20 skipped’ and passes. Running it with CAPTURE_SHOTS=1 overwrites the committed screenshot corpus in apps/pumice/docs/screenshots/, so the suite is either vacuous or destructive with no third option. Same failure class as the vacuous-pass bugs already fixed elsewhere in this repo. (2) CHECK RED ON MAIN. ‘moon run pumice:check’ fails on main independently of any markdown work, stopping at pumice:frontend-format-check. ‘bun run lint’ reports 2 errors, both import/first, at apps/pumice/src-nuxt/tests/use-dashboard.test.ts:18:1 and 19:1; that file is untouched by the PR, so the worktree copy is the HEAD copy. ‘bun run format:check’ fails on app/assets/css/phase-tokens.css and app/components/PProfilePickerRow.vue, both verified by extracting their HEAD revisions into temporary files and running prettier —check on those copies in isolation, each reporting [warn]. app/admin/generated/admin-registry.ts also fails prettier at HEAD, but it is codegen output. The evidence is recorded so whoever picks this up does not have to re-derive it.