docs(gap): refresh product-technical baseline (74 repos, live census)

[seonghobae]

Canonical baseline owner

Single writer for docs/product-technical-gap-baseline.md. Protected source and exact-head evidence are authoritative; active PR behavior is never promoted into shipped truth here.

Current authority

• Protected product source last revalidated on 2026-09-05: develop@314ddeae7b775a4957594b599358c8255617eb2e, protected with 14 required status contexts.
• Exact docs(gap): refresh product-technical baseline (74 repos, live census) #1116 source head remains cff6495b0dbf06831981f148d4c3143f03ebc4e2.
• The source file itself remains stale and must be repaired on this branch before docs(gap): refresh product-technical baseline (74 repos, live census) #1116 can become code-current.

Active source-repair finding

docs/product-technical-gap-baseline.md still records predecessor #1160 b41fdb4f6ef5606f91cb39daa211dea62160ab32. Current #1160 is 332240dbba957602f217dc6e4e6a82a59d4d39b2, open/Draft/unshipped on #1159 c27f3781….

Since the baseline source was written, #1160 has mounted the canonical five-source selector, exact same-project media-switch transaction, project/generation reset, stale prior-resource play() retirement, selected-stem revocation/fallback, EN/KO selector copy and discovery loading feedback. The newest source/test slice adds distinct post-discovery buyer states: RED 298c76be… requires a verified Full-mix-only explanation plus a retryable discovery-error state; d2a2d5f5… adds ready | empty | error classification; 0b4d1383… binds feedback/retry to the exact current authority/generation; 447e8a48… pins result classification and native-error redaction; 442b87f3… repairs an impossible non-canonical playback authority in the locale test fixture; current TRACEABILITY/head is 332240db…. These are Draft source/test facts, not protected shipped truth.

Canonical Project Persistence is now #970 1d2e0867d473b46869b845c9d07369822e667a5a, an ordinary descendant of protected develop with behind_by=0, ahead_by=104. It retains shared-song structural/domain closure, Windows evidence-trigger repair and the root AGENTS.md Security Notes repair. The newest canonical repair also corrects a buyer-visible unit mismatch without changing the admission threshold: RED a7c86be8… requires save/load diagnostics for the actual 5 * 1024 * 1024 byte ceiling to say 5 MiB; fix 04e19ef6… changes native copy/tests from ambiguous 5MB to 5 MiB; 73d6a801… aligns project-format docs; exact traceability/head is 1d2e0867…. Its exact-head SBOM, CodeQL PR, Security Scan, ci and SAST Semgrep runs are queued while build-baseline is in progress at the latest sweep. Devin and CodeRabbit combined-status successes explicitly report skipped review and are not approval evidence. No qualifying unchanged-head last-push approval is established. Stable selected-source semantics, autosave/recovery/migration, descriptor-bound parent authority and exhaustive fault injection remain #970/#962 work.

JA/ZH/VI/ES/DE/FR, CJK/text expansion/font fallback, database-backed/versioned translation ledger and shipped accessibility evidence remain #965 work. Selected source must persist as stable semantic truth through #970/#962, never as a revocable playback authority.

Until the canonical file itself is repaired, do not describe #1116 source as code-current for Active Player or Project Persistence. Source repair must remain Draft evidence; then #968 must be reconciled onto the new exact baseline head by ordinary non-force descent while preserving its unique queue-control files. Predecessor checks/reviews do not transfer.

Stack continuity

Current Draft Active Player lineage:

#971 09bedd835475015379716292e63e6be376fceec9
→ #1159 c27f3781ddcbcc013dce07a26c0baf6080e4b2ac
→ #1160 332240dbba957602f217dc6e4e6a82a59d4d39b2

Canonical Project Persistence: #970 1d2e0867d473b46869b845c9d07369822e667a5a targeting protected develop.

#968 remains executable queue-control owner for #966 at docs/bandscope-product-readiness-baseline@25e1610fff2a927ab421621eb147188ab86a3470, still targeting unchanged #1116 source head cff6495...; it must remain Draft while the canonical baseline file is stale.

Verification / merge gate

#1116 stays Draft. Repair the canonical baseline source before readiness, re-fetch every live required workflow/check, resolve all valid actionable findings, obtain qualifying independent non-author unchanged-head approval, and non-force reconcile #968. No force-push, destructive rebase, self-approval, gate weakening, fabricated evidence or self-modifying source-fix workflow.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

BandScope의 제품·기술 기준선과 운영 증거 문서를 갱신했습니다. 최신 census, 제품 요구사항, 병합 증거, transport 상태, 영속성 계약, 보안 경계, 품질 및 릴리스 기준을 반영했습니다.

Changes

BandScope 기준선 문서

Layer / File(s)	Summary
제품 및 배송 계약 docs/product-technical-gap-baseline.md, docs/doctoring/product-gap-baseline-2026-09-01.md	74개 저장소의 최신 census와 BandScope backlog를 갱신했습니다. 제품 요구사항, 활성 작업 흐름, 병합 승계, historical evidence 및 source-selection authority를 기록했습니다.
도메인 및 기술 설계 docs/product-technical-gap-baseline.md	도메인 모델과 시스템 토폴로지를 보완했습니다. InitialSourceSelecting 및 ReplacementSourceSelecting 상태와 source 취소·실패·교체·삭제 전이를 추가했습니다. project_format_version, 원자적 교체, last-known-good recovery 및 식별자 호환성 계약을 명시했습니다.
보안 및 추적성 기준 docs/product-technical-gap-baseline.md	실제 오디오 acceptance, allowlisted Tauri IPC, 127.0.0.1 loopback, 입력 admission, subprocess 권한, 개인정보 redaction, UI/UX evidence, 품질·릴리스 게이트 및 traceability 기준을 갱신했습니다.

Estimated code review effort: 2 (Simple) | ~15 minutes

Merge Risk: 🟡 Moderate · up to 3f29e

The recovery state model currently leaves RecoveryFailed with no documented exit, so a failed restore can dead-end users and encode an incomplete product contract. Merge should wait until the contract defines acknowledgement to NoSource or retry behavior, with regression coverage.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 74개 저장소의 실시간 census를 포함한 product-technical baseline 문서 갱신이라는 주요 변경 사항을 명확하고 간결하게 설명합니다.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/gap-baseline-2026-08-31

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

@opencode-agent Become the sole writer for canonical BandScope branch docs/gap-baseline-2026-08-31 only while it still resolves to exact head 00019c9ffe18bd630b14c4cd7c4ff4146def340f and protected develop still resolves to 749511c3ad4000090048718f685c6bee6b3d2c25. Apply superpowers:using-superpowers, receiving-code-review, systematic-debugging, and verification-before-completion. Immediately before writing refetch the exact head/base, the current blob of docs/product-technical-gap-baseline.md, and unresolved threads PRRT_kwDORjvEXs6ds6Rf, PRRT_kwDORjvEXs6ds6Sq, PRRT_kwDORjvEXs6ds6Ty, PRRT_kwDORjvEXs6duRIm; abort/adapt if the ref/blob moved. This is a BandScope-docs-only lane: do not modify central .github, foreign repos, source code, or workflows; do not create another PR, force-push, or weaken gates.

Validate every finding against fresh live evidence before editing. Current verified contradictions on this exact head include:

1. The document says the refreshed inventory is 185 open PRs but its recorded verification still says 130. Fresh GitHub pagination returns open develop PRs across pages 1 and 2, with page 3 empty and no open main PRs. Record a reproducible current inventory command/result or, if the count has moved since this comment, use the fresh actual count consistently instead of preserving 185 as a slogan.
2. §6 says docs has no Mermaid/sequence/class diagrams immediately before embedding two Mermaid diagrams itself; the review also notes existing doctoring Mermaid flowcharts. Replace the repository-wide absence claim with the narrower truthful gap (for example, no canonical comprehensive UML/C4/domain/state-model set, if fresh search supports that) and preserve existing diagrams as evidence rather than pretending they do not exist.
3. P1 misroutes loop playback to Issue [Release] Ship signed, notarized, auto-updatable desktop builds with rollback evidence #960. Fresh issue authority: [Release] Ship signed, notarized, auto-updatable desktop builds with rollback evidence #960 is signed/notarized/updater/release/rollback; [Product] Add an active rehearsal player with precise looping and role controls #961 owns active rehearsal player/transport/precise loops/role controls. The adjacent crash-safe project row is also shifted: [Reliability] Add a versioned crash-safe project format, autosave, migration and recovery #962 owns crash-safe/versioned project format; [Operations] Build redacted diagnostics, crash evidence and an offline support bundle #963 owns diagnostics/support bundle. Correct the issue mapping wherever the document has this off-by-one drift.
4. Revalidate live status claims rather than publishing remembered state. In particular, the Noema 120-second failure is now confirmed by consumer bandscope#1115@223d53f6c63dc17f7ce219faa52e5eafbd7719ed, required run/job 33386655858/99470699909, which reached call_llm only after sidecar/gateway preflight and then raised TimeoutError at the protected-main timeout=120 path. The canonical central owner is now open .github#1509 (fix(noema): raise call_llm HTTP timeout from 120s to org policy), exact current head 3d2b6a8262e323c794885387d1e70297b39366b5; a BandScope-local workaround is not appropriate. Also refetch refactor(engine): promote temporal probe from cli hack to api integration #1117 before repeating any exact-head test/readiness claim.

Keep the baseline a truth source rather than a blocker narrative: distinguish protected shipped truth, current live evidence, accepted/open work, and planned gaps. If correcting the document surfaces a concrete BandScope executable gap already owned by an issue/PR, link its canonical owner; do not implement that code in this docs lane. Run any repository doc/markdown/contract checks that apply plus git diff --check, commit the smallest correction on this same branch, reply with successor exact SHA and evidence, and resolve only threads whose exact claims are actually corrected on the successor head.

[seonghobae]

Concurrent recount note for the new exact head 825512fed478a1a30c60756bd21fd2599bc98f8b: every one of the 72 accessible repositories was queried individually in this cycle. Because remote agents continued opening/closing PRs during the sequential sweep, those 72 per-repository observations sum to 2,689, while the organization-wide atomic search returned 2,690 at the baseline capture and then 2,691 later in the same run. This is expected live-queue skew, not a counting contract to 'fix' by freezing writers. The rank is stable by a wide margin: BandScope 188, TEPP 142, OriginWeave 140, newsdom-api 130, naruon 127. The document's 2,690 value remains a timestamped capture rather than a timeless invariant; merge decisions continue to refetch exact live state.

[seonghobae]

@claude Please refresh the two canonical baseline files on exact current head 825512fed478a1a30c60756bd21fd2599bc98f8b through normal non-force history; do not create a competing PR. Superseding fresh evidence at 2026-09-01 17:43 KST: 73 repositories are now accessible through the connected ContextualWisdomLab GitHub account because ContextualWisdomLab/ConceptWeave is newly present; the organization-wide atomic is:pr is:open capture is 2,683. Current high-backlog counts remain bandscope 189, TEPP 149, OriginWeave 140, newsdom-api 130, naruon 125. This run exhaustively partitioned all 73 accessible repository names into GitHub issue-search groups; every non-BandScope partition was below 189, so the highest-backlog selection is proven without assuming a stale repository list. Treat all queue numbers as timestamped evidence because concurrent writers remain active. Replace the prior 72-repository/volatile-count snapshot in docs/product-technical-gap-baseline.md and docs/doctoring/product-gap-baseline-2026-09-01.md without rewriting immutable PRD/TRD/DDD/UML/research contracts merely because the queue moved.

Also reconcile central-review status from fresh protected-central evidence. ContextualWisdomLab/.github#1546 remains protected truth at 5686de41660d51a7a7f22b8840dfa6ccfe5ff3f1, but the post-#1546 repository-wide scripts/ci coverage repair is still not protected truth. The current canonical root owner remains .github#1567, now exact head 400f2b5a63a5cdaf95a42ee4d49a4e492132738b. That branch now carries the scheduler coverage/SIGPIPE repair plus the history-preserved stacked #1491 Noema cleanup that removes the never-wired CodeGraph-context branch; because #1491 merged into #1567 rather than protected main, all predecessor #1567 evidence was invalidated and fresh exact-head evidence is required. Therefore central coverage remains an outstanding downstream prerequisite until #1567 itself reaches protected main. Do not revert to the obsolete claim that #1551's closure meant no coverage prerequisite remained, and do not promote #1567/#1491 candidate behavior to protected truth.

Keep the existing Rust core-computation ownership, bounded CPU/accelerator boundary, real-audio acceptance, 100% coverage/docstring/edge-case target, Storybook/Figma/screenshot UX contract, security/operability baseline, and APA 7 traceability intact. Update only truthful volatile evidence and directly contradicted status prose. Run the documentation/baseline contract tests and git diff --check, report the resulting exact head, and do not self-approve, force-push, weaken gates, or transfer predecessor evidence.

[devin-ai-integration]

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 2 new potential issues.

[devin-ai-integration]

Devin Review found 1 new potential issue.

[seonghobae]

Active Player Draft navigation refresh (not shipped baseline truth): protected source remains develop@314ddeae7b775a4957594b599358c8255617eb2e; #971 remains 9c1b20e6df778e303fada3e170c93418c496394b, #1159 remains 22a9f18d960cc7df93db890b2a5aa9594428c2b4, and #1160 is now 1f933ec1998d53eb8f1bc4b96ac933c56b017c24. The #1160 delta now also contains test-first source-switch continuity (d3df3767… → 4b78eabe…) and stale-safe renderer discovery-session lifetime (899f122e… → d37a7b88…), with code-current traceability in docs/traceability/playback-source-session.md. These contracts still are not mounted selector/shipped truth: RehearsalPlayer does not yet bind discovery/session state or execute the source-switch plan through the media load lifecycle; current locale infrastructure remains EN/KO only; exact-head protected workflow evidence is absent. Keep #1116 source head unchanged unless/until the canonical baseline file itself needs a semantic refresh; this comment records live Draft lineage only.