Public report of yazinsai/OpenOats, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 23:01 UTC · Survey ID cd_d179f754971f4ac08db5fda176e65f31
yazinsai/OpenOats
Measured 14 November 2026, 23:00 UTC, at code version b4353cd
CAI scoreAt riskNo change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 42,839 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 51
Findings by how serious they are
14 critical368 serious40 minor
15 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 23:00 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
60of 60 dimensions measured by tools.
403of 422 findings point to an exact file and line, so you can open each one in the code. The other 19 concern the repository as a whole, such as missing documentation.
60dimensions across 8 lenses, read from 42,839 lines of product code in 4 projects.
yazinsai/OpenOats is rated At risk because critical security findings are open. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 51, is the weakest lens and counts most in the score. The best first step is adding automated security scanning, worth about 5 points. Adopting a type checker comes next, worth about 2 points. Raising Production Readiness to 70 would lift the score to about 62.
Seven known security holes in the packages the code depends on can be used by attackers. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and correcting the flagged pipeline settings would deal with the weakness in the build pipeline's configuration.
The product code is 42,839 lines, about €58,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
God Classes · MethodTooLong: MicCapture.bufferStream OpenOats/Sources/OpenOats/Audio/MicCapture.swift
Code Duplication · Edited copy of a member (83 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift
Code Duplication · Edited copy of a member (69 corresponding lines) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift
Code Duplication · Edited copy of a member (51 corresponding lines) OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift
Code Duplication · Edited copy of a member (29 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift
Code Duplication · Edited copy of a member (43 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift
Code Duplication · Edited copy of a member (41 corresponding lines) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift
Code Duplication · Edited copy of a member (36 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copy of a member (28 corresponding lines) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift
Code Duplication · Edited copy of a member (50 corresponding lines) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift
Code Duplication · Edited copy of a member (30 corresponding lines) OpenOats/Sources/OpenOats/Views/OverlayPanel.swift
Code Duplication · Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift
Code Duplication · Edited copies of one member (3 members, 35+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift
Code Duplication · Edited copy of a member (27 corresponding lines) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift
Code Duplication · Edited copy of a member (23 corresponding lines) OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift
Code Duplication · Edited copy of a member (23 corresponding lines) OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift
Code Duplication · Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift
Code Duplication · Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift
Code Duplication · Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift
Code Duplication · Edited copy of a member (19 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift
Code Duplication · Edited copy of a member (24 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift
Code Duplication · Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift
Code Duplication · Edited copy of a member (27 corresponding lines) OpenOats/Sources/OpenOats/Domain/MeetingTypes.swift
Code Duplication · Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift
Code Duplication · Edited copy of a member (29 corresponding lines) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift
Code Duplication · Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift
Code Duplication · Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/App/NotesController.swift
Code Duplication · Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift
Code Duplication · Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Intelligence/MarkdownMeetingWriter.swift
Code Duplication · Edited copy of a member (14 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift
Code Duplication · Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (14 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift
Code Duplication · Edited copy of a member (19 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift
Code Duplication · Edited copy of a member (16 corresponding lines) OpenOats/Sources/OpenOats/Meeting/NotificationService.swift
Code Duplication · Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift
Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift
Code Duplication · Edited copy of a member (15 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift
Code Duplication · Edited copy of a member (12 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift
Code Duplication · Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift
Code Duplication · Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift
Code Duplication · Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift
Code Duplication · Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift
Code Duplication · Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) OpenOats/Sources/OpenOats/Audio/MicCapture.swift
Code Duplication · Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Meeting/CameraActivityMonitor.swift
Code Duplication · Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift
Code Duplication · Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift
Code Duplication · Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/App/NotesController.swift
Code Duplication · Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift
Code Duplication · Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift
Code Duplication · Edited copy of a member (8 corresponding lines) OpenOats/Sources/OpenOats/Domain/Utterance.swift
Code Duplication · Edited copy of a member (12 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift
Code Duplication · Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift
Code Duplication · Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift
Code Duplication · Edited copy of a member (5 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift
Code Duplication · Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift
Code Duplication · Edited copy of a member (3 corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift
Code Duplication · Edited copy of a member (5 corresponding lines) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift
Code Duplication · Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift
Code Duplication · Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift
Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift
Code Duplication · Edited copies of one member (4 members, 3+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 43 findings
These 43 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one.
Forms & labels · <input> without a programmatic label tools/sidecast-debug/index.html
Page structure · Page without a main landmark tools/sidecast-debug/index.html
Visual & motion safety · Animation without a prefers-reduced-motion guard tools/sidecast-debug/index.html
Visual & motion safety · Focus outline removed in CSS without a :focus replacement tools/sidecast-debug/index.html
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €58,000 · Estimate
Cost to rebuild
€19,000 to €97,000, for 323 to 1,025 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 42,839 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`.
Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €58,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 51 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 6% on every change. The history of the code shows how much it changes: about 9,368 lines over the last 90 days, which is about 37,992 lines a year. At that pace, the extra work comes to an estimated 2.3 to 14 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
13 modules, with 3 dependencies between them. Every module uses only modules listed above it, so there are no loops.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
tools.sidecast-debug.src uses tools.sidecast-debug.src.sidecast, so a change to tools.sidecast-debug.src.sidecast can break tools.sidecast-debug.src, while a change to tools.sidecast-debug.src can't break tools.sidecast-debug.src.sidecast.
Position
Below the diagonal: tools.sidecast-debug.src uses a module listed above it, which is the healthy direction.
tools.sidecast-debug.src uses tools.sidecast-debug.src.transcript, so a change to tools.sidecast-debug.src.transcript can break tools.sidecast-debug.src, while a change to tools.sidecast-debug.src can't break tools.sidecast-debug.src.transcript.
Position
Below the diagonal: tools.sidecast-debug.src uses a module listed above it, which is the healthy direction.
tools.sidecast-debug.src uses tools.sidecast-debug.src.types, so a change to tools.sidecast-debug.src.types can break tools.sidecast-debug.src, while a change to tools.sidecast-debug.src can't break tools.sidecast-debug.src.types.
Position
Below the diagonal: tools.sidecast-debug.src uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
16
High / Critical
A05:2025 — Injection
7
High / Critical
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Bring the 39 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LiveSessionController.finalizeCurrentSession (cyclomatic 46), SidecastPreset.apply (cyclomatic 38), StreamingTranscriber.run (cyclomatic 34).
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 14
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 368
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 40
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 60 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 403 of 422 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in OpenOats produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (OpenOats), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `OpenOats/Sources/Benchmark/main.swift`, `OpenOats/Sources/OpenOats/App/AppCoordinator.swift`, `OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift`, `OpenOats/Sources/OpenOats/App/NotesController.swift`, `OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift`, … (+14 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in OpenOats/Sources/OpenOats/App/AppContainer.swift, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 34 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 39 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LiveSessionController.finalizeCurrentSession (cyclomatic 46), SidecastPreset.apply (cyclomatic 38), StreamingTranscriber.run (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 39 together lifts Cyclomatic Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 61 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with StreamingTranscriber.run (cognitive 91), LiveSessionController.synchronizeDerivedState (cognitive 63), LiveSessionController.finalizeCurrentSession (cognitive 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.7 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 20 MethodTooLong finding(s) in God Classes — start with SettingsView.swift (4), MeetingDetailPane.swift (3), LiveSessionController.swift (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 14 FileTooLong finding(s) in God Classes — start with MeetingDetailPane.swift, SessionRepository.swift, SettingsStore.swift. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 12 ClassTooLong finding(s) in God Classes — start with MeetingDetailPane.swift, SettingsStore.swift, LiveSessionController.swift. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
85 duplicated block group(s) detected. 9.8 % of the production lines (4,208 of 42,839) are in a reported copy. A further 77 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (13 corresponding lines) · ×5OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:81
Edited copy of a member (7 corresponding lines) · ×5OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:599
Edited copy of a member (9 corresponding lines) · ×4OpenOats/Sources/OpenOats/Views/ContentView.swift:557
Edited copy of a member (6 corresponding lines) · ×4OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:491
+ 84 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with SettingsStorage.swift, MarkdownMeetingWriter.swift, MeetingDetailPane.swift. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with SessionRepository.swift (2), MeetingDetailPane.swift, OpenOatsLocalModelStore.swift. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AudioRecorder.swift, HomeTimelineWorkspaceView.swift, MeetingDetailPane.swift. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.0 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
4 production modules (npm+SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 1 module(s) off the main sequence, with abstractness counted on 2 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: OpenOatsKit
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppCoordinator.swift, SettingsStore.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 7 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
No assertions: testStreamUsesUnboundedBuffering · ×3OpenOats/Tests/OpenOatsTests/MeetingDetectionControllerTests.swift:176
What to do
Resolve the 4 Skipped test finding(s) in Test Quality — start with TranscriptionBackendTests.swift (3), StreamingWhisperReproTests.swift. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 No assertions finding(s) in Test Quality — start with SettingsStoreTests.swift (2), MeetingDetectionControllerTests.swift. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
3 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
Outdated: fluidaudio · ×3
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 11 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 10 of them read from the licence file the repository carries at the revision REDACTED pins, and 1 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed REDACTED pins, direct and transitive, and every declared dependency none pins. 1 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with SettingsStore.swift, SettingsView.swift, ContentView.swift. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.0 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is OpenOats/Sources/OpenOats/Views/SelectableTextFlow.swift. Counted over 106 of the 133 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 42839 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 8 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 3 build units (SwiftPM, checkout, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift`, `OpenOats/Sources/OpenOats/Settings/SettingsStore.swift` (line 63, line 74, line 92, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
9 of 106 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift. Counted over 106 of the 133 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with SettingsStore.swift, SettingsView.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — promo/openoats-hype.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`#start .pb` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — promo/openoats-hype.html:154
`#shareF div` sets color: #fff on background-color: #ff3b30 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — promo/openoats-hype.html:75
`.model` sets color: #77777f on background-color: #26262b — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — promo/openoats-hype.html:108
`#aq` sets color: #fff on background-color: #5b9bf5 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — promo/openoats-hype.html:136
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour — a data-only reference entity whose logic lives in a foreign service is anemic. Rich models enforce their own invariants.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a reference entity protects its own invariants — a class whose identity is a computed content hash but whose hashed fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM on its own declaration (active-record), or reaching a web-framework transport type in its own method, couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
`tools/sidecast-debug/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — tools/sidecast-debug/package.json:10
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`bufferStream` is async and calls usleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:194
`unifiedLogReport` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — OpenOats/Sources/OpenOats/Utils/DiagnosticsSupport.swift:217
What to do
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
tools/sidecast-debug/src/ui.ts:705 · tools/sidecast-debug/src/ui.ts:721 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools/sidecast-debug/src/ui.ts:705
tools/sidecast-debug/src/ui.ts:254 · tools/sidecast-debug/src/ui.ts:263 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tools/sidecast-debug/src/ui.ts:254
tools/sidecast-debug/src/ui.ts:282 · tools/sidecast-debug/src/ui.ts:355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — tools/sidecast-debug/src/ui.ts:282
tools/sidecast-debug/src/ui.ts:486 · tools/sidecast-debug/src/ui.ts:502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — tools/sidecast-debug/src/ui.ts:486
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
tools/sidecast-debug/server/transcript-proxy.ts:3 imports youtube-transcript/dist/youtube-transcript.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — tools/sidecast-debug/server/transcript-proxy.ts:3
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
callLLM has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/sidecast-debug/src/sidecast.ts:103
filterAndRank has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/sidecast-debug/src/sidecast.ts:230
renderDebugLog has cyclomatic complexity 13 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tools/sidecast-debug/src/ui.ts:627
Do you agree with this assessment?
R3 · Large Files5.0 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
tools/sidecast-debug/src/ui.ts has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tools/sidecast-debug/src/ui.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Nothing imports this binding — it is safe to review for removal. — tools/sidecast-debug/src/transcript.ts:50
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — tools/sidecast-debug/src/ui.ts:70
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×9) — OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:570, OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:201, OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:50, …
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R4 Test Coverage — no production JavaScript/TypeScript files to cover (0 test file(s) present) — nothing to measure
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
MethodTooLong: LiveSessionController.finalizeCurrentSession OpenOats/Sources/OpenOats/App/LiveSessionController.swift:746— MethodTooLong — finalizeCurrentSession runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TranscriptionSettingsTab.body OpenOats/Sources/OpenOats/Views/SettingsView.swift:459— MethodTooLong — body runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GeneralSettingsTab.body OpenOats/Sources/OpenOats/Views/SettingsView.swift:96— MethodTooLong — body runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SystemAudioCapture.bufferStream OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:194— MethodTooLong — bufferStream runs 198 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsStore.init OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1464— MethodTooLong — init runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TranscriptionEngine.start OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:455— MethodTooLong — start runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MeetingDetailPane.notesEmptyState OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3135— MethodTooLong — notesEmptyState runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ContentView.rootContent OpenOats/Sources/OpenOats/Views/ContentView.swift:31— MethodTooLong — rootContent runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IntelligenceSettingsTab.body OpenOats/Sources/OpenOats/Views/SettingsView.swift:873— MethodTooLong — body runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TemplatesSettingsTab.body OpenOats/Sources/OpenOats/Views/SettingsView.swift:1106— MethodTooLong — body runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BatchTextCleaner.cleanup OpenOats/Sources/OpenOats/Intelligence/BatchTextCleaner.swift:53— MethodTooLong — cleanup runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ControlBar.body OpenOats/Sources/OpenOats/Views/ControlBar.swift:43— MethodTooLong — body runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: StreamingTranscriber.run OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift:103— MethodTooLong — run runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MeetingDetailPane.notesNoTranscriptState OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2754— MethodTooLong — notesNoTranscriptState runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LiveSessionController.synchronizeDerivedState OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1720— MethodTooLong — synchronizeDerivedState runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LiveTranscriptCleaner.performCleanup OpenOats/Sources/OpenOats/Intelligence/LiveTranscriptCleaner.swift:92— MethodTooLong — performCleanup runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BatchAudioTranscriber.runTranscription OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:522— MethodTooLong — runTranscription runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SidecastSettingsTab.body OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:12— MethodTooLong — body runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MeetingDetailPane.meetingFamilyOverviewSection OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:734— MethodTooLong — meetingFamilyOverviewSection runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MicCapture.bufferStream OpenOats/Sources/OpenOats/Audio/MicCapture.swift:67— MethodTooLong — bufferStream runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: Views/MeetingDetailPane.swift OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift— FileTooLong — 3025 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: MeetingDetailPane (40-4101). The bar is 500 significant lines; this is 2525 over it, 6.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Storage/SessionRepository.swift OpenOats/Sources/OpenOats/Storage/SessionRepository.swift— FileTooLong — 1562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1062 over it, 3.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Settings/SettingsStore.swift OpenOats/Sources/OpenOats/Settings/SettingsStore.swift— FileTooLong — 1406 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: SettingsStore (9-1982). The bar is 500 significant lines; this is 906 over it, 2.81× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: App/LiveSessionController.swift OpenOats/Sources/OpenOats/App/LiveSessionController.swift— FileTooLong — 1290 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: LiveSessionController (60-1911). The bar is 500 significant lines; this is 790 over it, 2.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: App/NotesController.swift OpenOats/Sources/OpenOats/App/NotesController.swift— FileTooLong — 1211 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: NotesController (158-1729). The bar is 500 significant lines; this is 711 over it, 2.42× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Views/SettingsView.swift OpenOats/Sources/OpenOats/Views/SettingsView.swift— FileTooLong — 1178 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 678 over it, 2.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Transcription/TranscriptionEngine.swift OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift— FileTooLong — 1083 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: TranscriptionEngine (68-1600). The bar is 500 significant lines; this is 583 over it, 2.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Views/IdleHomeDashboardView.swift OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift— FileTooLong — 787 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 287 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Transcription/BatchAudioTranscriber.swift OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift— FileTooLong — 744 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 244 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Views/NotesView.swift OpenOats/Sources/OpenOats/Views/NotesView.swift— FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: NotesView (4-909). The bar is 500 significant lines; this is 179 over it, 1.36× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Views/HomeTimelineWorkspaceView.swift OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift— FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: HomeTimelineWorkspaceView (4-688). The bar is 500 significant lines; this is 158 over it, 1.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Intelligence/KnowledgeBase.swift OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: KnowledgeBase (152-931). The bar is 500 significant lines; this is 138 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Audio/SystemAudioCapture.swift OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: SystemAudioCapture (10-821). The bar is 500 significant lines; this is 99 over it, 1.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Views/ContentView.swift OpenOats/Sources/OpenOats/Views/ContentView.swift— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: ContentView (5-654). The bar is 500 significant lines; this is 93 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
ClassTooLong: MeetingDetailPane OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:40— ClassTooLong — 2974 significant lines (blank, comment-only and punctuation-only lines excluded), 129 methods. The bar is 400 significant lines; this is 2574 over it, 7.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SettingsStore OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:7— ClassTooLong — 1297 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 897 over it, 3.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LiveSessionController OpenOats/Sources/OpenOats/App/LiveSessionController.swift:58— ClassTooLong — 1245 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 845 over it, 3.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NotesController OpenOats/Sources/OpenOats/App/NotesController.swift:156— ClassTooLong — 1063 significant lines (blank, comment-only and punctuation-only lines excluded), 87 methods. The bar is 400 significant lines; this is 663 over it, 2.66× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TranscriptionEngine OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:66— ClassTooLong — 1043 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 400 significant lines; this is 643 over it, 2.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NotesView OpenOats/Sources/OpenOats/Views/NotesView.swift:4— ClassTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 248 over it, 1.62× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SystemAudioCapture OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:10— ClassTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 192 over it, 1.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: KnowledgeBase OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:150— ClassTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 130 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SuggestionEngine OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:9— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 95 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HomeTimelineWorkspaceView OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:4— ClassTooLong — 484 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 84 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WizardViewModel OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:5— ClassTooLong — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 73 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ContentView OpenOats/Sources/OpenOats/Views/ContentView.swift:5— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:570— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:201— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:50— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:127— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:176— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:221— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:174— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:454— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:472— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
TooManyMethods: MeetingDetailPane OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:40— TooManyMethods — 129 methods. The bar is 30 methods; this is 99 over it, 4.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SessionRepository OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:181— TooManyMethods — 103 methods. The bar is 30 methods; this is 73 over it, 3.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NotesController OpenOats/Sources/OpenOats/App/NotesController.swift:156— TooManyMethods — 87 methods. The bar is 30 methods; this is 57 over it, 2.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LiveSessionController OpenOats/Sources/OpenOats/App/LiveSessionController.swift:58— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TranscriptionEngine OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:66— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsStore OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:7— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NotesView OpenOats/Sources/OpenOats/Views/NotesView.swift:4— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Hotspot: OpenOats/Sources/OpenOats/Settings/SettingsStore.swift OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1464— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in SettingsStore.init at line 1464. 1 of those changes was a fix/bug commit, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:47:14 +03:00' --until='2026-11-03 15:47:14 +03:00' --full-history --no-merges -- OpenOats/Sources/OpenOats/Settings/SettingsStore.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: OpenOats/Sources/OpenOats/Views/SettingsView.swift OpenOats/Sources/OpenOats/Views/SettingsView.swift:459— OpenOats/Sources/OpenOats/Views/SettingsView.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in TranscriptionSettingsTab.body at line 459. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:47:14 +03:00' --until='2026-11-03 15:47:14 +03:00' --full-history --no-merges -- OpenOats/Sources/OpenOats/Views/SettingsView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: OpenOats/Sources/OpenOats/Views/ContentView.swift OpenOats/Sources/OpenOats/Views/ContentView.swift:283— OpenOats/Sources/OpenOats/Views/ContentView.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ContentView.contentWithLifecycle at line 283. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:47:14 +03:00' --until='2026-11-03 15:47:14 +03:00' --full-history --no-merges -- OpenOats/Sources/OpenOats/Views/ContentView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:182— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in OpenRouterClient.streamCompletion at line 182. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:47:14 +03:00' --until='2026-11-03 15:47:14 +03:00' --full-history --no-merges -- OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift:103— OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in StreamingTranscriber.run at line 103. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-05..2026-11-03, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-05 15:47:14 +03:00' --until='2026-11-03 15:47:14 +03:00' --full-history --no-merges -- OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:81— OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:81-94 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2133-2145 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Intelligence/MarkdownMeetingWriter.swift:354— OpenOats/Sources/OpenOats/Intelligence/MarkdownMeetingWriter.swift:354-366 | OpenOats/Sources/OpenOats/Intelligence/MarkdownMeetingWriter.swift:470-482 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1602— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1602-1614 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2257-2269 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/Meeting/CameraActivityMonitor.swift:95— OpenOats/Sources/OpenOats/Meeting/CameraActivityMonitor.swift:95-107 | OpenOats/Sources/OpenOats/Meeting/CameraActivityMonitor.swift:109-121 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) OpenOats/Sources/OpenOats/App/NotesController.swift:914— OpenOats/Sources/OpenOats/App/NotesController.swift:914-926 | OpenOats/Sources/OpenOats/App/NotesController.swift:928-942 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×5
Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:599— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:599-605 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:904-912 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1749— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1749-1755 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1757-1766 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1964— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1964-1970 | OpenOats/Sources/OpenOats/Views/NotesView.swift:646-652 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:89— OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:89-99 | OpenOats/Sources/OpenOats/Utils/DiagnosticsSupport.swift:137-143 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift:46— OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift:46-52 | OpenOats/Sources/OpenOats/Transcription/Qwen3Backend.swift:49-59 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:543— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:543-547 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:1050-1054 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:554— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:554-558 | OpenOats/Sources/OpenOats/Views/NotesView.swift:569-573 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1897— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1897-1901 | OpenOats/Sources/OpenOats/Views/NotesView.swift:411-415 — before extracting anything, compare `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift` and `OpenOats/Sources/OpenOats/Views/NotesView.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) OpenOats/Sources/OpenOats/Views/ContentView.swift:562— OpenOats/Sources/OpenOats/Views/ContentView.swift:562-566 | OpenOats/Sources/OpenOats/Views/TranscriptWindowView.swift:43-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/ContentView.swift:562` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:29— OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:29-33 | OpenOats/Sources/OpenOats/Wizard/SetupSnapshot.swift:98-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift:557— OpenOats/Sources/OpenOats/Views/ContentView.swift:557-566 | OpenOats/Sources/OpenOats/Views/TranscriptWindowView.swift:39-47 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:215— OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:215-223 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1914-1922 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift:625— OpenOats/Sources/OpenOats/Views/ContentView.swift:625-638 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2415-2423 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1446— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1446-1454 | OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift:405-413 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×4
Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:491— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:491-496 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:486-491 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:867— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:867-872 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1742-1747 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1865— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1865-1870 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:2323-2328 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:315— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:315-320 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:373-378 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×4
Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:498— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:498-501 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:497-500 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:591— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:591-594 | OpenOats/Sources/OpenOats/App/NotesController.swift:1271-1274 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:615— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:615-618 | OpenOats/Sources/OpenOats/App/NotesController.swift:1287-1290 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:486— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:486-489 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:481-484 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:18— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:18-30 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:52-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2626— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2626-2638 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3298-3310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2626` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) OpenOats/Sources/OpenOats/Views/SettingsView.swift:785— OpenOats/Sources/OpenOats/Views/SettingsView.swift:785-797 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:410-422 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/SettingsView.swift:785` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:549— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:549-561 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:1056-1068 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:503— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:503-515 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:1017-1028 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:503` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:637— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:637-648 | OpenOats/Sources/OpenOats/Views/NotesView.swift:575-586 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1926— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1926-1937 | OpenOats/Sources/OpenOats/Views/NotesView.swift:821-832 — before extracting anything, compare `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift` and `OpenOats/Sources/OpenOats/Views/NotesView.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:425— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:425-436 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:267-278 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:216— OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:216-223 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1915-1922 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:172— OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:172-179 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:301-308 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:846— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:846-853 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:502-509 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:225— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:225-232 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:361-368 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3797— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3797-3803 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3804-3810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3797` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:629— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:629-635 | OpenOats/Sources/OpenOats/App/NotesController.swift:1297-1303 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:863— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:863-869 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:831-837 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:376— OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:376-382 | OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:711-717 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:494— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:494-499 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:1007-1013 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:494` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2072— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2072-2077 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2078-2083 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:532— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:532-537 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:566-571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `config` to `ImportedSessionConfig` in one and `ManualTranscriptSessionConfig` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:540` calls `appendingPathComponent`, `createDirectory` and `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:573` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:597— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:597-602 | OpenOats/Sources/OpenOats/App/NotesController.swift:1264-1269 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
No assertions: testStreamUsesUnboundedBuffering OpenOats/Tests/OpenOatsTests/MeetingDetectionControllerTests.swift:176— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTypealiasCompiles OpenOats/Tests/OpenOatsTests/SettingsStoreTests.swift:958— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testStorageTypealiasCompiles OpenOats/Tests/OpenOatsTests/SettingsStoreTests.swift:965— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:916— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:916-969 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:984-1029 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1085-1118 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1120-1149 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1157-1187 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:668— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:668-687 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:518-537 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:885-904 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:420-439 | OpenOats/Sources/OpenOats/Views/NotesView.swift:714-733 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:16— OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:16-40 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:43-67 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:70-94 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:97-121 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:124-155 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:500— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:500-552 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:734-819 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:959-1027 | OpenOats/Sources/OpenOats/Views/NotesView.swift:515-567 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:637— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:637-648 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:408-420 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:380-400 | OpenOats/Sources/OpenOats/Views/NotesView.swift:575-586 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:11— OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:11-104 | OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:7-88 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:11-133 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:14-75 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×3
Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:43— OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:43-67 | OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:72-96 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift:8— OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift:8-32 | OpenOats/Sources/OpenOats/Views/OverlayPanel.swift:6-31 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift:799— OpenOats/Sources/OpenOats/Views/SettingsView.swift:799-823 | OpenOats/Sources/OpenOats/Views/SettingsView.swift:831-855 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift:28— OpenOats/Sources/OpenOats/Transcription/ParakeetBackend.swift:28-44 | OpenOats/Sources/OpenOats/Transcription/Qwen3Backend.swift:27-47 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:19— OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:19-36 | OpenOats/Sources/OpenOats/Wizard/SetupSnapshot.swift:92-108 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) OpenOats/Sources/OpenOats/Views/ContentView.swift:580— OpenOats/Sources/OpenOats/Views/ContentView.swift:580-600 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2374-2390 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift:200— OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift:200-219 | OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:409-429 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/App/NotesController.swift:207— OpenOats/Sources/OpenOats/App/NotesController.swift:207-236 | OpenOats/Sources/OpenOats/App/NotesController.swift:267-286 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1359— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1359-1378 | OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1425-1444 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1258— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1258-1272 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1278-1288 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:119— OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:119-131 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1054-1064 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift:406— OpenOats/Sources/OpenOats/Views/SettingsView.swift:406-417 | OpenOats/Sources/OpenOats/Views/SettingsView.swift:1076-1086 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (20 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3260— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3260-3279 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3302-3321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3258` calls `accessibilityIdentifier` and `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3300` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:19— OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:19-38 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:46-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:19` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:11— OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:11-30 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:14-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) OpenOats/Sources/OpenOats/App/NotesController.swift:319— OpenOats/Sources/OpenOats/App/NotesController.swift:319-329 | OpenOats/Sources/OpenOats/App/NotesController.swift:472-482 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:331— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:331-341 | OpenOats/Sources/OpenOats/Views/NotesView.swift:880-890 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:774— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:774-784 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:718-728 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:774` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 4) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:938— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:938-947 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:993-1002 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1132-1141 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1168-1177 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:937— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:937-946 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1100-1109 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1131-1140 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1167-1176 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:84— OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:84-93 | OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:74-83 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:107-116 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:51-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:84` calls `accessibilityIdentifier` and `OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:117` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:604— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:604-613 | OpenOats/Sources/OpenOats/App/NotesController.swift:1277-1285 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 2) OpenOats/Sources/OpenOats/App/NotesController.swift:963— OpenOats/Sources/OpenOats/App/NotesController.swift:963-971 | OpenOats/Sources/OpenOats/App/NotesController.swift:1015-1024 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/App/NotesController.swift:963` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 2) OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:85— OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:85-94 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2137-2145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3623— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3623-3632 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3886-3895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3623` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:79— OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:79-88 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:250-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `spacing` to `4` in one and `8` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:438— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:438-449 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:280-289 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:145— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:145-153 | OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:156-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:289— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:289-297 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:320-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift:207— OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift:207-215 | OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:416-424 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/SidecastPanelContent.swift:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Change-coupling hub: SettingsStore.swift → MeetingDetectionController.swift, KnowledgeBase.swift, NotesEngine.swift, SuggestionEngine.swift, NotificationService.swift, SettingsView.swift OpenOats/Sources/OpenOats/Settings/SettingsStore.swift— `OpenOats/Sources/OpenOats/Settings/SettingsStore.swift` changes together with 6 other files — `OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift`, `OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift`, `OpenOats/Sources/OpenOats/Intelligence/NotesEngine.swift`, `OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift`, `OpenOats/Sources/OpenOats/Meeting/NotificationService.swift`, `OpenOats/Sources/OpenOats/Views/SettingsView.swift` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: SettingsView.swift → MeetingDetectionController.swift, SuggestionEngine.swift, NotificationService.swift OpenOats/Sources/OpenOats/Views/SettingsView.swift— `OpenOats/Sources/OpenOats/Views/SettingsView.swift` changes together with 3 other files — `OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift`, `OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift`, `OpenOats/Sources/OpenOats/Meeting/NotificationService.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1989— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1989-2017 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2020-2054 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:794— OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:794-822 | OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:840-870 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:17— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:17-47 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:51-77 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) OpenOats/Sources/OpenOats/Domain/MeetingTypes.swift:60— OpenOats/Sources/OpenOats/Domain/MeetingTypes.swift:60-86 | OpenOats/Sources/OpenOats/Models/Models.swift:279-305 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:171— OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:171-193 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:300-326 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:110— OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:110-132 | OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:136-159 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift:779— OpenOats/Sources/OpenOats/Views/SettingsView.swift:779-797 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:404-422 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:101— OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:101-120 | OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:122-140 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:40— OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:40-53 | OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:55-68 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1242— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1242-1256 | OpenOats/Sources/OpenOats/Views/NotesView.swift:688-701 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:54— OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:54-66 | OpenOats/Sources/OpenOats/Settings/SettingsStorage.swift:68-79 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:253— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:253-271 | OpenOats/Sources/OpenOats/Views/NotesView.swift:423-434 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1574— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1574-1578 | OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:136-140 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:82— OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:82-86 | OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:33-37 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:917— OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:917-937 | OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:983-1003 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:917` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:940` calls `finishStream` and `OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:1005` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) OpenOats/Sources/OpenOats/Views/ContentView.swift:603— OpenOats/Sources/OpenOats/Views/ContentView.swift:603-623 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2393-2413 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19–20 lines × 2) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1326— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1326-1345 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1364-1382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1326` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 2) OpenOats/Sources/OpenOats/Views/SettingsView.swift:752— OpenOats/Sources/OpenOats/Views/SettingsView.swift:752-770 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:380-399 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/SettingsView.swift:752` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1998— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1998-2016 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2033-2051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1998` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:937— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:937-955 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1057-1075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:937` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 2) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:232— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:232-248 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:458-473 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:250` calls `StreamOutcome` and `OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:475` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–17 lines × 2) OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:741— OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:741-756 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:973-989 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:741` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1360— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1360-1375 | OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1426-1441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:77— OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:77-92 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:104-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:389— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:389-403 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:223-237 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:389` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:99— OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:99-113 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:175-189 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: AppCoordinator (LCOM4 6) OpenOats/Sources/OpenOats/App/AppCoordinator.swift:16— AppCoordinator's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SettingsStore (LCOM4 5) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:7— SettingsStore's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Sync-over-async blocking OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:194— `bufferStream` is async and calls usleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Sync-over-async blocking OpenOats/Sources/OpenOats/Utils/DiagnosticsSupport.swift:217— `unifiedLogReport` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark promo/openoats-hype.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard promo/openoats-hype.html:154— `#start .pb` moves (`transition: transform .2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Low contrast colour pair in CSS (3.5:1) promo/openoats-hype.html:75— `#shareF div` sets color: #fff on background-color: #ff3b30 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.4:1) promo/openoats-hype.html:108— `.model` sets color: #77777f on background-color: #26262b — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.8:1) promo/openoats-hype.html:136— `#aq` sets color: #fff on background-color: #5b9bf5 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
LiveSessionController.finalizeCurrentSession (cyclomatic 46) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:746— LiveSessionController.finalizeCurrentSession has cyclomatic complexity 46 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SidecastPreset.apply (cyclomatic 38) OpenOats/Sources/OpenOats/Models/SidecastPreset.swift:90— SidecastPreset.apply has cyclomatic complexity 38 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
StreamingTranscriber.run (cyclomatic 34) OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift:103— StreamingTranscriber.run has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsStore.init (cyclomatic 31) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1464— SettingsStore.init has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TranscriptionEngine.start (cyclomatic 31) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:455— TranscriptionEngine.start has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ControlBar.body (cyclomatic 31) OpenOats/Sources/OpenOats/Views/ControlBar.swift:43— ControlBar.body has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiveSessionController.synchronizeDerivedState (cyclomatic 29) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1720— LiveSessionController.synchronizeDerivedState has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AudioRecorder.writeMicBuffer (cyclomatic 29) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:78— AudioRecorder.writeMicBuffer has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NotesEngine.generate (cyclomatic 28) OpenOats/Sources/OpenOats/Intelligence/NotesEngine.swift:76— NotesEngine.generate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AudioRecorder.mergeAndEncode (cyclomatic 25) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:355— AudioRecorder.mergeAndEncode has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BatchTextCleaner.cleanup (cyclomatic 25) OpenOats/Sources/OpenOats/Intelligence/BatchTextCleaner.swift:53— BatchTextCleaner.cleanup has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TranscriptionSettingsTab.body (cyclomatic 25) OpenOats/Sources/OpenOats/Views/SettingsView.swift:459— TranscriptionSettingsTab.body has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LiveTranscriptCleaner.performCleanup (cyclomatic 24) OpenOats/Sources/OpenOats/Intelligence/LiveTranscriptCleaner.swift:92— LiveTranscriptCleaner.performCleanup has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SystemAudioCapture.bufferStream (cyclomatic 23) OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:194— SystemAudioCapture.bufferStream has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppCoordinator.startDetectionEventLoop (cyclomatic 21) OpenOats/Sources/OpenOats/App/AppCoordinator.swift:312— AppCoordinator.startDetectionEventLoop has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KnowledgeBase.chunkMarkdownStatic (cyclomatic 21) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:559— KnowledgeBase.chunkMarkdownStatic has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TranscriptView.transcriptScrollView (cyclomatic 21) OpenOats/Sources/OpenOats/Views/TranscriptView.swift:73— TranscriptView.transcriptScrollView has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MicCapture.bufferStream (cyclomatic 20) OpenOats/Sources/OpenOats/Audio/MicCapture.swift:67— MicCapture.bufferStream has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
KnowledgeBase.index (cyclomatic 20) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:220— KnowledgeBase.index has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SidecastEngine.apply (cyclomatic 20) OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:145— SidecastEngine.apply has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StreamingAudioConverter.extractSamples (cyclomatic 20) OpenOats/Sources/OpenOats/Transcription/StreamingAudioConverter.swift:15— StreamingAudioConverter.extractSamples has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ContentView.contentWithLifecycle (cyclomatic 20) OpenOats/Sources/OpenOats/Views/ContentView.swift:283— ContentView.contentWithLifecycle has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OpenRouterClient.streamCompletion (cyclomatic 19) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:182— OpenRouterClient.streamCompletion has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IntelligenceSettingsTab.body (cyclomatic 19) OpenOats/Sources/OpenOats/Views/SettingsView.swift:873— IntelligenceSettingsTab.body has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WizardViewModel.canAdvance (cyclomatic 19) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:314— WizardViewModel.canAdvance has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
LiveSessionController.runPollingLoop (cyclomatic 18) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:233— LiveSessionController.runPollingLoop has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiveSessionController.recordingHealthNotice (cyclomatic 18) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1380— LiveSessionController.recordingHealthNotice has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AudioRecorder.readAllMono (cyclomatic 18) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:461— AudioRecorder.readAllMono has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ContentView.rootContent (cyclomatic 18) OpenOats/Sources/OpenOats/Views/ContentView.swift:31— ContentView.rootContent has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsStore.migrateFilesFromOpenGranola (cyclomatic 17) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2059— SettingsStore.migrateFilesFromOpenGranola has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiveSessionController.refreshState (cyclomatic 16) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1619— LiveSessionController.refreshState has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MeetingDetectionController.handleMeetingDetected (cyclomatic 16) OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift:370— MeetingDetectionController.handleMeetingDetected has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NotesController.isLikelyMeetingHistoryNameLine (cyclomatic 16) OpenOats/Sources/OpenOats/App/NotesController.swift:1662— NotesController.isLikelyMeetingHistoryNameLine has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KnowledgeBase.searchRaw (cyclomatic 16) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:432— KnowledgeBase.searchRaw has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SuggestionEngine.onUtterance (cyclomatic 16) OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:218— SuggestionEngine.onUtterance has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppleNotesService.markdownToHTML (cyclomatic 16) OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:304— AppleNotesService.markdownToHTML has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SessionRepository.normalizedMirrorAssetPath (cyclomatic 16) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:2240— SessionRepository.normalizedMirrorAssetPath has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BatchAudioSampleReader.resample (cyclomatic 16) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:972— BatchAudioSampleReader.resample has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WizardViewModel.applySettings (cyclomatic 16) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:607— WizardViewModel.applySettings has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StreamingTranscriber.run (cognitive 91) OpenOats/Sources/OpenOats/Transcription/StreamingTranscriber.swift:103— StreamingTranscriber.run has cognitive complexity 91 (threshold 15). Drivers by points: if/else 22 (66 pts), error handling 2 (9 pts), boolean chains 8, match/switch 1 (5 pts), loops 2 (3 pts) (nesting depth added 56). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LiveSessionController.synchronizeDerivedState (cognitive 63) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1720— LiveSessionController.synchronizeDerivedState has cognitive complexity 63 (threshold 15). Drivers by points: if/else 35 (60 pts), boolean chains 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiveSessionController.finalizeCurrentSession (cognitive 62) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:746— LiveSessionController.finalizeCurrentSession has cognitive complexity 62 (threshold 15). Drivers by points: if/else 34 (42 pts), boolean chains 18, ternaries 2 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
LiveSessionController.runPollingLoop (cognitive 52) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:233— LiveSessionController.runPollingLoop has cognitive complexity 52 (threshold 15). Drivers by points: if/else 9 (34 pts), ternaries 2 (8 pts), match/switch 1 (5 pts), boolean chains 4, loops 1 (nesting depth added 35). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ControlBar.body (cognitive 52) OpenOats/Sources/OpenOats/Views/ControlBar.swift:43— ControlBar.body has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 17 (34 pts), if/else 10 (14 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemAudioCapture.bufferStream (cognitive 51) OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift:194— SystemAudioCapture.bufferStream has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (47 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioRecorder.writeMicBuffer (cognitive 48) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:78— AudioRecorder.writeMicBuffer has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (25 pts), loops 5 (15 pts), boolean chains 5, error handling 2 (3 pts) (nesting depth added 16). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KnowledgeBase.chunkMarkdownStatic (cognitive 47) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:559— KnowledgeBase.chunkMarkdownStatic has cognitive complexity 47 (threshold 15). Drivers by points: if/else 19 (38 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppCoordinator.startDetectionEventLoop (cognitive 46) OpenOats/Sources/OpenOats/App/AppCoordinator.swift:312— AppCoordinator.startDetectionEventLoop has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (42 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SettingsStore.init (cognitive 44) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1464— SettingsStore.init has cognitive complexity 44 (threshold 15). Drivers by points: if/else 30 (34 pts), ternaries 6, boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
KnowledgeBase.index (cognitive 39) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:220— KnowledgeBase.index has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 3 (8 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranscriptionEngine.start (cognitive 39) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:455— TranscriptionEngine.start has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 6, loops 1 (2 pts), error handling 1, match/switch 1, ternaries 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OpenRouterClient.streamCompletion (cognitive 37) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:182— OpenRouterClient.streamCompletion has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (28 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AudioRecorder.mergeAndEncode (cognitive 33) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:355— AudioRecorder.mergeAndEncode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 7, ternaries 2 (6 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotesEngine.generate (cognitive 33) OpenOats/Sources/OpenOats/Intelligence/NotesEngine.swift:76— NotesEngine.generate has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (24 pts), error handling 2 (3 pts), loops 1 (2 pts), match/switch 2, ternaries 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContentView.rootContent (cognitive 31) OpenOats/Sources/OpenOats/Views/ContentView.swift:31— ContentView.rootContent has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchTextCleaner.cleanup (cognitive 30) OpenOats/Sources/OpenOats/Intelligence/BatchTextCleaner.swift:53— BatchTextCleaner.cleanup has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 3, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiveTranscriptCleaner.performCleanup (cognitive 30) OpenOats/Sources/OpenOats/Intelligence/LiveTranscriptCleaner.swift:92— LiveTranscriptCleaner.performCleanup has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 6 (12 pts), error handling 1, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsStore.migrateFilesFromOpenGranola (cognitive 28) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:2059— SettingsStore.migrateFilesFromOpenGranola has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StreamingAudioConverter.extractSamples (cognitive 28) OpenOats/Sources/OpenOats/Transcription/StreamingAudioConverter.swift:15— StreamingAudioConverter.extractSamples has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (17 pts), loops 2 (7 pts), boolean chains 4 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OllamaSetupClient.pullModel (cognitive 28) OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:39— OllamaSetupClient.pullModel has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 3, error handling 3, loops 1 (2 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SidecastEngine.apply (cognitive 27) OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:145— SidecastEngine.apply has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SuggestionEngine.streamSynthesis (cognitive 27) OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:374— SuggestionEngine.streamSynthesis has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (22 pts), error handling 2, loops 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SidecastPreset.apply (cognitive 27) OpenOats/Sources/OpenOats/Models/SidecastPreset.swift:90— SidecastPreset.apply has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 3 (9 pts), boolean chains 5 (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TranscriptView.transcriptScrollView (cognitive 27) OpenOats/Sources/OpenOats/Views/TranscriptView.swift:73— TranscriptView.transcriptScrollView has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 9 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppleNotesService.markdownToHTML (cognitive 26) OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:304— AppleNotesService.markdownToHTML has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 2, loops 1 (nesting depth added 10). Of this number, 24 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchAudioTranscriber.transcribeFile (cognitive 26) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:677— BatchAudioTranscriber.transcribeFile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotesView.sidebar (cognitive 26) OpenOats/Sources/OpenOats/Views/NotesView.swift:124— NotesView.sidebar has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (26 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContentView.contentWithLifecycle (cognitive 25) OpenOats/Sources/OpenOats/Views/ContentView.swift:283— ContentView.contentWithLifecycle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OpenRouterClient.streamAnthropicCompletion (cognitive 24) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:427— OpenRouterClient.streamAnthropicCompletion has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranscriptionSettingsTab.body (cognitive 24) OpenOats/Sources/OpenOats/Views/SettingsView.swift:459— TranscriptionSettingsTab.body has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12, boolean chains 10, match/switch 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AudioRecorder.readAllMono (cognitive 23) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:461— AudioRecorder.readAllMono has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, loops 1 (3 pts), error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MicCapture.bufferStream (cognitive 23) OpenOats/Sources/OpenOats/Audio/MicCapture.swift:67— MicCapture.bufferStream has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 7, error handling 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BatchAudioTranscriber.detectSpeech (cognitive 23) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:853— BatchAudioTranscriber.detectSpeech has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranscriptionEngine.startSystemAudioStream (cognitive 23) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:1177— TranscriptionEngine.startSystemAudioStream has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiveSessionController.recordingHealthNotice (cognitive 22) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:1380— LiveSessionController.recordingHealthNotice has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MeetingDetectionController.handleMeetingDetected (cognitive 22) OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift:370— MeetingDetectionController.handleMeetingDetected has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 3 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KnowledgeBase.searchRaw (cognitive 22) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:432— KnowledgeBase.searchRaw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), error handling 2 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotesController.loadMeetingHistorySuggestions (cognitive 21) OpenOats/Sources/OpenOats/App/NotesController.swift:1426— NotesController.loadMeetingHistorySuggestions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KnowledgeBase.embedBatchesConcurrently (cognitive 21) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:779— KnowledgeBase.embedBatchesConcurrently has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KnowledgeBase.embedBatchesSequentially (cognitive 21) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:822— KnowledgeBase.embedBatchesSequentially has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KnowledgeBase.scanFiles (cognitive 20) OpenOats/Sources/OpenOats/Intelligence/KnowledgeBase.swift:348— KnowledgeBase.scanFiles has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 2 (6 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MeetingDetector.handleMicSignal (cognitive 20) OpenOats/Sources/OpenOats/Meeting/MeetingDetector.swift:356— MeetingDetector.handleMicSignal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionRepository.rewriteJSONLWithCleanedText (cognitive 20) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1954— SessionRepository.rewriteJSONLWithCleanedText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchAudioSampleReader.resample (cognitive 20) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:972— BatchAudioSampleReader.resample has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MeetingDetailPane.parseMarkdownSections (cognitive 20) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3787— MeetingDetailPane.parseMarkdownSections has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkdownTextFlow.inlineMarkdown (cognitive 20) OpenOats/Sources/OpenOats/Views/SelectableTextFlow.swift:240— MarkdownTextFlow.inlineMarkdown has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotesController.meetingHistoryHighlights (cognitive 19) OpenOats/Sources/OpenOats/App/NotesController.swift:1574— NotesController.meetingHistoryHighlights has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 9). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchTranscriptionSegmentLayout.slices (cognitive 19) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:35— BatchTranscriptionSegmentLayout.slices has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MeetingDetailPane.notesEmptyState (cognitive 19) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3135— MeetingDetailPane.notesEmptyState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 4 (5 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MeetingDetailPane.notesExportAttributedText (cognitive 19) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3877— MeetingDetailPane.notesExportAttributedText has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 3 (5 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 11). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WizardViewModel.canAdvance (cognitive 19) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:314— WizardViewModel.canAdvance has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 4 (8 pts), match/switch 1 (nesting depth added 4). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
openoats-hype.html.schedule (cognitive 19) promo/openoats-hype.html:443— openoats-hype.html.schedule has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (4 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiveSessionController.startTranscription (cognitive 18) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:648— LiveSessionController.startTranscription has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ElevenLabsScribeBackend.buildDiarizedSegments (cognitive 18) OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:221— ElevenLabsScribeBackend.buildDiarizedSegments has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 8, loops 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguagePrivacyStepView.body (cognitive 18) OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:11— LanguagePrivacyStepView.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (7 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RecommendationEngine.nextStepAfterIntent (cognitive 18) OpenOats/Sources/OpenOats/Wizard/RecommendationEngine.swift:328— RecommendationEngine.nextStepAfterIntent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 7, ternaries 1 (2 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
NotesController.insertAssets (cognitive 17) OpenOats/Sources/OpenOats/App/NotesController.swift:676— NotesController.insertAssets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SuggestionEngine.onUtterance (cognitive 17) OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:218— SuggestionEngine.onUtterance has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MeetingDetectionController.startSilenceMonitoring (cognitive 16) OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift:276— MeetingDetectionController.startSilenceMonitoring has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotesController.isLikelyMeetingHistoryNameLine (cognitive 16) OpenOats/Sources/OpenOats/App/NotesController.swift:1662— NotesController.isLikelyMeetingHistoryNameLine has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 3 (4 pts), loops 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MicCapture.normalizedRMS (cognitive 16) OpenOats/Sources/OpenOats/Audio/MicCapture.swift:298— MicCapture.normalizedRMS has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), loops 2 (5 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchAudioTranscriber.runTranscription (cognitive 16) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:522— BatchAudioTranscriber.runTranscription has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ElevenLabsScribeBackend.parseKeyterms (cognitive 16) OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:300— ElevenLabsScribeBackend.parseKeyterms has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MeetingDetailPane.notesToolbarActions (cognitive 16) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2143— MeetingDetailPane.notesToolbarActions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WizardViewModel.applySettings (cognitive 16) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:607— WizardViewModel.applySettings has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:437— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:437-495 | OpenOats/Sources/OpenOats/App/NotesController.swift:676-754 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (83 corresponding lines) · ×1
Edited copy of a member (83 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1798— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1798-1890 | OpenOats/Sources/OpenOats/Views/NotesView.swift:737-819 — These two members are one piece of code written twice and then edited apart: 83 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:461— OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:461-529 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:972-1048 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:90— OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:90-140 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:165-220 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:915— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:915-957 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1029-1077 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:313— OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:313-353 | OpenOats/Sources/OpenOats/Transcription/BatchAudioTranscriber.swift:368-411 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1302— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1302-1345 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1347-1382 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:94— OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:94-121 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:64-93 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:910— OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:910-973 | OpenOats/Sources/OpenOats/Transcription/TranscriptionEngine.swift:975-1024 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) OpenOats/Sources/OpenOats/Views/OverlayPanel.swift:59— OpenOats/Sources/OpenOats/Views/OverlayPanel.swift:59-90 | OpenOats/Sources/OpenOats/Views/OverlayPanel.swift:93-122 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:560— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:560-599 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1761-1796 | OpenOats/Sources/OpenOats/Views/NotesView.swift:370-404 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) OpenOats/Sources/OpenOats/Views/SettingsView.swift:750— OpenOats/Sources/OpenOats/Views/SettingsView.swift:750-777 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:379-402 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1935— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1935-1944 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1946-1957 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1959-1974 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:236— OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:236-251 | OpenOats/Sources/OpenOats/Meeting/NotificationService.swift:255-270 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 16+ corresponding lines) · ×1
Edited copies of one member (5 members, 16+ corresponding lines) OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:464— OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:464-479 | OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:481-496 | OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:498-513 | OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:515-530 | OpenOats/Sources/OpenOats/Wizard/WizardViewModel.swift:532-547 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1333— OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1333-1347 | OpenOats/Sources/OpenOats/Settings/SettingsStore.swift:1367-1381 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:596— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:596-602 | OpenOats/Sources/OpenOats/App/NotesController.swift:1263-1269 | OpenOats/Sources/OpenOats/Intelligence/MarkdownMeetingWriter.swift:279-286 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:5— OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:5-21 | OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:23-38 | OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:70-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) OpenOats/Sources/OpenOats/Audio/MicCapture.swift:418— OpenOats/Sources/OpenOats/Audio/MicCapture.swift:418-429 | OpenOats/Sources/OpenOats/Audio/MicCapture.swift:432-442 | OpenOats/Sources/OpenOats/Audio/MicCapture.swift:445-455 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) OpenOats/Sources/OpenOats/Domain/Utterance.swift:84— OpenOats/Sources/OpenOats/Domain/Utterance.swift:84-91 | OpenOats/Sources/OpenOats/Domain/Utterance.swift:110-117 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:421— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:421-423 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:263-265 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:451— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:451-454 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:302-305 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1490-1493 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:664— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:664-666 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:514-516 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:416-418 | OpenOats/Sources/OpenOats/Views/NotesView.swift:710-712 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (77 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1800— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1800-1876 | OpenOats/Sources/OpenOats/Views/NotesView.swift:739-815 — before extracting anything, compare `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift` and `OpenOats/Sources/OpenOats/Views/NotesView.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1800` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `spacing` to `14` in one and `10` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (51 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:502— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:502-552 | OpenOats/Sources/OpenOats/Views/NotesView.swift:517-567 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (78 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:287— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:287-364 | OpenOats/Sources/OpenOats/Views/NotesView.swift:436-513 — before extracting anything, compare `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift` and `OpenOats/Sources/OpenOats/Views/NotesView.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (48 lines × 2) OpenOats/Sources/OpenOats/App/LiveSessionController.swift:442— OpenOats/Sources/OpenOats/App/LiveSessionController.swift:442-489 | OpenOats/Sources/OpenOats/App/NotesController.swift:685-732 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (34 lines × 2) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2830— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2830-2863 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2871-2904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2830` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2864` calls `frame` and `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2905` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35 lines × 2) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:601— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:601-635 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:372-406 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (25–27 lines × 2) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:97— OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:97-121 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:67-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:97— OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:97-119 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:41-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:97` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 5) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:668— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:668-687 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:518-537 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:885-904 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:420-439 | OpenOats/Sources/OpenOats/Views/NotesView.swift:714-733 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (17 lines × 2) OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:399— OpenOats/Sources/OpenOats/Intelligence/SidecastEngine.swift:399-415 | OpenOats/Sources/OpenOats/Intelligence/SuggestionEngine.swift:517-533 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 3) OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:14— OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:14-29 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:13-28 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:16-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (15–16 lines × 2) OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift:18— OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift:18-32 | OpenOats/Sources/OpenOats/Views/OverlayPanel.swift:16-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MiniBarPanel.swift:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 3) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1094— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1094-1108 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1126-1139 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1162-1175 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1094` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1161` calls `scheduleMirror` and `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1125` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 3) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2843— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2843-2857 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2884-2898 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3375-3389 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2843` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:2841` calls `font`, `system`, `foregroundStyle` and `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3374` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–14 lines × 3) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:94— OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:94-105 | OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift:45-56 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:64-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:127— OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:127-140 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:150-163 | OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:207-220 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `OpenOats/Sources/OpenOats/Wizard/IntentStepView.swift:125` calls `contentShape`, `Rectangle` and `OpenOats/Sources/OpenOats/Wizard/LanguagePrivacyStepView.swift:205` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 2) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:941— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:941-953 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:996-1009 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:996` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 4) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:521— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:521-532 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:758-769 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:995-1007 | OpenOats/Sources/OpenOats/Views/NotesView.swift:536-547 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:521` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:368— OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:368-380 | OpenOats/Sources/OpenOats/Intelligence/OpenRouterClient.swift:531-542 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 4) OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:29— OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:29-40 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:56-67 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:83-94 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:110-121 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 5) OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:17— OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:17-27 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:44-54 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:71-81 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:98-108 | OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift:125-135 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:941— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:941-951 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1061-1071 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1087-1097 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1106-1116 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:941` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:953` calls `menuStyle`, `buttonStyle` and `OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:1098` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:939— OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:939-949 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:994-1004 | OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:1169-1179 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:118— OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:118-126 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:154-162 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:184-192 | OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:214-222 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Wizard/ProviderSetupStepView.swift:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5–9 lines × 3) OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:96— OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:96-104 | OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:106-114 | OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:115-119 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:96` calls `textFieldStyle` and `OpenOats/Sources/OpenOats/Views/SidecastSettingsTab.swift:115` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:639— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:639-645 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:411-417 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:386-392 | OpenOats/Sources/OpenOats/Views/NotesView.swift:577-583 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (5 lines × 3) OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:110— OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:110-114 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:82-86 | OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:148-152 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift:153` calls `String`, `Data`, `prefix` and `OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:115` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3796— OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3796-3801 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3803-3808 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:3810-3815 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) OpenOats/Sources/OpenOats/Views/CalendarSettingsView.swift:461— OpenOats/Sources/OpenOats/Views/CalendarSettingsView.swift:461-470 | OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:456-465 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:291-300 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 5) OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:657— OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:657-662 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:503-508 | OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:855-860 | OpenOats/Sources/OpenOats/Views/MeetingDetailPane.swift:409-414 | OpenOats/Sources/OpenOats/Views/NotesView.swift:703-708 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `OpenOats/Sources/OpenOats/Views/IdleHomeDashboardView.swift:510` calls `folderDisplayName`, `folderDefinition` and `OpenOats/Sources/OpenOats/Views/HomeTimelineWorkspaceView.swift:664` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Off the main sequence: OpenOatsKit — OpenOatsKit: abstractness 0.01, instability 0.00, distance 0.99 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Duplicated block (11 lines × 2 locations) tools/sidecast-debug/src/ui.ts:705— tools/sidecast-debug/src/ui.ts:705 · tools/sidecast-debug/src/ui.ts:721 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) tools/sidecast-debug/src/ui.ts:254— tools/sidecast-debug/src/ui.ts:254 · tools/sidecast-debug/src/ui.ts:263 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) tools/sidecast-debug/src/ui.ts:282— tools/sidecast-debug/src/ui.ts:282 · tools/sidecast-debug/src/ui.ts:355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2 locations) tools/sidecast-debug/src/ui.ts:486— tools/sidecast-debug/src/ui.ts:486 · tools/sidecast-debug/src/ui.ts:502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Boundary violation [package:third-party-deep-import] tools/sidecast-debug/server/transcript-proxy.ts:3— tools/sidecast-debug/server/transcript-proxy.ts:3 imports youtube-transcript/dist/youtube-transcript.esm.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Complex function callLLM (cyclomatic 20, cognitive 26) tools/sidecast-debug/src/sidecast.ts:103— callLLM has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function filterAndRank (cyclomatic 15, cognitive 23) tools/sidecast-debug/src/sidecast.ts:230— filterAndRank has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderDebugLog (cyclomatic 13, cognitive 25) tools/sidecast-debug/src/ui.ts:627— renderDebugLog has cyclomatic complexity 13 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· tools/sidecast-debug/src/ui.ts · ×1
tools/sidecast-debug/src/ui.ts: 656 lines of code tools/sidecast-debug/src/ui.ts:1— tools/sidecast-debug/src/ui.ts has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Orphaned file OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Views/RecordingConsentView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Wizard/SetupWizardView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Wizard/WizardTypes.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Views/CalendarEventViews.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file OpenOats/Sources/OpenOats/Transcription/WAVEncoder.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Silent fallback default in catch OpenOats/Sources/OpenOats/Audio/AudioRecorder.swift:472— `readAllMono` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Meeting/CalendarManager.swift:431— `detectedURLs` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:31— `listSessions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/LegacySessionReader.swift:135— `loadLiveTranscript` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:899— `loadScratchpad` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:918— `listSessions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:2038— `scanPendingMirrorSessionIDs` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Storage/SessionRepository.swift:2221— `referencedMirrorAssetPaths` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch OpenOats/Sources/OpenOats/Utils/DiagnosticsSupport.swift:134— `loadContents` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: OpenOats/Sources/OpenOats/Views/NoteAssetMarkdownParser.swift, OpenOats/Sources/OpenOats/Transcription/CloudTranscriptCopy.swift, OpenOats/Sources/OpenOats/Views/OpenOatsProminentButtonStyle.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: OpenOats/Sources/OpenOats/Views/MiniBarContent.swift, OpenOats/Sources/OpenOats/Intelligence/RealtimeGate.swift, OpenOats/Sources/OpenOats/Transcription/ModelHubEndpoint.swift. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (11 single-owned of 106 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 106 of the 133 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: OpenOats/Sources/OpenOats/Views/SelectableTextFlow.swift, OpenOats/Sources/OpenOats/Views/ContentExporter.swift, OpenOats/Sources/OpenOats/Storage/MirrorAttemptLedger.swift, OpenOats/Sources/OpenOats/Meeting/SpeakerNameSeeder.swift, OpenOats/Sources/OpenOats/App/MenuBarNextMeeting.swift.
No ADRs found OpenOats/Package.swift:13— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `OpenOats/Package.swift` makes this repository a deployable product (line 13).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `OpenOats` (40811 LoC, 376 module-visible types across 14 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 9 of 106 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 106 of the 133 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: OpenOats/Sources/OpenOats/Meeting/AppleNotesService.swift, OpenOats/Sources/OpenOats/Transcription/OpenOatsLocalModelStore.swift, OpenOats/Sources/OpenOats/Wizard/ConfirmationStepView.swift, OpenOats/Sources/OpenOats/Wizard/OllamaSetupClient.swift, OpenOats/Sources/OpenOats/Views/RecordingConsentView.swift, OpenOats/Sources/OpenOats/Wizard/SetupWizardView.swift, OpenOats/Sources/OpenOats/Wizard/WizardTypes.swift, OpenOats/Sources/OpenOats/Views/CalendarEventViews.swift (and 1 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation tools/sidecast-debug/package.json:10— `tools/sidecast-debug/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Unused export 'getSummary' tools/sidecast-debug/src/transcript.ts:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'fieldToggle' · ×1
Unused module-local declaration 'fieldToggle' tools/sidecast-debug/src/ui.ts:70— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Duplicated predicate OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift:111— `http.statusCode == 401 || http.statusCode == 403` appears character-identically in 4 files — OpenOats/Sources/OpenOats/Transcription/AssemblyAIBackend.swift, OpenOats/Sources/OpenOats/Transcription/CohereTranscribeArabicBackend.swift, OpenOats/Sources/OpenOats/Transcription/ElevenLabsScribeBackend.swift, OpenOats/Sources/OpenOats/Wizard/APIKeyValidator.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Outdated: fluidaudio — `fluidaudio` is resolved at 0.13.5, but 0.18.3 is the newest release tagged on https://github.com/FluidInference/FluidAudio.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update fluidaudio` reaches this one with no change to Package.swift.
Outdated: sparkle — `sparkle` is resolved at 2.9.0, but 2.10.1 is the newest release tagged on https://github.com/sparkle-project/Sparkle within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sparkle` reaches this one with no change to Package.swift.
Outdated: whisperkit — `whisperkit` is resolved at 0.17.0, but 0.18.0 is the newest release tagged on https://github.com/argmaxinc/WhisperKit.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update whisperkit` reaches this one with no change to Package.swift.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 19 file(s) — `OpenOats/Sources/Benchmark/main.swift`, `OpenOats/Sources/OpenOats/App/AppCoordinator.swift`, `OpenOats/Sources/OpenOats/App/MeetingDetectionController.swift`, `OpenOats/Sources/OpenOats/App/NotesController.swift`, `OpenOats/Sources/OpenOats/Audio/SystemAudioCapture.swift`, … (+14 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dc4a-84da-7364-8656-7e0a8b9c21f9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 14 · Warnings: 368 · Recommendations: 37 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 23:00 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.