Public report of yuga-hashimoto/and-code, published 16 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, 16 November 2026, 22:40 UTC · Survey ID cd_398914bc1f9e434c8053edefce1967dc
yuga-hashimoto/and-code
Measured 16 November 2026, 22:38 UTC, at code version 244a7e0
First survey, so nothing to compare with yet
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
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: 68,370 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 31.8
Findings by how serious they are
38 critical323 serious54 minor
13 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
16 November 2026, 22:38 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.
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 ▸
58of 58 dimensions measured by tools.
407of 415 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
58dimensions across 8 lenses, read from 68,370 lines of product code in 2 projects.
yuga-hashimoto/and-code falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 49.6 out of 100 and is rated Weak, and all 38 of its critical findings are security problems in the build pipeline and in its code.
Production Readiness, at 31.8, is the weakest lens and counts most in the score. The best first steps are adding a diagnostic log and adding automated security scanning, each worth about 8.1 points. Raising Production Readiness to 70 would lift the score to about 64.0.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version and passing outside input through environment variables would close both risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 68,370 lines, about €100,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.
If Production Readiness rose from 31.8 to 70, the lowest score rated Strong, the score would rise from 49.6 to about 64.0.
Code composition: what the lines of code are
Product code 70%Tests 30%
Rebuild cost: about €100,000 · Estimate
Cost to rebuild
€35,000 to €170,000, for 576 to 1,827 hours of work, about 0.7 person-years for 1 to 2 engineers
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.7 at a score of 50. 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: 68,370 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
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 8.1 points · Medium effort · Observability
2
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
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 €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 31.8 (Weak). 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
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Of all the actions in this report, it raises the score most for the work it takes: about 8.1 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.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 48,263 lines over the last 90 days, which is about 195,733 lines a year. At that pace, the extra work comes to an estimated 9.8 to 65.2 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: 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.
234 modules, with 273 dependencies between them. 7 loops run through 39 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 194 more are left out to keep it readable.
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.
core.api.ProtocolDetectingOpenCodeApi.Probe uses core.api, so a change to core.api can break core.api.ProtocolDetectingOpenCodeApi.Probe, while a change to core.api.ProtocolDetectingOpenCodeApi.Probe can't break core.api.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 core.diagnostics uses core.apipart of a loop✕
Connections
2 pairs of types, where a type in core.diagnostics uses a type in core.api.
data.schedule.CronExpression uses data.schedule, so a change to data.schedule can break data.schedule.CronExpression, while a change to data.schedule.CronExpression can't break data.schedule.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→23 data.settings uses data.connectionpart of a loop✕
Connections
1 pair of types, where a type in data.settings uses a type in data.connection.
data.settings uses data.connection, so a change to data.connection can break data.settings, while a change to data.settings can't break data.connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
feature.chat.ChatPart uses feature.chat, so a change to feature.chat can break feature.chat.ChatPart, while a change to feature.chat.ChatPart can't break feature.chat.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→31 feature.schedule.ScheduleExecutionService uses feature.schedulepart of a loop✕
Connections
1 pair of types, where a type in feature.schedule.ScheduleExecutionService uses a type in feature.schedule.
feature.schedule.ScheduleExecutionService uses feature.schedule, so a change to feature.schedule can break feature.schedule.ScheduleExecutionService, while a change to feature.schedule.ScheduleExecutionService can't break feature.schedule.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→19 feature.terminal.AnsiTerminalEmulator uses feature.terminalpart of a loop✕
Connections
2 pairs of types, where a type in feature.terminal.AnsiTerminalEmulator uses a type in feature.terminal.
feature.terminal.AnsiTerminalEmulator uses feature.terminal, so a change to feature.terminal can break feature.terminal.AnsiTerminalEmulator, while a change to feature.terminal.AnsiTerminalEmulator can't break feature.terminal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
runtime.local.CodexRuntime uses runtime.local, so a change to runtime.local can break runtime.local.CodexRuntime, while a change to runtime.local.CodexRuntime can't break runtime.local.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→22 runtime.local.LocalRuntimeInstaller uses runtime.localpart of a loop✕
Connections
1 pair of types, where a type in runtime.local.LocalRuntimeInstaller uses a type in runtime.local.
runtime.local.LocalRuntimeInstaller uses runtime.local, so a change to runtime.local can break runtime.local.LocalRuntimeInstaller, while a change to runtime.local.LocalRuntimeInstaller can't break runtime.local.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
data.repository uses core.diagnostics, so a change to core.diagnostics can break data.repository, while a change to data.repository can't break core.diagnostics.
Position
Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
data.repository uses data.settings, so a change to data.settings can break data.repository, while a change to data.repository can't break data.settings.
Position
Below the diagonal: data.repository uses a module listed above it, which is the healthy direction.
data.schedule uses data.schedule.CronExpression, so a change to data.schedule.CronExpression can break data.schedule, while a change to data.schedule can't break data.schedule.CronExpression.
Position
Below the diagonal: data.schedule uses a module listed above it, which is the healthy direction.
feature.browser uses core.storage.DeviceStorage, so a change to core.storage.DeviceStorage can break feature.browser, while a change to feature.browser can't break core.storage.DeviceStorage.
Position
Below the diagonal: feature.browser uses a module listed above it, which is the healthy direction.
feature.chat.TimelineEntry uses feature.chat.ChatPart, so a change to feature.chat.ChatPart can break feature.chat.TimelineEntry, while a change to feature.chat.TimelineEntry can't break feature.chat.ChatPart.
Position
Below the diagonal: feature.chat.TimelineEntry uses a module listed above it, which is the healthy direction.
18→30 feature.chat.TimelineEntry uses feature.chatpart of a loop✕
Connections
10 pairs of types, where a type in feature.chat.TimelineEntry uses a type in feature.chat.
feature.chat.TimelineEntry uses feature.chat, so a change to feature.chat can break feature.chat.TimelineEntry, while a change to feature.chat.TimelineEntry can't break feature.chat.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
feature.terminal uses feature.terminal.AnsiTerminalEmulator, so a change to feature.terminal.AnsiTerminalEmulator can break feature.terminal, while a change to feature.terminal can't break feature.terminal.AnsiTerminalEmulator.
Position
Below the diagonal: feature.terminal uses a module listed above it, which is the healthy direction.
runtime.LocalRuntimeStatus uses runtime, so a change to runtime can break runtime.LocalRuntimeStatus, while a change to runtime.LocalRuntimeStatus can't break runtime.
Position
Below the diagonal: runtime.LocalRuntimeStatus uses a module listed above it, which is the healthy direction.
runtime.remote uses data.connection, so a change to data.connection can break runtime.remote, while a change to runtime.remote can't break data.connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
52 pairs of types, where a type in runtime.remote uses a type in core.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
runtime.local uses core.storage.DeviceStorage, so a change to core.storage.DeviceStorage can break runtime.local, while a change to runtime.local can't break core.storage.DeviceStorage.
Position
Below the diagonal: runtime.local uses a module listed above it, which is the healthy direction.
54 pairs of types, where a type in runtime.local uses a type in runtime. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
runtime.local uses runtime.local.CodexRuntime, so a change to runtime.local.CodexRuntime can break runtime.local, while a change to runtime.local can't break runtime.local.CodexRuntime.
Position
Below the diagonal: runtime.local uses a module listed above it, which is the healthy direction.
runtime.local uses runtime.local.LocalRuntimeInstaller, so a change to runtime.local.LocalRuntimeInstaller can break runtime.local, while a change to runtime.local can't break runtime.local.LocalRuntimeInstaller.
Position
Below the diagonal: runtime.local uses a module listed above it, which is the healthy direction.
runtime.local uses runtime.LocalRuntimeStatus, so a change to runtime.LocalRuntimeStatus can break runtime.local, while a change to runtime.local can't break runtime.LocalRuntimeStatus.
Position
Below the diagonal: runtime.local uses a module listed above it, which is the healthy direction.
runtime.local uses data.connection, so a change to data.connection can break runtime.local, while a change to runtime.local can't break data.connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
143 pairs of types, where a type in runtime.local uses a type in core.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
runtime.local uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break runtime.local, while a change to runtime.local can't break com.yugahashimoto.andcode.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
data.connection uses data.repository, so a change to data.repository can break data.connection, while a change to data.connection can't break data.repository.
Position
Below the diagonal: data.connection uses a module listed above it, which is the healthy direction.
data.connection uses runtime.local, so a change to runtime.local can break data.connection, while a change to data.connection can't break runtime.local.
Position
Below the diagonal: data.connection uses a module listed above it, which is the healthy direction.
ui.components uses runtime.LocalRuntimeStatus, so a change to runtime.LocalRuntimeStatus can break ui.components, while a change to ui.components can't break runtime.LocalRuntimeStatus.
Position
Below the diagonal: ui.components uses a module listed above it, which is the healthy direction.
feature.wakeword uses data.connection, so a change to data.connection can break feature.wakeword, while a change to feature.wakeword can't break data.connection.
Position
Below the diagonal: feature.wakeword uses a module listed above it, which is the healthy direction.
25→33 feature.wakeword uses com.yugahashimoto.andcodepart of a loop✕
Connections
1 pair of types, where a type in feature.wakeword uses a type in com.yugahashimoto.andcode.
feature.wakeword uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break feature.wakeword, while a change to feature.wakeword can't break com.yugahashimoto.andcode.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
feature.workspace uses core.runtime, so a change to core.runtime can break feature.workspace, while a change to feature.workspace can't break core.runtime.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
feature.workspace uses core.storage.DeviceStorage, so a change to core.storage.DeviceStorage can break feature.workspace, while a change to feature.workspace can't break core.storage.DeviceStorage.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
feature.workspace uses data.repository, so a change to data.repository can break feature.workspace, while a change to feature.workspace can't break data.repository.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
feature.workspace uses feature.terminal, so a change to feature.terminal can break feature.workspace, while a change to feature.workspace can't break feature.terminal.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
feature.workspace uses runtime.local, so a change to runtime.local can break feature.workspace, while a change to feature.workspace can't break runtime.local.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
feature.workspace uses data.connection, so a change to data.connection can break feature.workspace, while a change to feature.workspace can't break data.connection.
Position
Below the diagonal: feature.workspace uses a module listed above it, which is the healthy direction.
26→27 feature.workspace uses core.apipart of a loop✕
Connections
11 pairs of types, where a type in feature.workspace uses a type in core.api.
core.api uses core.api.ProtocolDetectingOpenCodeApi.Probe, so a change to core.api.ProtocolDetectingOpenCodeApi.Probe can break core.api, while a change to core.api can't break core.api.ProtocolDetectingOpenCodeApi.Probe.
Position
Below the diagonal: core.api uses a module listed above it, which is the healthy direction.
core.notification uses core.diagnostics, so a change to core.diagnostics can break core.notification, while a change to core.notification can't break core.diagnostics.
Position
Below the diagonal: core.notification uses a module listed above it, which is the healthy direction.
data.repository.RuntimeCatalogRepository uses runtime, so a change to runtime can break data.repository.RuntimeCatalogRepository, while a change to data.repository.RuntimeCatalogRepository can't break runtime.
Position
Below the diagonal: data.repository.RuntimeCatalogRepository uses a module listed above it, which is the healthy direction.
data.repository.RuntimeCatalogRepository uses data.repository, so a change to data.repository can break data.repository.RuntimeCatalogRepository, while a change to data.repository.RuntimeCatalogRepository can't break data.repository.
Position
Below the diagonal: data.repository.RuntimeCatalogRepository uses a module listed above it, which is the healthy direction.
data.repository.RuntimeCatalogRepository uses core.api, so a change to core.api can break data.repository.RuntimeCatalogRepository, while a change to data.repository.RuntimeCatalogRepository can't break core.api.
Position
Below the diagonal: data.repository.RuntimeCatalogRepository uses a module listed above it, which is the healthy direction.
feature.chat uses core.diagnostics, so a change to core.diagnostics can break feature.chat, while a change to feature.chat can't break core.diagnostics.
Position
Below the diagonal: feature.chat uses a module listed above it, which is the healthy direction.
feature.chat uses feature.chat.ChatPart, so a change to feature.chat.ChatPart can break feature.chat, while a change to feature.chat can't break feature.chat.ChatPart.
Position
Below the diagonal: feature.chat uses a module listed above it, which is the healthy direction.
feature.chat uses feature.chat.TimelineEntry, so a change to feature.chat.TimelineEntry can break feature.chat, while a change to feature.chat can't break feature.chat.TimelineEntry.
Position
Below the diagonal: feature.chat uses a module listed above it, which is the healthy direction.
feature.chat uses feature.workspace, so a change to feature.workspace can break feature.chat, while a change to feature.chat can't break feature.workspace.
Position
Below the diagonal: feature.chat uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in feature.chat uses a type in core.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
feature.schedule uses feature.schedule.ScheduleExecutionService, so a change to feature.schedule.ScheduleExecutionService can break feature.schedule, while a change to feature.schedule can't break feature.schedule.ScheduleExecutionService.
Position
Below the diagonal: feature.schedule uses a module listed above it, which is the healthy direction.
feature.schedule uses data.schedule, so a change to data.schedule can break feature.schedule, while a change to feature.schedule can't break data.schedule.
Position
Below the diagonal: feature.schedule uses a module listed above it, which is the healthy direction.
feature.schedule uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break feature.schedule, while a change to feature.schedule can't break com.yugahashimoto.andcode.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
feature.settings.SettingsViewModel uses data.settings, so a change to data.settings can break feature.settings.SettingsViewModel, while a change to feature.settings.SettingsViewModel can't break data.settings.
Position
Below the diagonal: feature.settings.SettingsViewModel uses a module listed above it, which is the healthy direction.
feature.settings.SettingsViewModel uses runtime, so a change to runtime can break feature.settings.SettingsViewModel, while a change to feature.settings.SettingsViewModel can't break runtime.
Position
Below the diagonal: feature.settings.SettingsViewModel uses a module listed above it, which is the healthy direction.
feature.settings.SettingsViewModel uses data.repository, so a change to data.repository can break feature.settings.SettingsViewModel, while a change to feature.settings.SettingsViewModel can't break data.repository.
Position
Below the diagonal: feature.settings.SettingsViewModel uses a module listed above it, which is the healthy direction.
feature.settings.SettingsViewModel uses core.api, so a change to core.api can break feature.settings.SettingsViewModel, while a change to feature.settings.SettingsViewModel can't break core.api.
Position
Below the diagonal: feature.settings.SettingsViewModel uses a module listed above it, which is the healthy direction.
32→36 feature.settings.SettingsViewModel uses feature.settingspart of a loop✕
Connections
3 pairs of types, where a type in feature.settings.SettingsViewModel uses a type in feature.settings.
feature.settings.SettingsViewModel uses feature.settings, so a change to feature.settings can break feature.settings.SettingsViewModel, while a change to feature.settings.SettingsViewModel can't break feature.settings.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
com.yugahashimoto.andcode uses core.lifecycle, so a change to core.lifecycle can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break core.lifecycle.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses core.runtime, so a change to core.runtime can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break core.runtime.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses data.settings, so a change to data.settings can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break data.settings.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses runtime, so a change to runtime can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break runtime.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses data.repository, so a change to data.repository can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break data.repository.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses data.schedule, so a change to data.schedule can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break data.schedule.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses runtime.local, so a change to runtime.local can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break runtime.local.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses data.connection, so a change to data.connection can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break data.connection.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses feature.wakeword, so a change to feature.wakeword can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break feature.wakeword.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses core.notification, so a change to core.notification can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break core.notification.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
com.yugahashimoto.andcode uses feature.schedule, so a change to feature.schedule can break com.yugahashimoto.andcode, while a change to com.yugahashimoto.andcode can't break feature.schedule.
Position
Below the diagonal: com.yugahashimoto.andcode uses a module listed above it, which is the healthy direction.
feature.assistant uses data.connection, so a change to data.connection can break feature.assistant, while a change to feature.assistant can't break data.connection.
Position
Below the diagonal: feature.assistant uses a module listed above it, which is the healthy direction.
feature.assistant uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break feature.assistant, while a change to feature.assistant can't break com.yugahashimoto.andcode.
Position
Below the diagonal: feature.assistant uses a module listed above it, which is the healthy direction.
startup.RuntimeAutoStartInitializer uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break startup.RuntimeAutoStartInitializer, while a change to startup.RuntimeAutoStartInitializer can't break com.yugahashimoto.andcode.
Position
Below the diagonal: startup.RuntimeAutoStartInitializer uses a module listed above it, which is the healthy direction.
35→37 startup.RuntimeAutoStartInitializer uses startuppart of a loop✕
Connections
1 pair of types, where a type in startup.RuntimeAutoStartInitializer uses a type in startup.
startup.RuntimeAutoStartInitializer uses startup, so a change to startup can break startup.RuntimeAutoStartInitializer, while a change to startup.RuntimeAutoStartInitializer can't break startup.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
feature.settings uses data.settings, so a change to data.settings can break feature.settings, while a change to feature.settings can't break data.settings.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses data.repository, so a change to data.repository can break feature.settings, while a change to feature.settings can't break data.repository.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses runtime.local, so a change to runtime.local can break feature.settings, while a change to feature.settings can't break runtime.local.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses data.connection, so a change to data.connection can break feature.settings, while a change to feature.settings can't break data.connection.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses feature.wakeword, so a change to feature.wakeword can break feature.settings, while a change to feature.settings can't break feature.wakeword.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses feature.settings.SettingsViewModel, so a change to feature.settings.SettingsViewModel can break feature.settings, while a change to feature.settings can't break feature.settings.SettingsViewModel.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
feature.settings uses feature.assistant, so a change to feature.assistant can break feature.settings, while a change to feature.settings can't break feature.assistant.
Position
Below the diagonal: feature.settings uses a module listed above it, which is the healthy direction.
startup uses startup.RuntimeAutoStartInitializer, so a change to startup.RuntimeAutoStartInitializer can break startup, while a change to startup can't break startup.RuntimeAutoStartInitializer.
Position
Below the diagonal: startup uses a module listed above it, which is the healthy direction.
feature.onboarding uses runtime.LocalRuntimeStatus, so a change to runtime.LocalRuntimeStatus can break feature.onboarding, while a change to feature.onboarding can't break runtime.LocalRuntimeStatus.
Position
Below the diagonal: feature.onboarding uses a module listed above it, which is the healthy direction.
feature.onboarding uses runtime.local, so a change to runtime.local can break feature.onboarding, while a change to feature.onboarding can't break runtime.local.
Position
Below the diagonal: feature.onboarding uses a module listed above it, which is the healthy direction.
feature.onboarding uses feature.settings, so a change to feature.settings can break feature.onboarding, while a change to feature.onboarding can't break feature.settings.
Position
Below the diagonal: feature.onboarding uses a module listed above it, which is the healthy direction.
ui.navigation uses feature.workspace, so a change to feature.workspace can break ui.navigation, while a change to ui.navigation can't break feature.workspace.
Position
Below the diagonal: ui.navigation uses a module listed above it, which is the healthy direction.
ui.navigation uses com.yugahashimoto.andcode, so a change to com.yugahashimoto.andcode can break ui.navigation, while a change to ui.navigation can't break com.yugahashimoto.andcode.
Position
Below the diagonal: ui.navigation uses a module listed above it, which is the healthy direction.
ui.navigation uses feature.settings, so a change to feature.settings can break ui.navigation, while a change to ui.navigation can't break feature.settings.
Position
Below the diagonal: ui.navigation uses a module listed above it, which is the healthy direction.
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
A05:2025 — Injection
39
High / Critical
A03:2025 — Software Supply Chain Failures
5
Medium
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
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.
Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
How the grades work
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 — 38
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 — 323
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 — 54
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 58 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 — 58 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, 407 of 415 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: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, 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 (.kt) and this repository declares a JVM test suite (repository root, Gradle), 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.
D12 Dependency Hygiene — 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. Not scored — a Gradle build resolved 360 artifact(s) across its subprojects (109 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 933 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 4 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — 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 ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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. `app/src/main/java/com/yugahashimoto/andcode/core/diagnostics/SessionStallDiagnosis.kt`, `app/src/main/java/com/yugahashimoto/andcode/data/local/MessageEntity.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/assistant/VoiceDictationPolicy.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt`, … (+10 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.
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's container is Koin, 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.
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. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: .107.97_aarch64.deb: Failed to download https://ftp.fau.de/termux/termux-main/pool/main/p/proot/proot_5.1.107.97_aarch64.deb: <urlopen error Tunnel connection failed: 403 Forbidden>
FAILURE: Build fa…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
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.
DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
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, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin, Python 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin, Python 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.
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.
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.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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").
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
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.
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.
26 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AndCodeAppKt.AndCodeApp at 85. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being OpenCodeV2EventTranslator.translateEvent at 34 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2EventTranslator.kt (OpenCodeV2EventTranslator.translateEvent at 34), app/src/main/java/com/yugahashimoto/andcode/feature/browser/StaticAssetInterceptor.kt (StaticAssetInterceptorKt.mimeTypeFor at 24), app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt (LocalRuntimeService.onStartCommand at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with AndCodeAppKt.AndCodeApp (cyclomatic 85), ChatHomeScreenKt.ChatHomeScreen (cyclomatic 66), ChatViewModel.handleEvent (cyclomatic 55). — 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 6 together lifts Cyclomatic Complexity from 6.2 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with AndCodeAppKt.AndCodeApp (cognitive 106), ChatHomeScreenKt.ChatHomeScreen (cognitive 80), ChatViewModel.handleEvent (cognitive 73). — 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 4 together lifts Cognitive Complexity from 6.0 to about 6.5/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.1 / 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 18 TooManyMethods finding(s) in God Classes — start with OpenCodeV2ApiClient.kt, ChatViewModel.kt, OpenCodeApiClient.kt. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 17 FileTooLong finding(s) in God Classes — start with ChatHomeScreen.kt, ChatViewModel.kt, AndCodeApp.kt. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 13 MethodTooLong finding(s) in God Classes — start with ChatViewModel.kt (3), SettingsNavGraph.kt, RemoteConnectionScreen.kt. — One of this dimension's main actionable groups (13 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.
76 duplicated block group(s) detected. 5.7 % of the production lines (3,863 of 68,370) are in a reported copy. A further 59 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 68 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AndroidSetupScreen.kt, ScheduleEditorScreen.kt, AgentSettingsScreen.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with LocalRuntimeInstaller.kt, CodeViewerViewModel.kt, OpenCodeApiClient.kt. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with ScheduleListScreen.kt (2), AndroidSetupScreen.kt, AgentSettingsScreen.kt. — 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 · Coupling10.0 / 10Exemplary✓ 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.
2 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence.
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.
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 14 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 17 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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.
Top hotspots: app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt (41×85=3485); app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt (34×66=2244); app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt (34×55=1870) Repeated repair below the complexity floor: app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt (9 of 14 changes were fixes); app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt (7 of 9 changes were fixes); app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt (7 of 8 changes were fixes)
Resolve the 25 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ClaudeCodeTarget.kt, ChatMessageComponents.kt, ClaudeCodeController.kt. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with AndCodeApp.kt, ChatHomeScreen.kt, ChatViewModel.kt. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d15_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 68370 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. 24 document(s) read across 1 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 build.gradle.kts. — 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 names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
7 naming inconsistencies among 554 declarations measured against a convention their peers follow.
`callID` spells `ID` where 733 names in the project spell it `Id`app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt:119
`projectID` spells `ID` where 733 names in the project spell it `Id`app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1530
`parentID` spells `ID` where 733 names in the project spell it `Id`app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1531
`providerID` spells `ID` where 733 names in the project spell it `Id`app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1550
`attemptID` spells `ID` where 733 names in the project spell it `Id`app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1612
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 `callID` spells `ID` where 733 names in the project spell it `Id` finding(s) in Naming Consistency — start with OpenCodeApiModels.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `projectID` spells `ID` where 733 names in the project spell it `Id` finding(s) in Naming Consistency — start with OpenCodeV2ApiClient.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `parentID` spells `ID` where 733 names in the project spell it `Id` finding(s) in Naming Consistency — start with OpenCodeV2ApiClient.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionapp/build.gradle.kts:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — 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.
12 % of calls cross a namespace and 9 % 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).
39 finding(s): 0 critical, 38 high, 1 medium, 0 low. 34 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) — `app/src/main/java/com/yugahashimoto/andcode/runtime/local/RuntimeArchive.kt` (line 111), `gradlew` (line 72, line 177) — 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 2 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
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 34 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 (34 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 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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 244 of the 337 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 3 Change coupling finding(s) in Change Coupling — start with LocalRuntimeTarget.kt, Routes.kt, AndCodeApplication.kt. — One of this dimension's main actionable groups (3 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.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 44 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
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.
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.
`.button` moves (`transition: transform 160ms ease, border-color 160ms ease, background 160ms ease, box-shadow 160ms ease`) 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. — pages/index.html:123
`.feature-card` moves (`transition: transform 180ms ease, border-color 180ms ease, background 180ms ease`) 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. — pages/index.html:217
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`OpenCodeApi` declares 50 abstract methods: `health`, `sessions`, `session`, `createSession`, `messages`, `deleteMessage`, `providers`, `agents`, `providerAuthMethods`, `authorizeProvider`, `setProviderApiKey`, `removeProviderAuth`, `completeProviderOAuth`, `projects`, `currentProject`, `pathInfo`, `files`, `fileContent`, `fileStatus`, `searchText`, `findFiles`, `vcsInfo`, `vcsStatus`, `vcsDiff`, `sessionDiff`, `sessionTodo`, `promptAsync`, `summarizeSession`, `abortSession`, `renameSession`, `deleteSession`, `archiveSession`, `mcpServers`, `addMcpServer`, `connectMcpServer`, `disconnectMcpServer`, `removeMcpAuth`, `mcpAuth`, `mcpAuthCallback`, `config`, and 10 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:15
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
Do you agree with this assessment?
DM10 · One transaction, one aggregate9.5 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
`VoskModelStore.install` saves `Downloading`, `VoskModelState` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/VoskModelStore.kt:57
What to do
Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
`MessageEntity`'s public constructor takes `id`, `sessionId`, `role`, `text` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MessageEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/yugahashimoto/andcode/data/local/MessageEntity.kt:20
`SessionEntity`'s public constructor takes `id`, `title`, `directory`, `providerId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `SessionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/yugahashimoto/andcode/data/local/SessionEntity.kt:7
What to do
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
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.
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.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 spotbugs with find-sec-bugs (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 8 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:6
`app/build.gradle.kts` 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`. — app/build.gradle.kts:254
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — 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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads 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 the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether suspend functions that make a cancellable request accept or pass on the coroutine's cancellation (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/18 suspend functions that make a cancellable request (Ktor, OkHttp newCall, URL streams) accept the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a screen navigated away from, a disposed widget, a superseded search. In a suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`latest` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:43
`fetch` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderModelFetcher.kt:26
`check` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:65
`download` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/VoskModelInstaller.kt:81
`pollToken` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:96
`refreshAccount` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:141
`listRepos` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:158
`executeJson` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:190
`getPullRequests` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. (×4) — app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:58, app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:159, app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:252, …
`getIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. (×3) — app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:89, app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:189, app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:278
`getPullRequest` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:66
`searchIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:91
`fileContent` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:341
What to do
Thread the coroutine's cancellation through suspend functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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 (_: Exception)` 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. (×2) — app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt:136, app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:86
`catch (_: Throwable)` 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. — app/src/main/java/com/yugahashimoto/andcode/core/api/ConnectionQualityMonitor.kt:103
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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 — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 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.
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 class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. 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.
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: .107.97_aarch64.deb: Failed to download https://ftp.fau.de/termux/termux-main/pool/main/p/proot/proot_5.1.107.97_aarch64.deb: <urlopen error Tunnel connection failed: 403 Forbidden>
FAILURE: Build fa…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
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.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, 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 field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~28800 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
D12 Dependency Hygiene — Not scored — a Gradle build resolved 360 artifact(s) across its subprojects (109 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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) — 15 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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 included — suite not readable by the collector
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
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, Scala, Rust and Java, 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 JVM, Python 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
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.
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.
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
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
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
X20 Mistyped argument 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
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
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 Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt:361— app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt changed 14 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ClaudeCodeTarget.sendMessage at line 361), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: stop local-runtime ANRs and a Keystore-corruption crash loop”; “fix(system-prompt): never record a preset that has been deleted”; “fix(system-prompt): move a blank chat's preset onto the chat that chose it”; “fix(system-prompt): stage a new chat's preset instead of moving the default”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt:396— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ChatMessageComponentsKt.MarkdownText at line 396), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): read an image data URL's type from its header, not by copying it”; “fix(chat): linkify urls inside bold/italic/strikethrough”; “fix(chat): resolve text direction from content for RTL/LTR mixed input”; “fix(chat): explain OpenCode Zen free-tier client gate (#343)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt:148— app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is ClaudeCodeController.install at line 148), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(system-prompt): move a blank chat's preset onto the chat that chose it”; “fix(system-prompt): keep a staged preset to the chat it was chosen in”; “fix(system-prompt): stage a new chat's preset instead of moving the default”; “fix(system-prompt): move the chip on the tap, not on the next recompose”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/AndCodeAgentContext.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/AndCodeAgentContext.kt:88— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AndCodeAgentContext.kt changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is AndCodeAgentContextKt.installAndCodeAgentContext at line 88), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(runtime): bound and guard the remaining agent-context file I/O”; “fix(runtime): make agent-context install fully best-effort per path”; “fix(runtime): keep installing agent context when a guarded path is unusable”; “fix(runtime): reject symlinked agent-context paths, including dangling ones”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/AndCodeAgentContext.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceViewModel.kt:202— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceViewModel.kt changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is WorkspaceViewModel.deleteProjectFiles at line 202), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(system-prompt): move a blank chat's preset onto the chat that chose it”; “fix(system-prompt): keep a staged preset to the chat it was chosen in”; “fix(system-prompt): stage a new chat's preset instead of moving the default”; “fix(system-prompt): move the chip on the tap, not on the next recompose”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceViewModel.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/SystemPromptStore.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/SystemPromptStore.kt:155— app/src/main/java/com/yugahashimoto/andcode/runtime/local/SystemPromptStore.kt changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is SystemPromptStore.delete at line 155), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(system-prompt): stop a write from being able to lose the user's presets”; “fix(system-prompt): strip what exec will not carry from a pasted preset”; “fix(system-prompt): stage a new chat's preset instead of moving the default”; “fix(system-prompt): cap a preset at what exec will carry”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/SystemPromptStore.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt:502— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is SettingsViewModel.beginProviderOAuth at line 502), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): show the agent chip loading instead of ignoring taps”; “fix(providers): rethrow cancellation in custom provider submit too”; “fix(providers): address review on custom provider model fetch”; “fix(providers): keep model selection and connect DeepSeek from picker”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt:450— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is OpenCodeApiModelsKt.sessionIdOrNull at line 450), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): say why a run is waiting when the provider keeps failing”; “fix(opencode): decode agents whose hidden flag is null”; “fix(chat): copy unsupported attachments into the workspace”; “fix(api): archive OpenCode sessions through time.archived, filter them from lists”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt:626— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is LocalRuntimeService.notification at line 626), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(runtime): stop the main thread and startForeground waiting on local-runtime work”; “fix(runtime): make full development tools optional and resumable”; “fix(runtime): restore the onboarding sync ordering and harden the idle stop”; “fix(runtime): make the boot suppression real and refresh the proot notices”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt:438— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is AntigravityRuntime.summarizeTitle at line 438), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(terminal): end the shell's whole process tree and harden the output parser”; “fix(antigravity): stream chat history to disk to avoid OOM”; “fix(chat): copy unsupported attachments into the workspace”; “fix(chat): keep LazyColumn keys unique when a transcript repeats a user message id”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:69— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is ModelAndRuntimePickerSheetKt.ModelAndRuntimePickerSheet at line 69), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): make the favorite star work in the voice assistant model picker”; “fix(chat): persist composer drafts, stream chat history to disk, add android-build-setup”; “fix(providers): keep model selection and connect DeepSeek from picker”; “fix(chat): surface reasoning-effort variants in the model picker”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/browser/GuestBrowserScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/browser/GuestBrowserScreen.kt:45— app/src/main/java/com/yugahashimoto/andcode/feature/browser/GuestBrowserScreen.kt changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is GuestBrowserScreenKt.GuestBrowserScreen at line 45), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(browser): guard only the provider start, and handle linkage failures”; “fix(browser): explain instead of crashing when the system WebView cannot start”; “fix(browser): restore guest commands and visible address bar (#372)”; “fix(chat): persist composer drafts, stream chat history to disk, add android-build-setup”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/browser/GuestBrowserScreen.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalViewModel.kt:151— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalViewModel.kt changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is TerminalViewModel.run at line 151), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(terminal): find addresses across wrapped rows and keep slots for real servers”; “fix(terminal): apply the re-review's cheap suggestions”; “fix(terminal): end the shell's whole process tree and harden the output parser”; “fix(runtime): cover the work paths the wake lock rework missed”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalViewModel.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt:118— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is AntigravityController.rehydrate at line 118), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(runtime): make full development tools optional and resumable”; “fix(runtime): make the boot suppression real and refresh the proot notices”; “fix(runtime): cover the work paths the wake lock rework missed”; “fix(antigravity): refresh the model catalog after an install or update”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:461— app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is AssistantActivityRowKt.TodoTimelineCard at line 461), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): resolve text direction from content for RTL/LTR mixed input”; “fix(chat): show thinking content instead of empty reasoning cards”; “fix(antigravity): unblock tool calls; fix(theme): make the light theme readable (#283)”; “fix(chat): wire auto-expand reasoning setting to the activity sheet”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/OpenCodeSystemPrompt.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/OpenCodeSystemPrompt.kt:53— app/src/main/java/com/yugahashimoto/andcode/runtime/local/OpenCodeSystemPrompt.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is OpenCodeSystemPromptKt.applyOpenCodeSystemPrompt at line 53), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(opencode): stage the prompt under a unique name”; “fix(opencode): replace an existing instructions file on the rename”; “fix(opencode): stage and rename the instructions file instead of truncating”; “fix(opencode): open the instructions write no-follow”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/OpenCodeSystemPrompt.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt:499— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is ScheduleExecutionService.watchForCompletion at line 499), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(schedule): allow independent schedules to run concurrently (#296)”; “fix(schedule): retry runs that fail to start, and never miss one in silence (#265)”; “fix(schedule): stop losing runs to a dropped event stream”; “fix(chat): retain streamed bubbles on reconnect reloads; suppress abort errors in voice, schedule and add direct merge tests”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/settings/SystemPromptScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/SystemPromptScreen.kt:215— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SystemPromptScreen.kt changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is SystemPromptScreenKt.SystemPromptEditDialog at line 215), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): persist composer drafts, stream chat history to disk, add android-build-setup”; “fix(system-prompt): strip what exec will not carry from a pasted preset”; “fix(system-prompt): cap a preset at what exec will carry”; “fix(system-prompt): show the open chat's preset, and translate the built-in names”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/settings/SystemPromptScreen.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalOpenCodeBackend.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalOpenCodeBackend.kt:63— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalOpenCodeBackend.kt changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is LocalOpenCodeBackend.delegate at line 63), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(runtime): stop the main thread and startForeground waiting on local-runtime work”; “fix(opencode): confirm V1 servers with the profile's username”; “fix(security): authenticate the on-device OpenCode server”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalOpenCodeBackend.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt:151— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is TerminalScreenKt.TerminalToolbar at line 151), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(terminal): find addresses across wrapped rows and keep slots for real servers”; “fix(terminal): apply the re-review's cheap suggestions”; “fix(terminal): end the shell's whole process tree and harden the output parser”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:165— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is AntigravityTarget.sendMessage at line 165), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(antigravity): stream chat history to disk to avoid OOM”; “fix: stop local-runtime ANRs and a Keystore-corruption crash loop”; “fix(runtime): implement session archive for Claude Code and Antigravity targets”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatPreviewCard.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatPreviewCard.kt:67— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatPreviewCard.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ChatPreviewCardKt.ChatPreviewCard at line 67), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(browser): polish inline preview lifecycle, insets, and handoff scope”; “fix(chat): place the restore button above the composer with higher contrast”; “fix(chat): restore the inline preview chip and format the watcher”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatPreviewCard.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatImageViewer.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatImageViewer.kt:267— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatImageViewer.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ChatImageViewerKt.effectiveImageMime at line 267), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): read an image data URL's type from its header, not by copying it”; “fix(chat): harden clipboard image paste after review”; “fix: downsample attachment preview bitmaps to stop image-attach OOM”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatImageViewer.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:742— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is OpenCodeV2ApiClient.singleEventStream at line 742), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(opencode): decode agents whose hidden flag is null”; “fix(opencode): keep proxied V1 servers reachable and gate V2 MCP OAuth”; “fix(opencode): keep the V2 agent mapping independent of hidden agents”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt`: 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.
Repeated repair: app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityGroup.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityGroup.kt:90— app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityGroup.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is AssistantActivityGroupKt.groupConversationTimeline at line 90), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(chat): keep LazyColumn keys unique when a transcript repeats a user message id”; “fix(chat): show thinking content instead of empty reasoning cards”; “fix(chat): disambiguate reused todowrite ids in the timeline”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityGroup.kt`: 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.
TooManyMethods: OpenCodeV2ApiClient app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:56— TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: ChatViewModel app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:588— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× 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: OpenCodeApiClient app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:38— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. Most of these members implement api.OpenCodeApi (50 of 65 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: SettingsViewModel app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt:110— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× 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: ProtocolDetectingOpenCodeApi app/src/main/java/com/yugahashimoto/andcode/core/api/ProtocolDetectingOpenCodeApi.kt:38— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. Most of these members implement api.OpenCodeApi (50 of 61 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: LocalRuntimeTarget app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:44— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. Most of these members implement runtime.OpenCodeBackend (52 of 60 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: LocalOpenCodeBackend app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalOpenCodeBackend.kt:43— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. Most of these members implement runtime.OpenCodeBackend (50 of 54 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: RemoteRuntimeTarget app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt:38— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. Most of these members implement runtime.OpenCodeBackend (50 of 54 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: ClaudeCodeTarget app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt:63— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: RemoteOpenCodeBackend app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteOpenCodeBackend.kt:39— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. Most of these members implement runtime.OpenCodeBackend (50 of 51 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: AppPreferencesRepository app/src/main/java/com/yugahashimoto/andcode/data/settings/AppPreferencesRepository.kt:63— 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: CodexRuntime app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexRuntime.kt:54— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: ClaudeCodeRuntime app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeRuntime.kt:43— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: WorkspaceViewModel app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceViewModel.kt:86— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: CodexTarget app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexTarget.kt:48— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: LocalRuntimeUpdater app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeUpdater.kt:39— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: AntigravityTarget app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:19— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: LocalRuntimeManager app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeManager.kt:49— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× 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.
X2 · Cancellation propagation· Suspend function with a blocking request · ×18
Suspend function with a blocking request: latest app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:43— `latest` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: fetch app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderModelFetcher.kt:26— `fetch` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: check app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:65— `check` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: download app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/VoskModelInstaller.kt:81— `download` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: pollToken app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:96— `pollToken` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: refreshAccount app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:141— `refreshAccount` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: listRepos app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:158— `listRepos` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: executeJson app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:190— `executeJson` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getPullRequests app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:58— `getPullRequests` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getIssues app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:89— `getIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getPullRequests app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:159— `getPullRequests` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getIssues app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:189— `getIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getPullRequests app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:252— `getPullRequests` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getIssues app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:278— `getIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getPullRequests app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:30— `getPullRequests` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: getPullRequest app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:66— `getPullRequest` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: searchIssues app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:91— `searchIssues` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: fileContent app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:341— `fileContent` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
FileTooLong: chat/ChatHomeScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt— FileTooLong — 1865 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1365 over it, 3.73× 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: chat/ChatViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt— FileTooLong — 1690 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: ChatViewModel (588-2812). The bar is 500 significant lines; this is 1190 over it, 3.38× 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: ui/AndCodeApp.kt app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt— FileTooLong — 1342 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 842 over it, 2.68× 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: api/OpenCodeV2ApiClient.kt app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt— FileTooLong — 1143 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: OpenCodeV2ApiClient (56-1127). The bar is 500 significant lines; this is 643 over it, 2.29× 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: onboarding/AndroidSetupScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt— FileTooLong — 1049 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 549 over it, 2.10× 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/VoiceSettingsScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/VoiceSettingsScreen.kt— FileTooLong — 819 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 319 over it, 1.64× 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: workspace/WorkspaceExplorerScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× 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/SettingsScreenV2.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt— FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 170 over it, 1.34× 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/SettingsViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt— FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: SettingsViewModel (110-936). The bar is 500 significant lines; this is 147 over it, 1.29× 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: workspace/WorkspacesScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt— FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 147 over it, 1.29× 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: schedule/ScheduleEditorScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: class (85-628). 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: chat/ChatMessageComponents.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatMessageComponents.kt— FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 108 over it, 1.22× 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: api/OpenCodeApiClient.kt app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: OpenCodeApiClient (38-798). The bar is 500 significant lines; this is 70 over it, 1.14× 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: ui/AppDrawerContent.kt app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× 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: local/LocalRuntimeInstaller.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt— FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: LocalRuntimeInstaller (16-744). The bar is 500 significant lines; this is 40 over it, 1.08× 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: local/ClaudeCodeRuntime.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeRuntime.kt— FileTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ClaudeCodeRuntime (43-826). The bar is 500 significant lines; this is 25 over it, 1.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: settings/AgentSettingsScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9 over it, 1.02× 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.
MethodTooLong: SettingsNavGraphKt.settingsNavGraph app/src/main/java/com/yugahashimoto/andcode/ui/navigation/SettingsNavGraph.kt:41— MethodTooLong — settingsNavGraph runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.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.
MethodTooLong: RemoteConnectionScreenKt.RemoteConnectionScreen app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:84— MethodTooLong — RemoteConnectionScreen runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× 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: AndCodeApplication.onCreate app/src/main/java/com/yugahashimoto/andcode/AndCodeApplication.kt:243— MethodTooLong — onCreate runs 254 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 154 over it, 2.54× 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: WorkspaceNavGraphKt.workspaceNavGraph app/src/main/java/com/yugahashimoto/andcode/ui/navigation/WorkspaceNavGraph.kt:31— MethodTooLong — workspaceNavGraph runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× 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: ChatViewModel.sendMessage app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1414— MethodTooLong — sendMessage 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: OpenCodeV2EventTranslator.translateEvent app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2EventTranslator.kt:42— MethodTooLong — translateEvent runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: ChatViewModel.handleEvent app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2304— MethodTooLong — handleEvent runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: ProviderSettingsScreenKt.ProviderSettingsScreen app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:53— MethodTooLong — ProviderSettingsScreen runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: ChatViewModel.sendSlashCommand app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1677— MethodTooLong — sendSlashCommand 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: WakeWordService.startListening app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/WakeWordService.kt:227— MethodTooLong — startListening runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.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: ProviderAuthDialogKt.ProviderAuthDialog app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt:32— MethodTooLong — ProviderAuthDialog 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: VerifiedRuntimeDownloader.downloadLocked app/src/main/java/com/yugahashimoto/andcode/runtime/local/VerifiedRuntimeDownloader.kt:38— MethodTooLong — downloadLocked runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: CustomProviderDialogKt.CustomProviderDialog app/src/main/java/com/yugahashimoto/andcode/feature/settings/CustomProviderDialog.kt:30— MethodTooLong — CustomProviderDialog 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.
Hotspot: app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:182— app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt changed 41 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in AndCodeAppKt.AndCodeApp at line 182. 26 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:187— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in ChatHomeScreenKt.ChatHomeScreen at line 187. 21 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2304— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in ChatViewModel.handleEvent at line 2304. 26 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:99— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in AndroidSetupScreenKt.AndroidSetupScreen at line 99. 4 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt:489— app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in RuntimeActivityRepository.handle at line 489. 3 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt:176— app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RuntimeCatalogRepository.load at line 176. 8 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt:95— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in CodeViewerScreenKt.CodeViewerScreen at line 95. 3 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:89— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ScheduleEditorScreenKt.ScheduleEditorScreen at line 89. 3 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:841— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in WorkspacesScreenKt.targetSubtitle at line 841. 1 of those changes was a fix/bug commit, 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt`: 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: app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt:32— app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ProviderAuthDialogKt.ProviderAuthDialog at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 00:08:30 +09:00' --until='2026-11-16 00:08:30 +09:00' --full-history --no-merges -- app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt`: 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.
ClassTooLong: ChatViewModel app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:588— ClassTooLong — 1271 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 871 over it, 3.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: OpenCodeV2ApiClient app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:56— ClassTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded), 80 methods. The bar is 400 significant lines; this is 297 over it, 1.74× 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: SettingsViewModel app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt:110— ClassTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 147 over it, 1.37× 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: OpenCodeApiClient app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:38— ClassTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 135 over it, 1.34× 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: LocalRuntimeInstaller app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:16— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 127 over it, 1.32× 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: ClaudeCodeRuntime app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeRuntime.kt:43— ClassTooLong — 493 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 93 over it, 1.23× 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: LocalRuntimeManager app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeManager.kt:49— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 40 over it, 1.10× 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: SecureSettingsRepository app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:13— ClassTooLong — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 25 over it, 1.06× 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.
Duplicated block (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:883— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:883-891 | app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1230-1238 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:883` 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 (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:250— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:250-258 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/VoiceSettingsScreen.kt:726-734 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:250` 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 (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:189— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:189-197 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:240-248 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:189` 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 (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:109— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:109-117 | app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt:70-78 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt` and `app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:109` 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 (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1822— app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1822-1830 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:373-381 — 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 `app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1822` 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 (9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:163— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:163-171 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:193-201 — 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 `app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:163` 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 (9 lines × 2) runtime_tools/termux_assets.py:80— runtime_tools/termux_assets.py:80-88 | runtime_tools/termux_assets.py:97-105 — 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.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×5
Edited copy of a member (17 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:564— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:564-580 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:602-618 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerViewModel.kt:121— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerViewModel.kt:121-137 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerViewModel.kt:152-168 — 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) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:730— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:730-746 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1047-1064 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt:209— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt:209-225 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt:227-243 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:290— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:290-306 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:307-323 — 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.
Duplicated block (16 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1151— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1151-1166 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:103-118 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt` and `app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:92— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:92-107 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:135-150 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:92` 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 (16 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:179— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:179-194 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SystemPromptScreen.kt:148-163 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleListScreen.kt:179` 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 (16 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:665— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:665-680 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:83-98 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:665` 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 (16 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeSandboxLauncher.kt:60— app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeSandboxLauncher.kt:60-75 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexSandboxLauncher.kt:23-38 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeSandboxLauncher.kt:60` 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:133— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:133-149 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt:344-355 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:205— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:205-218 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeAuthCoordinator.kt:116-127 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexInstaller.kt:110— app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexInstaller.kt:110-123 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/RuntimeArchive.kt:34-45 — 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) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:686— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:686-702 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1008-1019 — 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.
Duplicated block (14 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:236— app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:236-249 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:467-480 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:236` 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 × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatDiffDialog.kt:74— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatDiffDialog.kt:74-87 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:586-599 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatDiffDialog.kt:74` 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 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:340— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:340-353 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:215-228 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:340` 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 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 (14 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:877— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:877-890 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:891-904 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:170— app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:170-182 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ServerInfoScreen.kt:144-156 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:170` 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 (13 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:495— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:495-507 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:601-613 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:495` 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:368— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:368-380 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:551-563 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:368` 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 (13 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:386— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:386-398 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt:124-136 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:386` 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) app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:257— app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:257-268 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:489-500 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:257` 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 (12 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2179— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2179-2190 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2249-2260 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2179` 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 (12 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:81— app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:81-92 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ServerInfoScreen.kt:87-98 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpScreen.kt:81` 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 (12 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudePermissionBridge.kt:146— app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudePermissionBridge.kt:146-157 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudePermissionBridge.kt:233-244 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudePermissionBridge.kt:146` 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 (10 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952-961 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2233-2242 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952` 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 × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:765— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:765-774 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:809-818 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:765` 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, `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:764` calls `clickable` and `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:808` does not — after which the two agree again for 4 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 (10 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:28— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:28-37 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:62-71 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:28` 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 (10 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:49— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:49-58 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:75-84 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:49` 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 before the matched lines, `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:74` calls `normalizeRuntimeVersion` and `app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:48` does not — after which the two agree again for 4 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.
Change coupling: LocalRuntimeTarget.kt ↔ RemoteRuntimeTarget.kt app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:1— `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt` and `app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt` change together 92% of the time (12 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `48259771` fix(opencode): keep proxied V1 servers reachable and gate V2 MCP OAuth; `6daa976f` feat: browse the whole sandbox filesystem and show diffs on changed f…; `9c9f6052` feat(chat): add "Edit & resend" for the last sent message — run `git show` on any of them.
Change coupling: Routes.kt ↔ SettingsNavGraph.kt app/src/main/java/com/yugahashimoto/andcode/ui/navigation/Routes.kt:1— `app/src/main/java/com/yugahashimoto/andcode/ui/navigation/Routes.kt` and `app/src/main/java/com/yugahashimoto/andcode/ui/navigation/SettingsNavGraph.kt` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a9a2b0f1` feat(codex): add MCP servers and apply pre-PR review fixes; `dd09a199` feat(opencode): carry the system prompt preset into OpenCode too; `54f41984` feat(claude-code): add system prompt presets and clearer thinking-lev… — run `git show` on any of them.
Change coupling: AndCodeApplication.kt ↔ Routes.kt app/src/main/java/com/yugahashimoto/andcode/AndCodeApplication.kt:1— `app/src/main/java/com/yugahashimoto/andcode/AndCodeApplication.kt` and `app/src/main/java/com/yugahashimoto/andcode/ui/navigation/Routes.kt` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e4b236f8` feat(terminal): run an interactive PTY shell in the embedded terminal; `a9a2b0f1` feat(codex): add MCP servers and apply pre-PR review fixes; `dd09a199` feat(opencode): carry the system prompt preset into OpenCode too — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleRepository.kt:180— app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleRepository.kt:180-189 | app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleRepository.kt:191-200 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndCodeVoiceSession.kt:486— app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndCodeVoiceSession.kt:486-495 | app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:154-163 — These two members are one piece of code written twice and then edited apart: 10 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 (10 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/CodexSignInViewModel.kt:69— app/src/main/java/com/yugahashimoto/andcode/feature/settings/CodexSignInViewModel.kt:69-81 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt:467-476 — These two members are one piece of code written twice and then edited apart: 10 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 (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravitySandboxLauncher.kt:67— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravitySandboxLauncher.kt:67-78 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexSandboxLauncher.kt:63-71 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:121— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:121-130 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:247-255 — 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) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:121— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:121-129 | app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:123-131 — 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 (3 corresponding lines) · ×3
Edited copy of a member (3 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:605— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:605-607 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:928-932 — 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.
Edited copy of a member (3 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:756— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:756-758 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1074-1076 — 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.
Edited copy of a member (3 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexKeepAliveService.kt:52— app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexKeepAliveService.kt:52-54 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeService.kt:462-464 — 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.
Duplicated block (22 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:426— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:426-447 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:573-594 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:426` 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 (22 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:231— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:231-252 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:244-265 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:231` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `selected` to `AntigravityPermissionMode` in one and `ClaudePermissionMode` 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 (22 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderStore.kt:123— app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderStore.kt:123-144 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalProviderCredentialStore.kt:115-136 — 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 (18 lines × 2) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:557— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:557-574 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:756-773 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt` and `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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 `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:557` 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 before the matched lines, `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:755` calls `OpenCodeV2EventTranslator` and `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:556` does not — after which the two agree again for 4 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 (18 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1386— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1386-1403 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:375-392 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt` and `app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1386` 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 (18 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:140— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:140-157 | app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt:101-118 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt` and `app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (17 lines × 2) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:709— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:709-725 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1026-1042 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt` and `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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. 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 (17 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:499— app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:499-515 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1042-1058 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:499` 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 (17 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1652— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1652-1668 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1835-1851 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1652` 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 (15 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2316— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2316-2330 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2787-2801 — 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 (15 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:199— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:199-213 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:250-264 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:199` 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:426— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:426-440 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:469-483 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:426` 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 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:100— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:100-104 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:312-318 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:100` 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, `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:311` calls `RoundedCornerShape` and `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:99` 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 (5 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:196— app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:196-200 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt:311-315 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt:46— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt:46-50 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt:51-55 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:834— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:834-839 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/VoiceSettingsScreen.kt:1081-1086 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:130— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:130-135 | app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt:91-96 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt` and `app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (6 lines × 2) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:256— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:256-261 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:282-287 — 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 `app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:256` 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 (8 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:65— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:65-72 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:91-98 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:65` 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 (8 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:223— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:223-230 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:246-253 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:223` 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 (8 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexInstaller.kt:113— app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexInstaller.kt:113-120 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/RuntimeArchive.kt:36-43 — 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.
Swallowed exception (caught, then discarded) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt:136— `catch (_: Exception)` 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) app/src/main/java/com/yugahashimoto/andcode/core/api/ConnectionQualityMonitor.kt:103— `catch (_: Throwable)` 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) app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:86— `catch (_: Exception)` 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×2
Animation without a prefers-reduced-motion guard pages/index.html:123— `.button` moves (`transition: transform 160ms ease, border-color 160ms ease, background 160ms ease, box-shadow 160ms ease`) 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.
Animation without a prefers-reduced-motion guard pages/index.html:217— `.feature-card` moves (`transition: transform 180ms ease, border-color 180ms ease, background 180ms ease`) 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.
D4 · Code Duplication· Edited copy of a member (55 corresponding lines) · ×2
Edited copy of a member (55 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:545— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:545-599 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:743-804 — These two members are one piece of code written twice and then edited apart: 55 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 (55 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1856— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1856-1910 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1986-2045 — These two members are one piece of code written twice and then edited apart: 55 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) · ×2
Edited copy of a member (41 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:431— app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:431-471 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:479-530 — 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.
Edited copy of a member (41 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1926— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1926-1970 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2282-2322 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpViewModel.kt:136— app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpViewModel.kt:136-159 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/McpViewModel.kt:165-196 — 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.
Edited copy of a member (24 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:401— app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:401-424 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:563-594 — 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 copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:194— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:194-213 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:200-218 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:731— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:731-750 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:671-689 — 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 (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:142— app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:142-156 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:159-171 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt:272— app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt:272-286 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatImageViewer.kt:325-337 — 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 (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt:581— app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt:581-598 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexKeepAliveService.kt:63-78 — 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.
Edited copy of a member (16 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AdbConnectionManager.kt:157— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AdbConnectionManager.kt:157-172 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/AdbConnectionManager.kt:175-191 — 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 copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:583— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:583-596 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:621-634 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt:203— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/TerminalScreen.kt:203-216 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:199-216 — 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 (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/CodexSignInViewModel.kt:49— app/src/main/java/com/yugahashimoto/andcode/feature/settings/CodexSignInViewModel.kt:49-63 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsViewModel.kt:426-441 — 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.
Edited copy of a member (15 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:845— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:845-859 | app/src/main/java/com/yugahashimoto/andcode/ui/components/AndCodeComponents.kt:85-100 — 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 copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:209— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:209-212 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt:675-678 — 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) app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeMessages.kt:61— app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeMessages.kt:61-64 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexMessages.kt:63-66 — 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.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:287— app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:287-291 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeManager.kt:640-646 — 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:186— app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:186-190 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt:277-285 — 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 (20 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1168— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1168-1187 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:129-148 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt` and `app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1168` 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 before the matched lines, `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1165` calls `RoundedCornerShape` and `app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt:127` 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 (20 lines × 2) app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:432— app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:432-451 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:480-499 — 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 `app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:432` 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 (7–8 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:271— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:271-277 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ModelVisibilityScreen.kt:93-100 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:271` 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–8 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:69— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:69-75 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:272-279 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:69` 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 (11 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1944— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1944-1954 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2300-2310 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1944` 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 (11 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:839— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:839-849 | app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:944-954 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:839` 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.
DM11 · Constructible invalid state· Constructible in an invalid state · ×2
Constructible in an invalid state: MessageEntity app/src/main/java/com/yugahashimoto/andcode/data/local/MessageEntity.kt:20— `MessageEntity`'s public constructor takes `id`, `sessionId`, `role`, `text` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `MessageEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: SessionEntity app/src/main/java/com/yugahashimoto/andcode/data/local/SessionEntity.kt:7— `SessionEntity`'s public constructor takes `id`, `title`, `directory`, `providerId`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `SessionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
AndCodeAppKt.AndCodeApp (cyclomatic 85) app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:182— AndCodeAppKt.AndCodeApp has cyclomatic complexity 85 (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.
ChatHomeScreenKt.ChatHomeScreen (cyclomatic 66) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:187— ChatHomeScreenKt.ChatHomeScreen has cyclomatic complexity 66 (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.
ChatViewModel.handleEvent (cyclomatic 55) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2304— ChatViewModel.handleEvent has cyclomatic complexity 55 (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.
AndroidSetupScreenKt.AndroidSetupScreen (cyclomatic 51) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:99— AndroidSetupScreenKt.AndroidSetupScreen has cyclomatic complexity 51 (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.
ChatViewModel.sendMessage (cyclomatic 33) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1414— ChatViewModel.sendMessage has cyclomatic complexity 33 (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.
ChatHomeScreenKt.ChatComposer (cyclomatic 31) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1370— ChatHomeScreenKt.ChatComposer 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.
VerifiedRuntimeDownloader.downloadLocked (cyclomatic 29) app/src/main/java/com/yugahashimoto/andcode/runtime/local/VerifiedRuntimeDownloader.kt:38— VerifiedRuntimeDownloader.downloadLocked 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.
ChatViewModel.sendSlashCommand (cyclomatic 27) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1677— ChatViewModel.sendSlashCommand has cyclomatic complexity 27 (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.
RuntimeActivityRepository.handle (cyclomatic 26) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt:489— RuntimeActivityRepository.handle has cyclomatic complexity 26 (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.
AndCodeVoiceSession.startEventCollection (cyclomatic 26) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndCodeVoiceSession.kt:222— AndCodeVoiceSession.startEventCollection has cyclomatic complexity 26 (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.
MarkdownLite.parse (cyclomatic 26) app/src/main/java/com/yugahashimoto/andcode/feature/chat/MarkdownLite.kt:65— MarkdownLite.parse has cyclomatic complexity 26 (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.
ScheduleEditorScreenKt.ScheduleEditorScreen (cyclomatic 25) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:89— ScheduleEditorScreenKt.ScheduleEditorScreen 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.
CodeViewerScreenKt.CodeViewerScreen (cyclomatic 24) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt:95— CodeViewerScreenKt.CodeViewerScreen 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.
WakeWordService.startListening (cyclomatic 22) app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/WakeWordService.kt:227— WakeWordService.startListening has cyclomatic complexity 22 (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.
AnsiTerminalEmulator.sgr (cyclomatic 21) app/src/main/java/com/yugahashimoto/andcode/feature/terminal/AnsiTerminalEmulator.kt:311— AnsiTerminalEmulator.sgr has cyclomatic complexity 21 (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. This is NOT this file's highest cyclomatic complexity: AnsiTerminalEmulator.dispatchCsi (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
OpenCodeUrl.isTrustedCleartextHost (cyclomatic 19) app/src/main/java/com/yugahashimoto/andcode/core/security/OpenCodeUrl.kt:41— OpenCodeUrl.isTrustedCleartextHost 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.
WorkspacesScreenKt.WorkspacesScreen (cyclomatic 19) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:90— WorkspacesScreenKt.WorkspacesScreen has cyclomatic complexity 19 (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.
WorkspacesScreenKt.targetSubtitle (cyclomatic 19) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:841— WorkspacesScreenKt.targetSubtitle 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.
GitHubStarCoordinator.refresh (cyclomatic 18) app/src/main/java/com/yugahashimoto/andcode/feature/support/GitHubStarSupport.kt:182— GitHubStarCoordinator.refresh 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.
RuntimeArchive.extractTar (cyclomatic 18) app/src/main/java/com/yugahashimoto/andcode/runtime/local/RuntimeArchive.kt:66— RuntimeArchive.extractTar has cyclomatic complexity 18 (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.
RuntimeCatalogRepository.load (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt:176— RuntimeCatalogRepository.load 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.
AndroidTTSProvider.speak (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndroidTTSProvider.kt:64— AndroidTTSProvider.speak 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.
SpeechRecognizerManager.startListening (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/SpeechRecognizerManager.kt:49— SpeechRecognizerManager.startListening has cyclomatic complexity 16 (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.
ScheduleBridge.applyScheduleArgs (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleBridge.kt:229— ScheduleBridge.applyScheduleArgs 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.
ProviderAuthDialogKt.ProviderAuthDialog (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt:32— ProviderAuthDialogKt.ProviderAuthDialog has cyclomatic complexity 16 (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.
LocalRuntimeManagementScreenKt.AdbSetupCard (cyclomatic 16) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt:431— LocalRuntimeManagementScreenKt.AdbSetupCard has cyclomatic complexity 16 (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.
AndCodeAppKt.AndCodeApp (cognitive 106) app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:182— AndCodeAppKt.AndCodeApp has cognitive complexity 106 (threshold 15). Drivers by points: if/else 70 (84 pts), boolean chains 10, match/switch 6 (9 pts), loops 2 (3 pts) (nesting depth added 18). 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.
ChatHomeScreenKt.ChatHomeScreen (cognitive 80) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:187— ChatHomeScreenKt.ChatHomeScreen has cognitive complexity 80 (threshold 15). Drivers by points: if/else 41 (56 pts), boolean chains 19, match/switch 3 (4 pts), loops 1 (nesting depth added 16). 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.
ChatViewModel.handleEvent (cognitive 73) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:2304— ChatViewModel.handleEvent has cognitive complexity 73 (threshold 15). Drivers by points: if/else 27 (53 pts), boolean chains 10, match/switch 5 (10 pts) (nesting depth added 31). 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.
AndroidSetupScreenKt.AndroidSetupScreen (cognitive 66) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:99— AndroidSetupScreenKt.AndroidSetupScreen has cognitive complexity 66 (threshold 15). Drivers by points: if/else 30 (42 pts), boolean chains 22, match/switch 2 (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.
CodeViewerScreenKt.CodeViewerScreen (cognitive 54) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt:95— CodeViewerScreenKt.CodeViewerScreen has cognitive complexity 54 (threshold 15). Drivers by points: if/else 30 (50 pts), boolean chains 4 (nesting depth added 20). 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.
ChatHomeScreenKt.ChatComposer (cognitive 42) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1370— ChatHomeScreenKt.ChatComposer has cognitive complexity 42 (threshold 15). Drivers by points: if/else 33 (37 pts), boolean chains 5 (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.
ChatViewModel.sendMessage (cognitive 39) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1414— ChatViewModel.sendMessage has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 12, loops 1 (nesting depth added 6). 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.
VerifiedRuntimeDownloader.downloadLocked (cognitive 37) app/src/main/java/com/yugahashimoto/andcode/runtime/local/VerifiedRuntimeDownloader.kt:38— VerifiedRuntimeDownloader.downloadLocked has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 11, error handling 2, loops 1 (2 pts) (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.
ChatViewModel.sendSlashCommand (cognitive 33) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1677— ChatViewModel.sendSlashCommand has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 10, loops 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.
ScheduleEditorScreenKt.ScheduleEditorScreen (cognitive 31) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleEditorScreen.kt:89— ScheduleEditorScreenKt.ScheduleEditorScreen has cognitive complexity 31 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 3, match/switch 2 (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.
MarkdownLite.parse (cognitive 30) app/src/main/java/com/yugahashimoto/andcode/feature/chat/MarkdownLite.kt:65— MarkdownLite.parse has cognitive complexity 30 (threshold 15). Drivers by points: loops 6 (16 pts), boolean chains 10, if/else 2, match/switch 1 (2 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Field.parse (cognitive 29) app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleModels.kt:155— Field.parse has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 2 (3 pts), boolean chains 2 (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.
WakeWordService.startListening (cognitive 26) app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/WakeWordService.kt:227— WakeWordService.startListening has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 2, error handling 2, loops 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.
RuntimeActivityRepository.handle (cognitive 24) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt:489— RuntimeActivityRepository.handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 2 (3 pts) (nesting depth added 9). 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.
AndCodeVoiceSession.startEventCollection (cognitive 24) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndCodeVoiceSession.kt:222— AndCodeVoiceSession.startEventCollection has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 4, match/switch 1 (nesting depth added 10). 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.
ScheduleBridge.applyScheduleArgs (cognitive 24) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleBridge.kt:229— ScheduleBridge.applyScheduleArgs has cognitive complexity 24 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 2 (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.
GitHubStarCoordinator.refresh (cognitive 23) app/src/main/java/com/yugahashimoto/andcode/feature/support/GitHubStarSupport.kt:182— GitHubStarCoordinator.refresh has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7 (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.
SettingsScreenV2Kt.SettingsScreenV2 (cognitive 21) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:67— SettingsScreenV2Kt.SettingsScreenV2 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 21. 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.
WorkspacesScreenKt.WorkspacesScreen (cognitive 21) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:90— WorkspacesScreenKt.WorkspacesScreen has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 1, match/switch 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.
AndCodeAppKt.GithubCloneDialog (cognitive 20) app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1602— AndCodeAppKt.GithubCloneDialog has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 3 (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.
FlowExtKt.debounceFalseEdge (cognitive 19) app/src/main/java/com/yugahashimoto/andcode/core/util/FlowExt.kt:34— FlowExtKt.debounceFalseEdge has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts) (nesting depth added 10). 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.
RuntimeCatalogRepository.load (cognitive 19) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt:176— RuntimeCatalogRepository.load has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 5 (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.
RuntimeCatalogRepository.refreshAgents (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeCatalogRepository.kt:324— RuntimeCatalogRepository.refreshAgents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, match/switch 1 (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.
AndroidTTSProvider.speak (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/feature/assistant/AndroidTTSProvider.kt:64— AndroidTTSProvider.speak has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 4 (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.
ModelAndRuntimePickerSheetKt.ModelAndRuntimePickerSheet (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:69— ModelAndRuntimePickerSheetKt.ModelAndRuntimePickerSheet has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (nesting depth added 3). 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.
ProviderAuthDialogKt.ProviderAuthDialog (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderAuthDialog.kt:32— ProviderAuthDialogKt.ProviderAuthDialog has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, match/switch 3 (4 pts) (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.
RemoteConnectionScreenKt.RemoteConnectionScreen (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:84— RemoteConnectionScreenKt.RemoteConnectionScreen has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 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.
RuntimeArchive.extractTar (cognitive 18) app/src/main/java/com/yugahashimoto/andcode/runtime/local/RuntimeArchive.kt:66— RuntimeArchive.extractTar has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, match/switch 2 (3 pts), loops 1 (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.
OpenCodeV2ApiClient.singleEventStream (cognitive 17) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:742— OpenCodeV2ApiClient.singleEventStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2, match/switch 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.
RuntimeActivityRepository.watchForStalls (cognitive 17) app/src/main/java/com/yugahashimoto/andcode/data/repository/RuntimeActivityRepository.kt:253— RuntimeActivityRepository.watchForStalls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), error handling 2 (6 pts), loops 2 (3 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.
AndroidSetupScreenKt.RuntimeDownloadStep (cognitive 17) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:735— AndroidSetupScreenKt.RuntimeDownloadStep has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1 (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.
ScheduleExecutionService.watchForCompletion (cognitive 17) app/src/main/java/com/yugahashimoto/andcode/feature/schedule/ScheduleExecutionService.kt:499— ScheduleExecutionService.watchForCompletion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, error handling 1, 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.
SettingsNavGraphKt.settingsNavGraph (cognitive 17) app/src/main/java/com/yugahashimoto/andcode/ui/navigation/SettingsNavGraph.kt:41— SettingsNavGraphKt.settingsNavGraph has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (17 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.
AssistantActivityRowKt.TodoTimelineCard (cognitive 16) app/src/main/java/com/yugahashimoto/andcode/feature/chat/AssistantActivityRow.kt:461— AssistantActivityRowKt.TodoTimelineCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 2 (4 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.
WorkspacesScreenKt.WorkspaceProjectRow (cognitive 16) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:701— WorkspacesScreenKt.WorkspaceProjectRow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (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.
LocalRuntimeInstaller.install (cognitive 16) app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:49— LocalRuntimeInstaller.install has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 3, error handling 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.
andcode-browser-mcp.main (cognitive 16) app/src/main/assets/scripts/andcode-browser-mcp.py:584— andcode-browser-mcp.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 2 (6 pts), boolean chains 1, 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.
andcode-schedule-mcp.main (cognitive 16) app/src/main/assets/scripts/andcode-schedule-mcp.py:219— andcode-schedule-mcp.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 2 (6 pts), boolean chains 1, 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.
Near-duplicate member pair (102 shared lines) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1414— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1414-1668 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1680-1851 — These two members are variants of one another: 102 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:62— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:62-87 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:93-118 | app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:35-59 | app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:96-120 — 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:220— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:220-258 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:230-271 — These two members are one piece of code written twice and then edited apart: 39 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 (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:44— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:44-90 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt:69-123 — These two members are one piece of code written twice and then edited apart: 47 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:266— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:266-287 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:279-304 — These two members are one piece of code written twice and then edited apart: 22 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/ServerInfoScreen.kt:283— app/src/main/java/com/yugahashimoto/andcode/feature/settings/ServerInfoScreen.kt:283-318 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/ServerInfoScreen.kt:321-372 — 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:208— app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:208-261 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:437-492 — These two members are one piece of code written twice and then edited apart: 54 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:187— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:187-220 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:238-281 — These two members are one piece of code written twice and then edited apart: 34 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:804— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:804-831 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/VoiceSettingsScreen.kt:1040-1078 — 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 copies of one member (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:163— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:163-187 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:193-217 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:256-276 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:282-302 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 21 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.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) app/src/main/java/com/yugahashimoto/andcode/core/notification/RuntimeNotificationHelper.kt:131— app/src/main/java/com/yugahashimoto/andcode/core/notification/RuntimeNotificationHelper.kt:131-158 | app/src/main/java/com/yugahashimoto/andcode/core/notification/RuntimeNotificationHelper.kt:200-220 | app/src/main/java/com/yugahashimoto/andcode/core/notification/RuntimeNotificationHelper.kt:231-257 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravitySandboxLauncher.kt:22— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravitySandboxLauncher.kt:22-53 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexSandboxLauncher.kt:23-56 — These two members are one piece of code written twice and then edited apart: 32 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) · ×1
Edited copy of a member (23 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:341— app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:341-363 | app/src/main/java/com/yugahashimoto/andcode/ui/AppDrawerContent.kt:533-556 — 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2325— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2325-2344 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2347-2370 — 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 copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:27— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:27-47 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AgentAuthDialogs.kt:61-81 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/CodeViewerScreen.kt:405-417 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:164— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:164-170 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:602-608 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentSettingsScreen.kt:617-623 — 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 copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:72— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:72-78 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/CodexTarget.kt:80-92 — 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.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderStore.kt:107— app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderStore.kt:107-117 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalProviderCredentialStore.kt:99-109 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:425— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityAuthCoordinator.kt:425-432 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeAuthCoordinator.kt:203-210 — 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 (2 corresponding lines) · ×1
Edited copy of a member (2 corresponding lines) runtime_tools/termux_assets.py:251— runtime_tools/termux_assets.py:251-253 | scripts/prepare_android_runtime_assets.py:320-321 — These two members are one piece of code written twice and then edited apart: 2 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) · ×1
Edited copy of a member (6 corresponding lines) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt:388— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt:388-393 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspaceExplorerScreen.kt:1012-1017 — 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.
Duplicated block (45–46 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:94— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:94-138 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:117-162 — 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 (39–44 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1500— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1500-1543 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1717-1755 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1500` 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–33 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1599— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1599-1631 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1800-1822 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1599` 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 (23–26 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1572— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1572-1597 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1776-1798 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1572` 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 before the matched lines, `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1571` calls `emptyList` and `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatViewModel.kt:1775` does not — after which the two agree again for 4 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 (25 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1858— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1858-1882 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1989-2013 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:1858` 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 (23–25 lines × 2) app/src/main/java/com/yugahashimoto/andcode/ui/theme/Theme.kt:55— app/src/main/java/com/yugahashimoto/andcode/ui/theme/Theme.kt:55-79 | app/src/main/java/com/yugahashimoto/andcode/ui/theme/Theme.kt:95-117 — 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 (23 lines × 4) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:512— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:512-534 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:544-566 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:618-640 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:650-672 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:512` 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 (21 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentStatusCard.kt:71— app/src/main/java/com/yugahashimoto/andcode/feature/settings/AgentStatusCard.kt:71-91 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt:400-420 — 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. 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 lines × 3) app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:429— app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:429-447 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:470-488 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:576-594 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/SettingsScreenV2.kt:429` 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 (19 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2483— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2483-2501 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2542-2560 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2483` 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 (17–18 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1353— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1353-1369 | app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1410-1427 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1353` 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 (15 lines × 3) app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:177— app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:177-191 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:241-255 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeInstaller.kt:469-483 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/DebianRootfsInstaller.kt:177` 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 (14–15 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:318— app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:318-332 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt:181-194 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:318` 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) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:731— app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:731-742 | app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1048-1060 — before extracting anything, compare `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt` and `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 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 `app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:731` 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 (10–13 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:272— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:272-281 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ClaudeCodeCard.kt:285-297 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/AntigravityCard.kt:272` 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.
Duplicated block (9–12 lines × 2) app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1440— app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1440-1451 | app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1480-1488 — 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 `app/src/main/java/com/yugahashimoto/andcode/ui/AndCodeApp.kt:1440` 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 (10–11 lines × 2) app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:733— app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:733-743 | app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:793-802 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/workspace/WorkspacesScreen.kt:733` 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 (9 lines × 3) app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952— app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952-960 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2154-2162 | app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:2233-2241 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt:952` 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 (8–9 lines × 2) app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityMessageStore.kt:81— app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityMessageStore.kt:81-88 | app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeMessageStore.kt:108-116 — 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 `app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeMessageStore.kt:108` 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 (5 lines × 4) app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:68— app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:68-72 | app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:99-103 | app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:41-45 | app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:102-106 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:68` 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) app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:144— app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:144-150 | app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:161-167 — 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 `app/src/main/java/com/yugahashimoto/andcode/feature/settings/GitHubAuthRepository.kt:144` 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.
DM10 · One transaction, one aggregate· One operation mutates 2 aggregates · ×1
One operation mutates 2 aggregates: VoskModelStore.install app/src/main/java/com/yugahashimoto/andcode/feature/wakeword/VoskModelStore.kt:57— `VoskModelStore.install` saves `Downloading`, `VoskModelState` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:84— `getPullRequests` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:115— `getIssues` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:184— `getPullRequests` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:214— `getIssues` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:273— `getPullRequests` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/ForgeClient.kt:299— `getIssues` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:56— `getPullRequests` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/core/api/GitHubApiClient.kt:117— `searchIssues` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:22— `connections` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:528— `readLanguage` swallows every exception into `"system"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/feature/settings/AssistantTargetResolver.kt:26— `loadAssistantProviders` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCommandCatalog.kt:82— `frontMatter` swallows every exception into `emptyMap()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudePermissionBridge.kt:330— `loadAlwaysRules` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/CustomProviderStore.kt:164— `decodeList` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalProviderCredentialStore.kt:156— `decodeMap` swallows every exception into `emptyMap()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeDiagnostics.kt:214— `readDirectChildPids` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeProcessLauncher.kt:221— `tail` swallows every exception into `"No runtime log was produced"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeTarget.kt:154— `listSessions` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/com/yugahashimoto/andcode/runtime/remote/RemoteRuntimeTarget.kt:115— `listSessions` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityInstaller.kt:61— `!destination.exists() && backup.exists()` appears character-identically in 3 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityInstaller.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeEnvironmentActivation.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/VerifiedRuntimeDownloader.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt:588— `attachment.url.startsWith("data:") && encoded.isNotEmpty()` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityRuntime.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/AttachmentImporter.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt:46— `before.isNullOrBlank() || before == after` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityController.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeController.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityInstaller.kt:54— `candidate.setExecutable(true, false) || candidate.canExecute()` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityInstaller.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeUpdater.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:534— `cause !is OpenCodeApiException || cause.statusCode >= 500` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt, app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:73— `digest != null && SHA256_DIGEST.matches(digest)` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt. 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.
Duplicated predicate app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/AnalyticsReporter.kt:23— `enabled && !com.yugahashimoto.andcode.BuildConfig.DEBUG` appears character-identically in 2 files — app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/AnalyticsReporter.kt, app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt:38— `endpoint.isHttps || endpoint.host in LOOPBACK_HOSTS` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityReleaseClient.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeReleaseClient.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt:86— `form.baseUrl.isNotBlank() && form.normalizedUrl == null` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/workspace/ConnectionDialog.kt, app/src/main/java/com/yugahashimoto/andcode/feature/workspace/RemoteConnectionScreen.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt:142— `message.info.role == "assistant" && message.info.model == null` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/runtime/local/AntigravityTarget.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/ClaudeCodeTarget.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt:202— `query.isBlank() || it.name.contains(query, true) || it.id.contains(query, true)` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/chat/ModelAndRuntimePickerSheet.kt, app/src/main/java/com/yugahashimoto/andcode/feature/settings/ModelVisibilityScreen.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt:1172— `searchQuery.isBlank() || provider.name.contains(searchQuery, ignoreCase = true) || provider.id.contains(searchQuery, ignoreCase = true)` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/onboarding/AndroidSetupScreen.kt, app/src/main/java/com/yugahashimoto/andcode/feature/settings/ProviderSettingsScreen.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt:709— `sensitive || statusCode == 401 || statusCode == 403` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiClient.kt, app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:35— `status !is LocalRuntimeStatus.NotInstalled && status !is LocalRuntimeStatus.UnsupportedAbi` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt, app/src/main/java/com/yugahashimoto/andcode/runtime/local/LocalRuntimeDiagnostics.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleModels.kt:65— `status == ScheduleRunStatus.PENDING || status == ScheduleRunStatus.RUNNING` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleModels.kt, app/src/main/java/com/yugahashimoto/andcode/data/schedule/ScheduleRepository.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt:426— `this is LocalRuntimeStatus.Installing || this is LocalRuntimeStatus.Starting || this is LocalRuntimeStatus.Updating` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementScreen.kt, app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt. 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.
Duplicated predicate app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt:196— `this is LocalRuntimeStatus.Ready || this is LocalRuntimeStatus.Stopped || this is LocalRuntimeStatus.Broken || this is LocalRuntimeStatus.No…` appears character-identically in 2 files — app/src/main/java/com/yugahashimoto/andcode/feature/settings/OpenCodeAgentSettingsViewModel.kt, app/src/main/java/com/yugahashimoto/andcode/feature/workspace/LocalRuntimeManagementViewModel.kt. 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.
Fat interface: OpenCodeApi (50 abstract methods) app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:15— `OpenCodeApi` declares 50 abstract methods: `health`, `sessions`, `session`, `createSession`, `messages`, `deleteMessage`, `providers`, `agents`, `providerAuthMethods`, `authorizeProvider`, `setProviderApiKey`, `removeProviderAuth`, `completeProviderOAuth`, `projects`, `currentProject`, `pathInfo`, `files`, `fileContent`, `fileStatus`, `searchText`, `findFiles`, `vcsInfo`, `vcsStatus`, `vcsDiff`, `sessionDiff`, `sessionTodo`, `promptAsync`, `summarizeSession`, `abortSession`, `renameSession`, `deleteSession`, `archiveSession`, `mcpServers`, `addMcpServer`, `connectMcpServer`, `disconnectMcpServer`, `removeMcpAuth`, `mcpAuth`, `mcpAuthCallback`, `config`, and 10 more. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
No ADRs found app/build.gradle.kts:5— 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 `app/build.gradle.kts` makes this repository a deployable product (line 5).
D21 · Naming Consistency· `callID` spells `ID` where 733 names in the project spell it `Id` · ×1
`callID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApiModels.kt:119— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `callId`. [rule N6]
D21 · Naming Consistency· `projectID` spells `ID` where 733 names in the project spell it `Id` · ×1
`projectID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1530— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `projectId`. [rule N6]
D21 · Naming Consistency· `parentID` spells `ID` where 733 names in the project spell it `Id` · ×1
`parentID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1531— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `parentId`. [rule N6]
D21 · Naming Consistency· `providerID` spells `ID` where 733 names in the project spell it `Id` · ×1
`providerID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1550— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `providerId`. [rule N6]
D21 · Naming Consistency· `attemptID` spells `ID` where 733 names in the project spell it `Id` · ×1
`attemptID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1612— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `attemptId`. [rule N6]
D21 · Naming Consistency· `integrationID` spells `ID` where 733 names in the project spell it `Id` · ×1
`integrationID` spells `ID` where 733 names in the project spell it `Id` app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeV2ApiClient.kt:1621— 733 of 739 names in project app spell the token `Id` (733 of 739; unit: names in project app containing `Id`). Peers: CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/fdroid/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:23); CrashReporter.recordRuntimeSessionError(runtimeId) (app/src/github/java/com/yugahashimoto/andcode/core/diagnostics/CrashReporter.kt:78); OpenCodeApi.session(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:20); OpenCodeApi.messages(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:27); OpenCodeApi.deleteMessage(sessionId) (app/src/main/java/com/yugahashimoto/andcode/core/api/OpenCodeApi.kt:29). Rename to `integrationId`. [rule N6]
D21 · Naming Consistency· `OpenAI` spells `AI` where 30 names in the project spell it `Ai` · ×1
`OpenAI` spells `AI` where 30 names in the project spell it `Ai` app/src/main/java/com/yugahashimoto/andcode/feature/assistant/TTSProvider.kt:19— 30 of 31 names in project app spell the token `Ai` (30 of 31; unit: names in project app containing `Ai`). Peers: SecureSettingsRepository.ttsOpenAiApiKey (app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:88); SecureSettingsRepository.ttsOpenAiVoice (app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:92); SecureSettingsRepository.ttsOpenAiModel (app/src/main/java/com/yugahashimoto/andcode/data/connection/SecureSettingsRepository.kt:96); AppPreferences.ttsOpenAiApiKey (app/src/main/java/com/yugahashimoto/andcode/data/settings/AppPreferencesRepository.kt:24); AppPreferences.ttsOpenAiVoice (app/src/main/java/com/yugahashimoto/andcode/data/settings/AppPreferencesRepository.kt:25). Rename to `OpenAi`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion app/build.gradle.kts:1— `app` (67325 LoC, 1051 module-visible types across 41 directories) overshoots its size bounds. 1 of 2 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 0.0/10. 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.
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:6— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (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 8 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 app/build.gradle.kts:254— `app/build.gradle.kts` 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 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.)
X2 · Cancellation propagation· Not all suspend functions that make a request accept the coroutine's cancellation · ×1
Not all suspend functions that make a request accept the coroutine's cancellation — Only 0/18 suspend functions that make a cancellable request (Ktor, OkHttp newCall, URL streams) accept the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a screen navigated away from, a disposed widget, a superseded search. In a suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 15 file(s) — `app/src/main/java/com/yugahashimoto/andcode/core/diagnostics/SessionStallDiagnosis.kt`, `app/src/main/java/com/yugahashimoto/andcode/data/local/MessageEntity.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/assistant/CloudTTSProvider.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/assistant/VoiceDictationPolicy.kt`, `app/src/main/java/com/yugahashimoto/andcode/feature/chat/ChatHomeScreen.kt`, … (+10 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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
0
—
Run 01a1e683-7ba0-761e-aed2-a268b604658f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 38 · Warnings: 323 · Recommendations: 54 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 22:38 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.