d3ro-voice/docs/map/11-gap-backlog.md
Yun Chan 4b40b25e53
Some checks failed
deploy-site / deploy (push) Failing after 1m4s
fix(site): stop the landing build from depending on hoisted Node types
The hero typed its timer ref with NodeJS.Timeout, which only resolves when
@types/node is visible from an ancestor node_modules. The deploy job installs
site dependencies alone, so tsc -b failed with TS2503 and the landing site has
not been redeployed since. Use ReturnType<typeof setTimeout> and record the
measured deploy blocker plus the runner's missing Python in the map.

💘 Generated with Crush

Assisted-by: Crush:deepseek-v4.1-flash
2026-09-19 08:47:33 +09:00

28 KiB

11 — Gap & Backlog Register

The maintained list of what is under-developed, deferred, or externally blocked. Status: living document. Every feature change updates this file (see 12-update-protocol.md). External items are marked EXT; they block "done" but must not block code, tests, or local fixtures.

Legend: [ ] open · [~] in progress · [!] blocked externally · [x] resolved (keep for one cycle, then prune).


0. How to read this

  • An item here is not a failure. It is a known state with an owner and a next step.
  • When you close an item, flip it to [x], add the date + evidence path, and also update 10-feature-catalog.md.
  • Grandfathered detail lives in docs/v3/MOBILE_APP_COMPLETION_SSOT.md; this file is the cross-surface roll-up. When the two disagree, the SSOT wins for mobile and must be reconciled here.

1. High impact — real capability gaps (no external blocker)

ID Area Gap Evidence Suggested next step
GAP-QA-01 Quality Extreme Red Team: headful end-to-end bug hunting across real desktop Electron, Web Next.js, and CI pipelines. red_team_log.md, tests/e2e/red_team_cycle*.spec.ts, apps/web/e2e/red_team_cycle4_web.spec.ts [x] 2026-09-15: 18 scenarios executed, 14 defects caught and 100% resolved (infinite chunking loop DEF-008, IPC signature mismatch DEF-004, markdown editor typing rollback DEF-006, Web RSC Link serialization DEF-012, secret scanner lookahead DEF-013, etc.). All 18 scenarios GREEN with zero regressions.
GAP-REL-01 Release Official release publication to Forgejo and active public download center deployment. scripts/ci/publish-forgejo-release.mjs, apps/web/src/app/download/page.tsx, site/src/sections/Download.tsx, apps/web/e2e/red_team_cycle4_web.spec.ts [~] 2026-09-15: v1.1.0 release assets (D3RO-Voice-Setup-1.1.0-x64.exe, .blockmap, latest.yml, update-policy.json) published to canonical Forgejo registry and release hub. 2026-09-16: the published 1.1.0 installer carries no Authenticode signature, so it does not satisfy the release policy; product version moved to 1.2.0 and publication must come from CI with the signing gate GREEN. Download centers in apps/web (/download) and site (#download) link the canonical Forgejo feed. 2026-09-19: 1.3.7 (overlay fix) is published to the canonical updater feed (latest.yml = 1.3.7, 90.6MiB); the CI signing gate that blocks tag-driven publication is still unresolved, so this went out through the local updater path (GAP-REL-06).
GAP-REL-08 Release 다운로드 센터가 존재하지 않는 설치 파일을 가리켰다. apps/web/src/lib/desktop-release.tssite/src/release.tsDESKTOP_VERSION1.2.0에 멈춰 있어 설치 URL이 D3RO-Voice-Setup-1.2.0-x64.exe였고, 그 경로는 피드에서 404다(실측: 1.2.0=404, 1.3.7=206). version:sync가 이 두 표면을 덮지 않아 계속 어긋났다. scripts/ci/sync-version.mjs, apps/web/src/lib/desktop-release.ts, site/src/release.ts [x] 2026-09-19: 두 다운로드 계약 파일을 sync-version.mjs 대상에 추가해 버전·릴리스일이 SSOT에서 자동 반영되도록 하고, 현재 값(1.3.7 / 2026-09-19)으로 정정했다. version:check·typecheck·site 빌드 GREEN.
GAP-REL-09 Release 랜딩 사이트가 재배포되지 않는다. deploy 워크플로가 main push마다 실패한다. 실측 원인(run#66 로그): site/src/sections/Hero.tsx가 타이머 ref를 NodeJS.Timeout으로 타이핑해 @types/node 네임스페이스가 필요했고, 배포 잡은 npm ci --prefix site만 하므로 조상 node_modules의 hoisted 타입이 없어 tsc -bTS2503: Cannot find namespace 'NodeJS'로 실패한다. 그래서 https://d3ro.chanpaca.net/release-identity.json이 404다(공개 버전 검증 불가). .forgejo/workflows/deploy-site.yml, site/src/sections/Hero.tsx [x] 2026-09-19: ref를 ReturnType<typeof setTimeout>으로 바꿔 hoisted 타입 의존을 제거했다(격리 --typeRoots로 CI 조건 재현 → 수정 전 TS2503, 수정 후 clean). 배포 잡이 Cloudflare Pages 단계까지 진행되는지 다음 run으로 확인한다.
GAP-REL-09b Release 위 빌드를 통과한 뒤에도 deploy가 실패하면 다음 원인은 Cloudflare Pages 시크릿이다. 워크플로는 CF_API_TOKEN(또는 CLOUDFLARE_API_TOKEN)이 없으면 exit 1로 중단한다. .forgejo/workflows/deploy-site.yml [ ] 2026-09-19: Forgejo에 CF_API_TOKEN + CF_ACCOUNT_ID를 등록하고 deploy-site.yml을 수동 실행해 사이트를 재배포한다.
GAP-REL-10 Release 태그 파이프라인은 서명 가드에 도달하기 전에 sidecar 단계에서 죽는다. Forgejo 자체 러너(yunchan-win)에 Python 3.11+가 없어 sidecar:setup("Python 3.11+ 를 찾을 수 없습니다") → sidecar:buildverify-sidecar-bundle.mjs가 연쇄 실패한다(실측: v1.3.7 release-windows run#65 로그). 즉 CI 게시는 인증서 이전에 러너 환경에서 먼저 막혀 있다. .forgejo/workflows/release.yml, .forgejo/workflows/portable.yml, apps/desktop/scripts/setup-sidecar.mjs [!] 2026-09-19: 러너에 Python 3.11+를 설치하거나 워크플로에 actions/setup-python 단계를 추가한다. 그때까지 게시 정본은 로컬 release:updater/release:portable 경로다(GAP-REL-06).
GAP-REL-02 Release Windows stable publication needs an external public-trust Authenticode PFX, its password, the exact signer subject, and a Forgejo token, none of which live in the repository. .forgejo/workflows/release.yml, .gitlab-ci.yml, scripts/ci/set-forgejo-secrets.mjs, scripts/ci/verify-windows-release-artifact.ps1 [!] 2026-09-18 measured: the Forgejo repo had zero Actions secrets; FORGEJO_TOKEN is registered now (2026-09-18) but WIN_CSC_* still have no values, so v1.2.0 (run 49) and v1.3.0 (run 51) both failed at the signing guard and no updater-feed release has been published since 1.1.0. Inject the four secrets (WIN_CSC_LINK, WIN_CSC_KEY_PASSWORD, WIN_CSC_EXPECTED_SIGNER_SUBJECT, FORGEJO_TOKEN) with npm run release:secrets (check: npm run release:secrets:check), then re-run release.yml for the v1.3.0 tag via workflow_dispatch (tags are immutable). 2026-09-19 정정: CI 서명 게이트는 여전히 막혀 있지만, updater feed에는 1.3.2~1.3.7이 로컬 release:updater 경로로 게시되어 있다(GAP-REL-06).
GAP-REL-06 Release 서명 인증서가 없어 stable(latest) 채널에 무서명 설치본을 게시했다. electron-updater는 app-update.ymlpublisherName이 없으면 서명 검증을 건너뛰므로 설치는 동작하지만, SmartScreen 평판은 버전마다 0부터 시작한다. scripts/ci/publish-updater-release.mjs, release/update-policy.json, .forgejo/workflows/release.yml [!] 2026-09-18: 1.3.2--ack-unsigned(명시적 승인 플래그)로 게시. 2026-09-19: 1.3.7도 같은 경로로 게시(npm run release:updater -- --ack-unsigned, 설치본 90.6MiB, latest.yml=1.3.7, 설치본 sha512가 피드 메타데이터와 일치). 인증서 확보 시 더 높은 버전으로 서명 게시하여 대체하고, 이 예외를 제거한다.
GAP-REL-07 Release 패키징된 better-sqlite3가 호스트 Node ABI여서 1.3.2 설치본이 시작 즉시 죽었다(NODE_MODULE_VERSION 131 vs 130). 원인: 로컬 npm install이 네이티브 모듈을 Node용으로 재빌드했고 패키징이 재빌드를 건너었다. scripts/ci/verify-native-abi.mjs, scripts/ci/fix-native-abi.mjs, .gitlab-ci.yml/.forgejo/.github 패키징 단계 [x] 2026-09-18: 패키징 후 Electron ABI를 검증하고, 검증된 트리에서만 설치본을 생성(--prepackaged)한다. 1.3.3은 설치본에서 추출한 바이너리로 재검증 GREEN.
GAP-ADS-01 Ads 9 of 10 desktop ad adapters still extend UnavailableAdAdapter (provider_not_integrated). apps/desktop/src/main/services/ads/* [~] 2026-09-13: DirectHouseSponsorAdapter is now a real configurable REST adapter (bid/impression/click/reward via endpointUrl; fail-closed when unconfigured; 22 unit tests GREEN). Remaining 9 need official SDKs/authenticated endpoints.
GAP-ADS-02 Ads Desktop mediation reward accounting is not wired to license quota (claimReward still returns no tokens). AdMediationEngine.ts, AppLayout.tsx Wire verified reportRewardCompletion to LicenseService quota after the direct sponsor endpoint exists.
GAP-ID-01 Identity Supabase, .NET JWT/SQLite, and the desktop offline license each had their own tier/role shape. @d3ro/core/entitlement, LicenseService, entitlement-context [~] 2026-09-13: canonical EntitlementSnapshot + resolveEntitlement added with tests; desktop tier normalization + isPro fixed. Full adoption tracked as GAP-ID-02.
GAP-ID-02 Identity Web and mobile still hand-roll tier/role normalization instead of consuming the canonical resolver; .NET identity is still a separate store. apps/web/src/lib, apps/mobile-rn/src/lib/entitlement-context.tsx Adopt resolveEntitlement in web/mobile; decide whether to retire the .NET user store or keep explicit mapping.
GAP-TEAM-01 Teams Team comments / activity feed was not implemented. server/supabase/migrations/20260913000033_team_activities.sql, web activity-feed.tsx, mobile team-service.ts [x] 2026-09-13: team_activities table + create_team_activity RPC + RLS + realtime publication; web + mobile UI.
GAP-MEM-01 Knowledge Web file upload was deferred and semantic search was mislabeled future. apps/web/src/components/knowledge/* [x] 2026-09-13: .txt/.md picker, newline-aware chunking, embed-chunks on submit, search-knowledge confirmed live.
GAP-MEM-02 Dictionary No dictionary import/export on any surface. catalog MEM-07 [x] 2026-09-13: desktop dictionary:import/export (JSON/CSV), web serialize/parse + download/upload, mobile via data-portability; 8 new unit tests.
GAP-MTG-01 Meetings Audio seek ↔ transcript timestamp sync missing. SSOT H-011 Store segment timestamps; wire player seek.
GAP-MTG-02 Meetings Speaker diarization only partially done on desktop; absent web/mobile. docs/phases/phase-15.5-speaker-diarization.md, SSOT H-014 Finish desktop pyannote path; expose speaker labels cross-surface.
GAP-INFRA-01 Build apps/mobile-rn is outside npm workspaces, so root typecheck/test/lint skip it. typecheck:mobile/lint:mobile/test:mobile/verify:all root scripts added 2026-09-13 (package.json), but membership/CI integration is still open. package.json Decide: add mobile to workspaces, or wire verify:all into CI.
GAP-MOB-01 Legacy apps/mobile Expo skeleton duplicated auth/data code and got version-sync edits. SSOT G-002 [x] 2026-09-13: deleted apps/mobile, removed from sync-version.mjs and package-lock.json; version:check GREEN.
GAP-INFRA-02 CI GitLab admin NAS deploy job is disabled; admin deploy is manual/GHCR. .gitlab-ci.yml (admin job comments) Re-enable with a protected environment, or document the manual runbook as canonical.
GAP-INFRA-03 Release Desktop auto-update was single-channel and pointed at GitLab while the public hub was Forgejo; no channel, mandatory-update, major-vs-delta, staging, or kill-switch policy. apps/desktop/src/main/update-feed.ts, electron-builder.yml, .forgejo/workflows [x] 2026-09-13: canonical Forgejo feed + legacy GitLab mirror, release/update-policy.json + runtime policy, publish-forgejo-release.mjs + Forgejo release workflow, 21 policy tests, verifier self-test 13 cases. See docs/deployment/update-system-assessment.md.
GAP-INFRA-04 Quality Desktop typecheck is a no-op: tsconfig.json is files: [] + references, so tsc --noEmit checks nothing. Real tsc -p tsconfig.node.json --noEmit surfaces many pre-existing errors. apps/desktop/package.json, apps/desktop/tsconfig.json Switch to tsc -b (or per-project -p) and clear the existing errors in a dedicated workstream; do not treat "typecheck GREEN" as evidence until then.
GAP-SHELL-01 Support Admin /support is a stub panel; desktop-only SupportModal. No shared ticket contract. apps/admin/src/app/(admin)/support/page.tsx Define a ticket/diagnostics contract or keep stub and mark N/A in catalog.
GAP-PUSH-01 Push send-push accepted webpush/apns but marked them push_provider_not_supported. _shared/webpush.ts, _shared/apns.ts, send-push/index.ts [x] 2026-09-13: VAPID Web Push (RFC 8291) + APNs .p8 transports implemented and routed; 10 new tests incl. an encryption round-trip. Client registration for those providers still pending (see GAP-PUSH-03).
GAP-PUSH-02 Push Nothing triggered send-push?mode=drain; enqueued notifications never left the outbox. server/cloudflare-worker/src/push-drain.ts, wrangler.toml [x] 2026-09-13: Cloudflare Cron Trigger (* * * * *) drains the outbox; tests in CI. Requires SUPABASE_URL + SUPABASE_SERVICE_ROLE_KEY secret on the worker.
GAP-PUSH-03 Push Mobile/web clients register only fcm; no service worker subscription or APNs device token. apps/mobile-rn/src/features/notifications/*, apps/web Add web service worker + pushManager.subscribe (store JSON subscription) and iOS APNs token registration.
GAP-PUSH-04 Push Android still depends on FCM (google-services.json). apps/mobile-rn/android, send-push Decide: minimal Firebase project, or UnifiedPush/ntfy. See docs/deployment/push-transport-without-firebase.md.
GAP-STT-01 Local STT Packaged desktop builds shipped no faster-whisper sidecar: electron-builder.yml had no extraResources entry for it and no pipeline job built it. Local transcription was impossible on any installed build; the app fell back to a system Python without the runtime. apps/desktop/electron-builder.yml, .gitlab-ci.yml, apps/desktop/scripts/build-sidecar.mjs [x] 2026-09-18: sidecar bundled via extraResources (sidecar-dist/sidecarresources/sidecar), sidecar:setup/sidecar:build scripts, and scripts/ci/verify-sidecar-bundle.mjs fails packaging when the engine or its Silero VAD data is missing. Verified on the real 242 MB bundle.
GAP-STT-02 Local STT Dev resolved the sidecar/SoX paths against the Vite output dir (out/main), so the sidecar ran a Python without faster-whisper and SoX recording died with spawn sox ENOENT. apps/desktop/src/main/utils/paths.ts, apps/desktop/tests/main/utils/paths.test.ts [x] 2026-09-18: app root is discovered by walking up for app markers; packaged mode fails loudly instead of silently falling back. Unit tests pin both branches.
GAP-STT-03 Local engines On hosts where localhost resolves only to IPv6, every local engine call (STT sidecar and Ollama) was refused. Audio capture and local LLM appeared dead. apps/desktop/src/main/utils/loopback.ts, LocalSTTService, LocalLLMService, RAGService, OnlineLLMService, STTManager [x] 2026-09-18: loopback normalization to 127.0.0.1 for all local engine URLs; defaults updated; 9 unit tests. Verified against the live sidecar and Ollama on a host with an IPv6-only localhost.
GAP-STT-04 Local STT Live partial transcript (CAP-03, voice:partialTranscript) was marked done but had no producer: the channel, popup UI, and preload existed, nothing ever emitted. apps/desktop/src/main/services/VoiceModeService.ts, LocalSTTService.transcribePartial, STTManager.transcribePartial [x] 2026-09-18: 1.5 s cadence over a 7.5 s trailing window, greedy decode, drained before the final transcription; never inserted.
GAP-STT-05 Local STT The bundled sidecar lacked faster-whisper's Silero VAD data, so vad_filter=true transcription would have failed at runtime even with the engine bundled. apps/desktop/scripts/build-sidecar.mjs, scripts/ci/verify-sidecar-bundle.mjs [x] 2026-09-18: --collect-all faster_whisper plus a packaging-time presence check for assets/silero_vad_v6.onnx.
GAP-REL-03 Release 서명이 없어 설치할 수 있는 경로가 없다(인증서 발급 전 공백). .forgejo/workflows/portable.yml, scripts/ci/build-portable.mjs, scripts/local/install-d3ro-voice.ps1, bucket/d3ro-voice.json [x] 2026-09-18: 서명 없는 portable 채널 구현 — 95MiB 7z 분할 볼륨(688MB → 162MiB) + Scoop 버킷 + 수동 설치 스크립트를 Forgejo에 게시. 실제 설치 스크립트 end-to-end 검증(볼륨 다운로드 → SHA-256 → 결합 → 해제 → 엔진 포함 확인). updater feed는 건드리지 않음.
GAP-REL-04 Release canonical feed는 Cloudflare 뒤에 있어 업로드 본문이 100MiB를 넘으면 HTTP 413으로 거부한다. scripts/ci/publish-updater-release.mjs, docs/deployment/unsigned-distribution.md [~] 2026-09-18: 설치본을 90.6MiB로 줄여 업데이트 피드 게시를 복구했다(GAP-STT-07). 휴대용/Scoop 채널은 여전히 95MiB 분할이 필요하다.
GAP-STT-07 Local STT 진(사이드카)을 앱 번들에 넣으면 설치본이 100MiB를 넘고 매 업데이트마다 162MiB를 다시 받는다. apps/desktop/src/main/services/RuntimeProvisioner.ts, apps/desktop/electron-builder.yml [x] 2026-09-18: 설치본에서 엔진/ffmpeg를 제거하고 처음 필요할 때 runtime-latest에서 내려받는다(부품별 + 결합본 SHA-256 검증). 설치본 189MB → 90.6MiB, 런타임 1회 116MiB(엔진 94.4 + ffmpeg 21.7). 실제 feed로 통합 검증 완료.
GAP-STT-06 Local STT Decode settings were untuned: previous-text conditioning let repeated hallucinations compound, and no VAD parameters meant slow, uneven segments. apps/desktop/sidecar/main.py [x] 2026-09-18: condition_on_previous_text=false, bounded low-temperature fallback, no_speech/compression_ratio/log_prob thresholds, 300 ms silence trimming. Same transcript, ~5x faster on the reference machine (7.7 s audio: 1609 ms → 303 ms).
GAP-STT-08 Local STT 1.3.5 설치본에서 엔진 설치가 "런타임 아카이브 해시 불일치 (sidecar)"로 항상 실패했다. 부품 검증은 메모리 스트림에서 센 값으로, 결합 검증은 디스크 파일에서 계산해 기준이 서로 달랐다. 디스크 쓰기가 잘려도 부품 검사를 통과하고 결합 단계에서만 터지므로 원인 파악도 불가능했다. 재시도가 없어 전송이 한 번 끊기면 곧바로 설치 실패였다. apps/desktop/src/main/services/RuntimeProvisioner.ts [x] 2026-09-18: 부품 크기·해시를 디스크 파일 기준으로 통일하고, 결합본은 크기를 먼저 검사한 뒤 해시를 본다(오류 메시지에 실제/기대값 포함). 부품 다운로드는 실패 시 해당 파일을 지우고 최대 3회 재시도한다. 서버 아티팩트는 무결함을 확인했고(부품 2개 해시 일치, 결합본 e203aa53… = 인덱스 기대값), 실제 feed로 설치를 재현해 18초 만에 성공. 1.3.6으로 게시 완료latest.yml이 1.3.6/90.6MiB를 서빙하고 설치본 sha512가 피드 메타데이터와 일치. 설치본 asar에 수정 코드가 포함되고 구버전 archiveHash 경로는 제거됨을 확인.

| GAP-INFRA-05 | Build | 패키징된 렌더러 팝업 스크립트가 번들에 없었다. 팝업 HTML이 classic <script src="./script.js">를 참조해 Vite가 처리하지 않았고, dev에서는 로드되지만 설치본에는 파일이 없었다. 그래서 녹음 오버레이가 0:00에서 멈추고 웨이브 바가 뜨지 않았으며 실시간 자막이 렌더되지 않았다. 로드 전 webContents.send가 조용히 버려지는 문제와 hide() 이후 재표시의 z-order/repaint 유실도 함께 있었다. | apps/desktop/src/renderer/popups/*/index.html, apps/desktop/src/main/windows/WindowManager.ts, scripts/ci/verify-desktop-renderer-bundles.mjs | [x] 2026-09-19: 팝업 5종을 type="module"로 전환해 Vite가 해시된 번들로 방출하도록 고쳤고, 빌드 HTML이 참조하는 모든 로컬 asset이 디스크에 있는지 검사하는 verify-desktop-renderer-bundles.mjs(+ self-test)를 .forgejo/.github 패키징 파이프라인에 연결했다. WindowManager는 렌더러 준비 전 IPC를 did-finish-load까지 보관하고, 팝업을 표시할 때마다 topmost 재선언 + 강제 repaint를 수행하며, 팝업 렌더러 콘솔/로드 실패를 main 로그로 승격한다. |


2. Mobile checklist roll-up (from MOBILE_APP_COMPLETION_SSOT.md §4)

These are the mobile SSOT rows still [ ] / [~]. Do not duplicate the full text here; open the SSOT for detail.

Group Open rows Theme
G (governance) G-002, G-006, G-007, G-008, G-009, G-010, G-011 Type/error/identity consolidation, legacy bundle separation, credential rotation
A (auth/account) A-001..A-013, A-018; A-014..A-017 [~] Session restore, signup, deep links, OAuth, profile, provider E2E
O (onboarding/a11y) O-001..O-012 Onboarding branches, permissions, tutorial, a11y, full ko/en
D (data/sync/offline) D-001..D-014 Schema/RLS, devices, cross-surface read/write, offline queue, conflict policy
R (record/transcribe) R-001..R-009, R-011..R-015, R-017..R-020; R-016 [x] Permissions, recorder, FGS, upload queue, job state, sharing
H (history/meetings) H-001..H-005, H-007..H-015; H-006 [x] Pagination, filters, detail, meeting timeline, docs, diarization, cross-app
F (feature parity) F-001..F-010, F-013, F-014; F-011/F-012 [x] Dashboard, dictionary, commands, actions, chat, conversation, knowledge
T (teams/admin/notify) T-001..T-005, T-009..T-012; T-006..T-008, T-013 [x] Team CRUD/roles, push delivery/deep links, notification settings
M (monetization) M-025, M-027; M-013 [~] Play Billing license test, Payple webhook signature
Q (quality/release) Q-012..Q-014, Q-019..Q-022, Q-026; Q-010/Q-011/Q-023/Q-027/Q-028 [~] Emulator scripts, OAuth E2E, billing E2E, visual/a11y gates, env unification, production AAB

3. External blockers (EXT) — require action outside the repo

ID Blocker What is needed Where tracked
EXT-FIREBASE-01 No production Firebase project Android FCM only; web/iOS can avoid Firebase (see push transport doc). Create project + Android app + Play fingerprint + FCM, or adopt UnifiedPush for Android. SSOT EXT-011, docs/deployment/push-transport-without-firebase.md
EXT-ADMOB-01 AdMob 검토 필요 / 광고 게재 제한 / store not linked / payment profile incomplete Complete console review + store link + payment profile. Playwright tooling ready: scripts/admob-login.mjs (one interactive login on a visible desktop) then scripts/admob-automate.mjs --apply creates/verifies units and reports store link. Neither persisted profile is signed in yet. SSOT §0, EXT-006
EXT-PLAY-01 Play Billing license tester + test payment method Configure license testers SSOT EXT-004
EXT-PLAY-02 Play product/offer/base-plan + tracks Create Pro/Pro+ products and tracks SSOT EXT-003
EXT-PLAY-03 Production AAB + CI secret injection + recovery backups Inject Firebase/AdMob/signing/evidence CI secrets SSOT EXT-008
EXT-PLAY-04 Closed test 0/12 members, 14 days; production access disabled Run closed test, request production SSOT EXT-010
EXT-OAUTH-01 GitHub/Apple provider secrets; real mobile Google consent→callback Configure providers, verify consent SSOT EXT-001
EXT-APPSIGN-01 Live App Links still old certificate Deploy updated assetlinks.json, re-verify live SSOT App Links row
EXT-PHYS-01 Physical Fold6 install/OAuth/purchase evidence User runs the artifact on device SSOT EXT-009
EXT-PAY-01 Payple live history + webhook signature verification Provider contract + signature scheme SSOT M-027
EXT-STRIPE-01 Production Stripe/Payple cross-verification Live payment E2E SSOT M-013
EXT-STT-01 Production provider keys (Groq/OpenAI/Deepgram/Gemini) Inject provider secrets apps/api-server/Program.cs env docs

4. Documentation & drift watch

ID Item Note
DOC-01 CLAUDE.md describes only Phase 1-15.5 desktop; does not mention web/mobile/admin/api-server. This map supersedes it for IA; consider trimming CLAUDE.md to rules + map pointer.
DOC-02 docs/design/* reflects an older desktop-only architecture and contains known naming drift (06-gap-analysis.md). Treat this map + code as current; design docs are historical.
DOC-03 memory/project_status.md is a chronological log, not current state. Use docs/map/* for current state.
DOC-04 docs/v2/00-v2-master-plan.md targets Expo for mobile. Actual mobile is RN CLI (apps/mobile-rn); the Expo app was removed 2026-09-13. v2 plan is historical.
DOC-05 This map itself must be regenerated after large refactors. See update protocol.

5. Quick "is X done?" lookup

  • Desktop local dictation / LLM / history / meetings / RAG / conversation: local dictation works in dev and in packaged builds as of 1.3.0 (engine bundled, paths fixed, IPv4 loopback). Ads: one real adapter, rest stubs.
  • Web console: yes, feature-complete for server-shared data; knowledge upload/search and team feed implemented.
  • Mobile: code complete for most flows and tested locally; blocked mainly by external store/console gates, plus a11y and some E2E depth.
  • Backend: fail-closed AI proxies, RLS, billing, ads SSV implemented; push transports (FCM + webpush + APNs) and cron drain implemented.
  • Admin: complete with deliberate "unavailable" states; support page is a stub.

6. Immediate TODO — push transports, drain, AdMob (2026-09-13)

Actionable checklist for the work started this session. Fields to fill are blank in .env (git-ignored) and mirrored in .env.example.

Push — server (code done, config pending)

  • Set Supabase Edge secrets for the transports you deploy: WEBPUSH_VAPID_PUBLIC_KEY, WEBPUSH_VAPID_PRIVATE_KEY, WEBPUSH_SUBJECT (web); APNS_KEY_ID, APNS_TEAM_ID, APNS_PRIVATE_KEY, APNS_TOPIC, APNS_ENVIRONMENT (iOS); FCM_SERVICE_ACCOUNT_JSON, FCM_PROJECT_ID (Android).
  • Deploy the updated send-push (supabase functions deploy send-push).
  • Generate a VAPID keypair (P-256) and store the private/public pair; subject must be mailto: or https:.
  • Create the APNs .p8 key in the Apple Developer portal and record Key ID + Team ID.

Push — Cloudflare cron drain

  • Set worker vars: SUPABASE_URL (wrangler secret/[vars]) and batch limit.
  • Set worker secret: wrangler secret put SUPABASE_SERVICE_ROLE_KEY.
  • wrangler deploy from server/cloudflare-worker and confirm the scheduled runs (Cloudflare dashboard → Cron Triggers).
  • Verify end-to-end: enqueue a test event (e.g. team invite) → drain → delivery row delivered.

Push — clients

  • Web: add a service worker + pushManager.subscribe, store the JSON subscription as the registration id, register provider: 'webpush'. (GAP-PUSH-03)
  • iOS: register the APNs device token with provider: 'apns'. (GAP-PUSH-03)
  • Android: decide FCM vs UnifiedPush/ntfy. (GAP-PUSH-04)

AdMob (Playwright tooling ready)

  • Run run-admob-login.bat (or node scripts/admob-login.mjs) once on a visible desktop to persist the Google session.
  • Run node scripts/admob-automate.mjs --apply to create/verify the banner + rewarded units and report the Play-store link.
  • Complete AdMob console gates externally: review, serving limits, store link, payment profile. (EXT-ADMOB-01)

Docs

  • Keep docs/deployment/push-transport-without-firebase.md and this file in sync when transports or clients change.