fix(ops): send apikey with push drain, read the web push public key from release/, record 2026-11-17 backlog evidence
The scheduled push drain got HTTP 401 because modern Supabase service keys need the apikey header next to Bearer. NAS deploy scripts fall back to release/webpush-vapid-public.key (public key only). Map, mobile SSOT and deployment runbooks are synced with the verified operations run in docs/evidence/2026-11-17-backlog-operations.md.
This commit is contained in:
parent
8d8aaf5794
commit
6791e29f27
16 changed files with 254 additions and 96 deletions
|
|
@ -57,7 +57,7 @@ Status quick-reference: `[x]` done+verified · `[~]` partial/unverified · `[ ]`
|
|||
| MEM-01 | History list + search | [x] | [x] | [x] | [x] | Desktop SQLite (`HistoryService.list`/`getAll` with SQLite `mode`, `isFavorite`, `tag`, `search`, and `beforeCreatedAt` cursor pagination — 2026-10-30 `GAP-UX-02` `[x]`); web/mobile Supabase |
|
||||
| MEM-02 | History detail + edit | [x] | [x] | [x] | [x] | Desktop `HistoryService.update` + `history:update` IPC + inline edit in `HistoryEntryCard.tsx` (2026-10-30 `GAP-UX-02` `[x]`); Mobile `HistoryDetailScreen` |
|
||||
| MEM-03 | History favorites | [~] | [x] | [x] | [x] | Desktop had **no** favorites until 2026-09-27 (the old `[x]` was wrong): `history.is_favorite` column, `HistoryService.setFavorite` + `history:setFavorite` IPC, star toggle in `HistoryEntryCard`; the value is the same Supabase `history.is_favorite` mobile filters on, so it syncs both ways (`apps/desktop/tests/main/sync/SyncEngine.test.ts` (20) + `apps/desktop/tests/integration/cross-device-sync.supabase.test.ts` (5, local Supabase stack)). `[~]` until a GUI run toggles it and mobile shows it |
|
||||
| MEM-04 | History export / share | [x] | [~] | [x] | [x] | Desktop `MemoService.exportMarkdown` exports both tagged and untagged history with filter support and interactive save dialog (2026-10-30 `GAP-UX-02` `[x]`); web limited; mobile share sheet |
|
||||
| MEM-04 | History export / share | [x] | [~] | [x] | [x] | Desktop `MemoService.exportMarkdown` exports both tagged and untagged history with filter support and interactive save dialog (2026-10-30 `GAP-UX-02` `[x]`); web limited; mobile text/Markdown/source-audio share (`history-share.ts`, `D3ROFileShareModule`). 외부 대상 앱 수신 증거는 SSOT R-017/R-018의 별도 게이트 |
|
||||
| MEM-05 | History audio playback | [~] | [x] | [x] | [x] | Signed URLs on web/mobile. **Desktop had no playback at all** (the old `[x]` was wrong); since 2026-09-27 the history card plays this device's recording from the file (`history:getAudio` → bytes → Blob) and a phone/web recording through a 5-minute signed URL of its `audio_files` row. Desktop recordings upload to the same `audio` bucket contract (`{userId}/desktop/...`, `audio_files`, ≤50 MiB, Settings > Cloud toggle `cloudSyncAudio`) so the phone plays them too (`tests/main/sync/SyncExtensions.test.ts` (9) + integration case "지식 문서·설정·녹음" against the local Supabase stack). `[~]` until a GUI run plays both kinds |
|
||||
| MEM-06 | Dictionary (custom vocabulary) | [x] | [x] | [x] | [x] | All surfaces CRUD; Desktop Red Team RT-02 & RT-18 fuzzed/verified |
|
||||
| MEM-07 | Dictionary import/export | [x] | [x] | [x] | [-] | Desktop `dictionary:import/export` JSON+CSV (file dialogs, `DictionaryService`); web `serializeDictionary`/`importDictionaryFile` + header buttons; mobile CSV/TXT export + CSV/JSON/TXT import via `data-portability` |
|
||||
|
|
@ -115,12 +115,12 @@ Status quick-reference: `[x]` done+verified · `[~]` partial/unverified · `[ ]`
|
|||
| ACC-04 | Password reset / recovery deep link | [ ] | [ ] | [x] | [x] | Mobile ForgotPassword/UpdatePassword |
|
||||
| ACC-05 | Account profile / identity management | [~] | [~] | [x] | [x] | Desktop `LicenseTab`; mobile `AccountScreen` |
|
||||
| ACC-06 | Logout + local sensitive purge | [x] | [x] | [x] | [x] | Mobile central purge GREEN |
|
||||
| ACC-07 | Account deletion (server cascade + local purge) | [ ] | [ ] | [~] | [x] | `account-delete` Edge; mobile device E2E pending. **2026-11-04 backend retention proof:** isolated local Supabase verified `audio-purge` authorization and both direct and pg_cron/Vault dispatch; the queued DB row, deleted `audio_files` row, and private Storage object were removed together. Production deployment/schedule remains `GAP-OPS-04`. |
|
||||
| ACC-07 | Account deletion (server cascade + local purge) | [ ] | [ ] | [~] | [x] | `account-delete` Edge; mobile device E2E pending. `audio-purge` local proof (2026-11-04) and production scheduled proof (2026-11-17) are GREEN: Vault → pg_net → Edge returned HTTP 200 and the isolated real Storage object and queue row changed `1 → 0` (`GAP-OPS-04` resolved). |
|
||||
| ACC-08 | Cloud sync (per-user data) | [~] | [x] | [x] | [x] | Desktop `CloudSyncService` + `services/sync/`. The earlier `[x]` hid shipped defects fixed on 2026-09-27 (GAP-SYNC-01/02): first pull after sign-in fetched nothing, only the first meeting's memos/documents were pushed, deletions never propagated, team meetings were pulled into the personal DB and their `team_id` cleared on re-push, Realtime never connected. Anonymous local-mode data is now imported into the first account that signs in (`db/index.ts importLocalModeData`). Production deploy pending (GAP-SYNC-05) |
|
||||
| ACC-09 | Device registration + revocation | [~] | [~] | [x] | [x] | Mobile `DevicesScreen`. **Desktop registers itself since 2026-09-27** (`services/sync/device-registration.ts`, platform `windows`/`macos`, installation id in `AppConfig.deviceInstallationId`); revoking it from the phone signs the desktop out (Realtime on `devices` + 5-min heartbeat), signing out on desktop unregisters it. Web creates/checks in a stable `platform='web'` device only when the user opts into browser notifications, refuses to resurrect a revoked row, and revalidates an existing local Push subscription through the register RPC before showing it connected (`web-device.ts`, `web-push-session.ts`, `web-push.spec.ts`). An isolated throwaway local-browser run produced exactly one active web device and one device-bound token; no web device-management UI or production proof. Mobile parser accepts all five platforms and names them on the card. Local-stack desktop evidence exists; production pending GAP-SYNC-05 |
|
||||
| ACC-10 | Offline queue + retry | [~] | [ ] | [x] | [x] | Mobile durable queue |
|
||||
| ACC-11 | Data export/import (portability) | [~] | [ ] | [x] | [x] | Mobile canonical JSON E2E GREEN; desktop has export files. **2026-09-27 backend fix:** `export_account_portability` serialised whole rows, so columns added after the v1 archive (meeting creation metadata, meeting-document template/idempotency) made any account with meetings fail the exact-key check in both the server restore and the mobile parser; the export now projects onto v1 keys (migration `20260927000034`, integration test asserts memo/meeting keys) |
|
||||
| ACC-12 | Notification / push | [ ] | [~] | [~] | [x] | Backend transports for FCM + Web Push (VAPID) + APNs (.p8) + outbox cron drain implemented. **2026-11-04 (`GAP-PUSH-03` `[~]`):** Web production sidebar calls the explicit user-gesture permission → stable web device → `subscribeWebPush` → `register_push_registration` path. Opt-out records disabled intent before bounded parallel server/local cleanup; a stale local subscription is re-registered through the server RPC before it may appear connected, and logout never waits on cleanup (`web-push.spec.ts` 17 contract tests). The standalone image copies `public/sw.js`, and missing build-time `NEXT_PUBLIC_VAPID_PUBLIC_KEY` fails closed. Isolated local evidence reached active device + token + pending outbox + completed drain + `push_deliveries.status='delivered'`; this is provider acceptance, not browser receipt. The final production-standalone browser attempt timed out at login navigation before the dashboard, so production permission/subscription/render/receipt and deployed cron/provider configuration remain open (`EXT-FIREBASE-01` for Android). |
|
||||
| ACC-12 | Notification / push | [ ] | [~] | [~] | [x] | Backend transports for FCM + Web Push (VAPID) + APNs (.p8) + outbox cron drain implemented. **2026-11-17:** production VAPID/web image and scheduled drain are deployed; authenticated Chrome subscriptions succeeded and two outbox runs ended `delivered`. Browser `getNotifications()` was still 0, so visible receipt and APNs/FCM live delivery remain open. |
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue