Public report of hosizoraru/KeiOS, published 17 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, 17 November 2026, 11:08 UTC · Survey ID cd_773e8c877e0e44bab18751630b60feed
hosizoraru/KeiOS
Measured 17 November 2026, 11:07 UTC, at code version 23618a3
First survey, so nothing to compare with yet
CAI scoreAdequate
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 large codebase: 303,492 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 3.1 person-years · Weakest lens: Production Readiness, 38.2
Findings by how serious they are
20 critical1585 serious101 minor
14 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
17 November 2026, 11:07 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 ▸
60of 60 dimensions measured by tools.
1685of 1706 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
60dimensions across 7 lenses, read from 303,492 lines of product code in 23 projects.
hosizoraru/KeiOS 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 53.3 out of 100 and is rated Adequate, and none of its 20 critical findings concern security.
Production Readiness, at 38.2, is the weakest lens and counts most in the score. The best first steps are adopting a logging library and adding automated security scanning, each worth about 8.8 points. Raising Production Readiness to 70 would lift the score to about 64.4.
Twenty sets of files in separate parts keep changing together, which points to hidden dependencies. Making the hidden dependencies explicit would close this risk.
The product code is 303,492 lines, about €450,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 38.2 to 70, the lowest score rated Strong, the score would rise from 53.3 to about 64.4.
Code composition: what the lines of code are
Product code 76%Tests 24%
Rebuild cost: about €450,000 · Estimate
Cost to rebuild
€150,000 to €750,000, for 2,474 to 7,850 hours of work, about 3.1 person-years for 1 to 6 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 53. 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
Large: 303,492 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
Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
Raises the score by about 8.8 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
Raises the score by about 2.1 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
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 €450,000 to build again, about 3.1 person-years of work. Its weakest lens is Production Readiness, at 38.2 (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
Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. Of all the actions in this report, it raises the score most for the work it takes: about 8.8 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.2 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 598,930 lines over the last 90 days, which is about 2,428,994 lines a year. At that pace, the extra work comes to an estimated 127.3 to 809.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
815 modules, with 1063 dependencies between them. 17 loops run through 94 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 775 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.
feature.github.model uses core.versioning, so a change to core.versioning can break feature.github.model, while a change to feature.github.model can't break core.versioning.
Position
Below the diagonal: feature.github.model uses a module listed above it, which is the healthy direction.
7→14 feature.github.model uses feature.github.domainpart of a loop✕
Connections
2 pairs of types, where a type in feature.github.model uses a type in feature.github.domain.
feature.github.model uses feature.github.domain, so a change to feature.github.domain can break feature.github.model, while a change to feature.github.model can't break feature.github.domain.
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.
ui.page.main.ba.support uses ui.page.main.ba, so a change to ui.page.main.ba can break ui.page.main.ba.support, while a change to ui.page.main.ba.support can't break ui.page.main.ba.
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→28 ui.page.main.os.shortcut uses ui.page.main.os.transferpart of a loop✕
Connections
4 pairs of types, where a type in ui.page.main.os.shortcut uses a type in ui.page.main.os.transfer.
ui.page.main.os.shortcut uses ui.page.main.os.transfer, so a change to ui.page.main.os.transfer can break ui.page.main.os.shortcut, while a change to ui.page.main.os.shortcut can't break ui.page.main.os.transfer.
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→33 ui.page.main.os.shortcut uses ui.page.main.ospart of a loop✕
Connections
14 pairs of types, where a type in ui.page.main.os.shortcut uses a type in ui.page.main.os.
ui.page.main.os.shortcut uses ui.page.main.os, so a change to ui.page.main.os can break ui.page.main.os.shortcut, while a change to ui.page.main.os.shortcut can't break ui.page.main.os.
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→34 ui.page.main.student.catalog uses ui.page.main.studentpart of a loop✕
Connections
3 pairs of types, where a type in ui.page.main.student.catalog uses a type in ui.page.main.student.
ui.page.main.student.catalog uses ui.page.main.student, so a change to ui.page.main.student can break ui.page.main.student.catalog, while a change to ui.page.main.student.catalog can't break ui.page.main.student.
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.
ui.page.main.widget.chrome uses core.prefs, so a change to core.prefs can break ui.page.main.widget.chrome, while a change to ui.page.main.widget.chrome can't break core.prefs.
Position
Below the diagonal: ui.page.main.widget.chrome uses a module listed above it, which is the healthy direction.
feature.github.data.local.fdroid uses feature.github.model, so a change to feature.github.model can break feature.github.data.local.fdroid, while a change to feature.github.data.local.fdroid can't break feature.github.model.
Position
Below the diagonal: feature.github.data.local.fdroid uses a module listed above it, which is the healthy direction.
229 pairs of types, where a type in feature.github.domain uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
feature.github.domain uses feature.github.model, so a change to feature.github.model can break feature.github.domain, while a change to feature.github.domain can't break feature.github.model.
Position
Below the diagonal: feature.github.domain uses a module listed above it, which is the healthy direction.
14→15 feature.github.domain uses feature.github.data.remotepart of a loop✕
Connections
33 pairs of types, where a type in feature.github.domain uses a type in feature.github.data.remote. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
feature.github.domain uses feature.github.data.remote, so a change to feature.github.data.remote can break feature.github.domain, while a change to feature.github.domain can't break feature.github.data.remote.
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→18 feature.github.domain uses feature.github.data.localpart of a loop✕
Connections
17 pairs of types, where a type in feature.github.domain uses a type in feature.github.data.local.
feature.github.domain uses feature.github.data.local, so a change to feature.github.data.local can break feature.github.domain, while a change to feature.github.domain can't break feature.github.data.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.
feature.github.data.remote uses core.versioning, so a change to core.versioning can break feature.github.data.remote, while a change to feature.github.data.remote can't break core.versioning.
Position
Below the diagonal: feature.github.data.remote uses a module listed above it, which is the healthy direction.
120 pairs of types, where a type in feature.github.data.remote uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
feature.github.data.remote uses feature.github.model, so a change to feature.github.model can break feature.github.data.remote, while a change to feature.github.data.remote can't break feature.github.model.
Position
Below the diagonal: feature.github.data.remote uses a module listed above it, which is the healthy direction.
feature.github.data.remote uses feature.github.domain, so a change to feature.github.domain can break feature.github.data.remote, while a change to feature.github.data.remote can't break feature.github.domain.
Position
Below the diagonal: feature.github.data.remote uses a module listed above it, which is the healthy direction.
feature.github.notification uses core.prefs, so a change to core.prefs can break feature.github.notification, while a change to feature.github.notification can't break core.prefs.
Position
Below the diagonal: feature.github.notification uses a module listed above it, which is the healthy direction.
feature.github.notification uses feature.github.model, so a change to feature.github.model can break feature.github.notification, while a change to feature.github.notification can't break feature.github.model.
Position
Below the diagonal: feature.github.notification uses a module listed above it, which is the healthy direction.
feature.github.notification uses feature.github.domain, so a change to feature.github.domain can break feature.github.notification, while a change to feature.github.notification can't break feature.github.domain.
Position
Below the diagonal: feature.github.notification uses a module listed above it, which is the healthy direction.
feature.home.model uses core.prefs, so a change to core.prefs can break feature.home.model, while a change to feature.home.model can't break core.prefs.
Position
Below the diagonal: feature.home.model uses a module listed above it, which is the healthy direction.
feature.home.model uses feature.github.model, so a change to feature.github.model can break feature.home.model, while a change to feature.home.model can't break feature.github.model.
Position
Below the diagonal: feature.home.model uses a module listed above it, which is the healthy direction.
feature.home.model uses feature.github.domain, so a change to feature.github.domain can break feature.home.model, while a change to feature.home.model can't break feature.github.domain.
Position
Below the diagonal: feature.home.model uses a module listed above it, which is the healthy direction.
feature.github.data.local uses core.privilege, so a change to core.privilege can break feature.github.data.local, while a change to feature.github.data.local can't break core.privilege.
Position
Below the diagonal: feature.github.data.local uses a module listed above it, which is the healthy direction.
56 pairs of types, where a type in feature.github.data.local uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
feature.github.data.local uses feature.github.model, so a change to feature.github.model can break feature.github.data.local, while a change to feature.github.data.local can't break feature.github.model.
Position
Below the diagonal: feature.github.data.local uses a module listed above it, which is the healthy direction.
feature.github.data.local uses feature.github.domain, so a change to feature.github.domain can break feature.github.data.local, while a change to feature.github.data.local can't break feature.github.domain.
Position
Below the diagonal: feature.github.data.local uses a module listed above it, which is the healthy direction.
feature.github.data.local uses feature.github.data.remote, so a change to feature.github.data.remote can break feature.github.data.local, while a change to feature.github.data.local can't break feature.github.data.remote.
Position
Below the diagonal: feature.github.data.local uses a module listed above it, which is the healthy direction.
feature.github.install uses core.download.segmented, so a change to core.download.segmented can break feature.github.install, while a change to feature.github.install can't break core.download.segmented.
Position
Below the diagonal: feature.github.install uses a module listed above it, which is the healthy direction.
feature.github.install uses core.privilege, so a change to core.privilege can break feature.github.install, while a change to feature.github.install can't break core.privilege.
Position
Below the diagonal: feature.github.install uses a module listed above it, which is the healthy direction.
feature.github.install uses feature.github.model, so a change to feature.github.model can break feature.github.install, while a change to feature.github.install can't break feature.github.model.
Position
Below the diagonal: feature.github.install uses a module listed above it, which is the healthy direction.
feature.github.install uses feature.github.data.remote, so a change to feature.github.data.remote can break feature.github.install, while a change to feature.github.install can't break feature.github.data.remote.
Position
Below the diagonal: feature.github.install uses a module listed above it, which is the healthy direction.
ui.page.main.github uses feature.github.model, so a change to feature.github.model can break ui.page.main.github, while a change to ui.page.main.github can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github uses a module listed above it, which is the healthy direction.
ui.page.main.github uses feature.github.data.remote, so a change to feature.github.data.remote can break ui.page.main.github, while a change to ui.page.main.github can't break feature.github.data.remote.
Position
Below the diagonal: ui.page.main.github uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses core.prefs, so a change to core.prefs can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break core.prefs.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses core.privilege, so a change to core.privilege can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break core.privilege.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses ui.page.main.widget.glass, so a change to ui.page.main.widget.glass can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break ui.page.main.widget.glass.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses mcp.server, so a change to mcp.server can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break mcp.server.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses ui.page.main.widget.chrome, so a change to ui.page.main.widget.chrome can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break ui.page.main.widget.chrome.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.host.pager uses feature.home.model, so a change to feature.home.model can break ui.page.main.host.pager, while a change to ui.page.main.host.pager can't break feature.home.model.
Position
Below the diagonal: ui.page.main.host.pager uses a module listed above it, which is the healthy direction.
ui.page.main.github.page.action uses core.privilege, so a change to core.privilege can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break core.privilege.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
77 pairs of types, where a type in ui.page.main.github.page.action uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.github.page.action uses feature.github.model, so a change to feature.github.model can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
ui.page.main.github.page.action uses feature.github.domain, so a change to feature.github.domain can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break feature.github.domain.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
ui.page.main.github.page.action uses feature.github.data.remote, so a change to feature.github.data.remote can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break feature.github.data.remote.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
ui.page.main.github.page.action uses feature.github.data.local, so a change to feature.github.data.local can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break feature.github.data.local.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
ui.page.main.github.page.action uses ui.page.main.github, so a change to ui.page.main.github can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break ui.page.main.github.
Position
Below the diagonal: ui.page.main.github.page.action uses a module listed above it, which is the healthy direction.
22→27 ui.page.main.github.page.action uses ui.page.main.github.pagepart of a loop✕
Connections
37 pairs of types, where a type in ui.page.main.github.page.action uses a type in ui.page.main.github.page. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.github.page.action uses ui.page.main.github.page, so a change to ui.page.main.github.page can break ui.page.main.github.page.action, while a change to ui.page.main.github.page.action can't break ui.page.main.github.page.
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.
ui.page.main.github.share uses ui.page.main.widget.glass, so a change to ui.page.main.widget.glass can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break ui.page.main.widget.glass.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
ui.page.main.github.share uses feature.github.model, so a change to feature.github.model can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
ui.page.main.github.share uses feature.github.domain, so a change to feature.github.domain can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break feature.github.domain.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
ui.page.main.github.share uses feature.github.data.remote, so a change to feature.github.data.remote can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break feature.github.data.remote.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
ui.page.main.github.share uses feature.github.data.local, so a change to feature.github.data.local can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break feature.github.data.local.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
ui.page.main.github.share uses feature.github.install, so a change to feature.github.install can break ui.page.main.github.share, while a change to ui.page.main.github.share can't break feature.github.install.
Position
Below the diagonal: ui.page.main.github.share uses a module listed above it, which is the healthy direction.
95 pairs of types, where a type in ui.page.main.github.sheet uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.github.sheet uses feature.github.model, so a change to feature.github.model can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github.sheet uses a module listed above it, which is the healthy direction.
ui.page.main.github.sheet uses feature.github.data.local.fdroid, so a change to feature.github.data.local.fdroid can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break feature.github.data.local.fdroid.
Position
Below the diagonal: ui.page.main.github.sheet uses a module listed above it, which is the healthy direction.
ui.page.main.github.sheet uses feature.github.data.remote, so a change to feature.github.data.remote can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break feature.github.data.remote.
Position
Below the diagonal: ui.page.main.github.sheet uses a module listed above it, which is the healthy direction.
ui.page.main.github.sheet uses feature.github.data.local, so a change to feature.github.data.local can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break feature.github.data.local.
Position
Below the diagonal: ui.page.main.github.sheet uses a module listed above it, which is the healthy direction.
ui.page.main.github.sheet uses ui.page.main.github, so a change to ui.page.main.github can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break ui.page.main.github.
Position
Below the diagonal: ui.page.main.github.sheet uses a module listed above it, which is the healthy direction.
24→27 ui.page.main.github.sheet uses ui.page.main.github.pagepart of a loop✕
Connections
6 pairs of types, where a type in ui.page.main.github.sheet uses a type in ui.page.main.github.page.
ui.page.main.github.sheet uses ui.page.main.github.page, so a change to ui.page.main.github.page can break ui.page.main.github.sheet, while a change to ui.page.main.github.sheet can't break ui.page.main.github.page.
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.
ui.page.main.os.state uses core.privilege, so a change to core.privilege can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break core.privilege.
Position
Below the diagonal: ui.page.main.os.state uses a module listed above it, which is the healthy direction.
ui.page.main.os.state uses ui.page.main.os.shortcut, so a change to ui.page.main.os.shortcut can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break ui.page.main.os.shortcut.
Position
Below the diagonal: ui.page.main.os.state uses a module listed above it, which is the healthy direction.
ui.page.main.os.state uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.os.state uses a module listed above it, which is the healthy direction.
25→28 ui.page.main.os.state uses ui.page.main.os.transferpart of a loop✕
Connections
3 pairs of types, where a type in ui.page.main.os.state uses a type in ui.page.main.os.transfer.
ui.page.main.os.state uses ui.page.main.os.transfer, so a change to ui.page.main.os.transfer can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break ui.page.main.os.transfer.
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.
25→31 ui.page.main.os.state uses ui.page.main.os.shellpart of a loop✕
Connections
7 pairs of types, where a type in ui.page.main.os.state uses a type in ui.page.main.os.shell.
ui.page.main.os.state uses ui.page.main.os.shell, so a change to ui.page.main.os.shell can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break ui.page.main.os.shell.
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.
25→33 ui.page.main.os.state uses ui.page.main.ospart of a loop✕
Connections
15 pairs of types, where a type in ui.page.main.os.state uses a type in ui.page.main.os.
ui.page.main.os.state uses ui.page.main.os, so a change to ui.page.main.os can break ui.page.main.os.state, while a change to ui.page.main.os.state can't break ui.page.main.os.
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.
ui.page.main.student.catalog.page uses ui.page.main.student.catalog, so a change to ui.page.main.student.catalog can break ui.page.main.student.catalog.page, while a change to ui.page.main.student.catalog.page can't break ui.page.main.student.catalog.
Position
Below the diagonal: ui.page.main.student.catalog.page uses a module listed above it, which is the healthy direction.
ui.page.main.student.catalog.page uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.student.catalog.page, while a change to ui.page.main.student.catalog.page can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.student.catalog.page uses a module listed above it, which is the healthy direction.
26→29 ui.page.main.student.catalog.page uses ui.page.main.student.catalog.statepart of a loop✕
Connections
36 pairs of types, where a type in ui.page.main.student.catalog.page uses a type in ui.page.main.student.catalog.state. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.student.catalog.page uses ui.page.main.student.catalog.state, so a change to ui.page.main.student.catalog.state can break ui.page.main.student.catalog.page, while a change to ui.page.main.student.catalog.page can't break ui.page.main.student.catalog.state.
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.
26→32 ui.page.main.student.catalog.page uses ui.page.main.student.catalog.componentpart of a loop✕
Connections
11 pairs of types, where a type in ui.page.main.student.catalog.page uses a type in ui.page.main.student.catalog.component.
ui.page.main.student.catalog.page uses ui.page.main.student.catalog.component, so a change to ui.page.main.student.catalog.component can break ui.page.main.student.catalog.page, while a change to ui.page.main.student.catalog.page can't break ui.page.main.student.catalog.component.
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.
26→34 ui.page.main.student.catalog.page uses ui.page.main.studentpart of a loop✕
Connections
18 pairs of types, where a type in ui.page.main.student.catalog.page uses a type in ui.page.main.student.
ui.page.main.student.catalog.page uses ui.page.main.student, so a change to ui.page.main.student can break ui.page.main.student.catalog.page, while a change to ui.page.main.student.catalog.page can't break ui.page.main.student.
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.
ui.page.main.github.page uses core.privilege, so a change to core.privilege can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break core.privilege.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
118 pairs of types, where a type in ui.page.main.github.page uses a type in feature.github.model. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.github.page uses feature.github.model, so a change to feature.github.model can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses feature.github.data.local.fdroid, so a change to feature.github.data.local.fdroid can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break feature.github.data.local.fdroid.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses feature.github.domain, so a change to feature.github.domain can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break feature.github.domain.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses feature.github.data.remote, so a change to feature.github.data.remote can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break feature.github.data.remote.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses feature.github.data.local, so a change to feature.github.data.local can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break feature.github.data.local.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses ui.page.main.github, so a change to ui.page.main.github can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break ui.page.main.github.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses ui.page.main.github.page.action, so a change to ui.page.main.github.page.action can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break ui.page.main.github.page.action.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.github.page uses ui.page.main.github.share, so a change to ui.page.main.github.share can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break ui.page.main.github.share.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in ui.page.main.github.page uses a type in ui.page.main.github.sheet. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.github.page uses ui.page.main.github.sheet, so a change to ui.page.main.github.sheet can break ui.page.main.github.page, while a change to ui.page.main.github.page can't break ui.page.main.github.sheet.
Position
Below the diagonal: ui.page.main.github.page uses a module listed above it, which is the healthy direction.
ui.page.main.os.transfer uses ui.page.main.os.shortcut, so a change to ui.page.main.os.shortcut can break ui.page.main.os.transfer, while a change to ui.page.main.os.transfer can't break ui.page.main.os.shortcut.
Position
Below the diagonal: ui.page.main.os.transfer uses a module listed above it, which is the healthy direction.
ui.page.main.os.transfer uses ui.page.main.os.state, so a change to ui.page.main.os.state can break ui.page.main.os.transfer, while a change to ui.page.main.os.transfer can't break ui.page.main.os.state.
Position
Below the diagonal: ui.page.main.os.transfer uses a module listed above it, which is the healthy direction.
28→31 ui.page.main.os.transfer uses ui.page.main.os.shellpart of a loop✕
Connections
3 pairs of types, where a type in ui.page.main.os.transfer uses a type in ui.page.main.os.shell.
ui.page.main.os.transfer uses ui.page.main.os.shell, so a change to ui.page.main.os.shell can break ui.page.main.os.transfer, while a change to ui.page.main.os.transfer can't break ui.page.main.os.shell.
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.
28→33 ui.page.main.os.transfer uses ui.page.main.ospart of a loop✕
Connections
1 pair of types, where a type in ui.page.main.os.transfer uses a type in ui.page.main.os.
ui.page.main.os.transfer uses ui.page.main.os, so a change to ui.page.main.os can break ui.page.main.os.transfer, while a change to ui.page.main.os.transfer can't break ui.page.main.os.
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.
39 pairs of types, where a type in ui.page.main.student.catalog.state uses a type in ui.page.main.student.catalog. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.student.catalog.state uses ui.page.main.student.catalog, so a change to ui.page.main.student.catalog can break ui.page.main.student.catalog.state, while a change to ui.page.main.student.catalog.state can't break ui.page.main.student.catalog.
Position
Below the diagonal: ui.page.main.student.catalog.state uses a module listed above it, which is the healthy direction.
ui.page.main.student.catalog.state uses ui.page.main.student.catalog.page, so a change to ui.page.main.student.catalog.page can break ui.page.main.student.catalog.state, while a change to ui.page.main.student.catalog.state can't break ui.page.main.student.catalog.page.
Position
Below the diagonal: ui.page.main.student.catalog.state uses a module listed above it, which is the healthy direction.
29→32 ui.page.main.student.catalog.state uses ui.page.main.student.catalog.componentpart of a loop✕
Connections
8 pairs of types, where a type in ui.page.main.student.catalog.state uses a type in ui.page.main.student.catalog.component.
ui.page.main.student.catalog.state uses ui.page.main.student.catalog.component, so a change to ui.page.main.student.catalog.component can break ui.page.main.student.catalog.state, while a change to ui.page.main.student.catalog.state can't break ui.page.main.student.catalog.component.
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.
29→34 ui.page.main.student.catalog.state uses ui.page.main.studentpart of a loop✕
Connections
32 pairs of types, where a type in ui.page.main.student.catalog.state uses a type in ui.page.main.student. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.student.catalog.state uses ui.page.main.student, so a change to ui.page.main.student can break ui.page.main.student.catalog.state, while a change to ui.page.main.student.catalog.state can't break ui.page.main.student.
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.
29→35 ui.page.main.student.catalog.state uses ui.page.main.student.page.statepart of a loop✕
Connections
1 pair of types, where a type in ui.page.main.student.catalog.state uses a type in ui.page.main.student.page.state.
ui.page.main.student.catalog.state uses ui.page.main.student.page.state, so a change to ui.page.main.student.page.state can break ui.page.main.student.catalog.state, while a change to ui.page.main.student.catalog.state can't break ui.page.main.student.page.state.
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.
ui.page.main.github.history uses feature.github.model, so a change to feature.github.model can break ui.page.main.github.history, while a change to ui.page.main.github.history can't break feature.github.model.
Position
Below the diagonal: ui.page.main.github.history uses a module listed above it, which is the healthy direction.
ui.page.main.github.history uses ui.page.main.widget.chrome, so a change to ui.page.main.widget.chrome can break ui.page.main.github.history, while a change to ui.page.main.github.history can't break ui.page.main.widget.chrome.
Position
Below the diagonal: ui.page.main.github.history uses a module listed above it, which is the healthy direction.
ui.page.main.github.history uses feature.github.domain, so a change to feature.github.domain can break ui.page.main.github.history, while a change to ui.page.main.github.history can't break feature.github.domain.
Position
Below the diagonal: ui.page.main.github.history uses a module listed above it, which is the healthy direction.
ui.page.main.github.history uses ui.page.main.github.page, so a change to ui.page.main.github.page can break ui.page.main.github.history, while a change to ui.page.main.github.history can't break ui.page.main.github.page.
Position
Below the diagonal: ui.page.main.github.history uses a module listed above it, which is the healthy direction.
ui.page.main.os.shell uses core.prefs, so a change to core.prefs can break ui.page.main.os.shell, while a change to ui.page.main.os.shell can't break core.prefs.
Position
Below the diagonal: ui.page.main.os.shell uses a module listed above it, which is the healthy direction.
ui.page.main.os.shell uses ui.page.main.os.transfer, so a change to ui.page.main.os.transfer can break ui.page.main.os.shell, while a change to ui.page.main.os.shell can't break ui.page.main.os.transfer.
Position
Below the diagonal: ui.page.main.os.shell uses a module listed above it, which is the healthy direction.
ui.page.main.student.catalog.component uses ui.page.main.student.catalog, so a change to ui.page.main.student.catalog can break ui.page.main.student.catalog.component, while a change to ui.page.main.student.catalog.component can't break ui.page.main.student.catalog.
Position
Below the diagonal: ui.page.main.student.catalog.component uses a module listed above it, which is the healthy direction.
ui.page.main.student.catalog.component uses ui.page.main.student.catalog.state, so a change to ui.page.main.student.catalog.state can break ui.page.main.student.catalog.component, while a change to ui.page.main.student.catalog.component can't break ui.page.main.student.catalog.state.
Position
Below the diagonal: ui.page.main.student.catalog.component uses a module listed above it, which is the healthy direction.
32→34 ui.page.main.student.catalog.component uses ui.page.main.studentpart of a loop✕
Connections
38 pairs of types, where a type in ui.page.main.student.catalog.component uses a type in ui.page.main.student. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.student.catalog.component uses ui.page.main.student, so a change to ui.page.main.student can break ui.page.main.student.catalog.component, while a change to ui.page.main.student.catalog.component can't break ui.page.main.student.
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.
ui.page.main.os uses core.privilege, so a change to core.privilege can break ui.page.main.os, while a change to ui.page.main.os can't break core.privilege.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in ui.page.main.os uses a type in ui.page.main.os.shortcut. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.os uses ui.page.main.os.shortcut, so a change to ui.page.main.os.shortcut can break ui.page.main.os, while a change to ui.page.main.os can't break ui.page.main.os.shortcut.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
ui.page.main.os uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.os, while a change to ui.page.main.os can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
ui.page.main.os uses ui.page.main.os.state, so a change to ui.page.main.os.state can break ui.page.main.os, while a change to ui.page.main.os can't break ui.page.main.os.state.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
ui.page.main.os uses ui.page.main.os.transfer, so a change to ui.page.main.os.transfer can break ui.page.main.os, while a change to ui.page.main.os can't break ui.page.main.os.transfer.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
ui.page.main.os uses ui.page.main.os.shell, so a change to ui.page.main.os.shell can break ui.page.main.os, while a change to ui.page.main.os can't break ui.page.main.os.shell.
Position
Below the diagonal: ui.page.main.os uses a module listed above it, which is the healthy direction.
ui.page.main.student uses ui.page.main.student.catalog, so a change to ui.page.main.student.catalog can break ui.page.main.student, while a change to ui.page.main.student can't break ui.page.main.student.catalog.
Position
Below the diagonal: ui.page.main.student uses a module listed above it, which is the healthy direction.
ui.page.main.student uses ui.page.main.student.catalog.component, so a change to ui.page.main.student.catalog.component can break ui.page.main.student, while a change to ui.page.main.student can't break ui.page.main.student.catalog.component.
Position
Below the diagonal: ui.page.main.student uses a module listed above it, which is the healthy direction.
ui.page.main.student.page.state uses ui.page.main.student.catalog, so a change to ui.page.main.student.catalog can break ui.page.main.student.page.state, while a change to ui.page.main.student.page.state can't break ui.page.main.student.catalog.
Position
Below the diagonal: ui.page.main.student.page.state uses a module listed above it, which is the healthy direction.
ui.page.main.student.page.state uses ui.page.main.widget.chrome, so a change to ui.page.main.widget.chrome can break ui.page.main.student.page.state, while a change to ui.page.main.student.page.state can't break ui.page.main.widget.chrome.
Position
Below the diagonal: ui.page.main.student.page.state uses a module listed above it, which is the healthy direction.
38 pairs of types, where a type in ui.page.main.student.page.state uses a type in ui.page.main.student. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.student.page.state uses ui.page.main.student, so a change to ui.page.main.student can break ui.page.main.student.page.state, while a change to ui.page.main.student.page.state can't break ui.page.main.student.
Position
Below the diagonal: ui.page.main.student.page.state uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses feature.github.model, so a change to feature.github.model can break ui.page.main.sync, while a change to ui.page.main.sync can't break feature.github.model.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses ui.page.main.os.shortcut, so a change to ui.page.main.os.shortcut can break ui.page.main.sync, while a change to ui.page.main.sync can't break ui.page.main.os.shortcut.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses ui.page.main.widget.chrome, so a change to ui.page.main.widget.chrome can break ui.page.main.sync, while a change to ui.page.main.sync can't break ui.page.main.widget.chrome.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses feature.github.data.local, so a change to feature.github.data.local can break ui.page.main.sync, while a change to ui.page.main.sync can't break feature.github.data.local.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.sync, while a change to ui.page.main.sync can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses ui.page.main.os.shell, so a change to ui.page.main.os.shell can break ui.page.main.sync, while a change to ui.page.main.sync can't break ui.page.main.os.shell.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.sync uses ui.page.main.os, so a change to ui.page.main.os can break ui.page.main.sync, while a change to ui.page.main.sync can't break ui.page.main.os.
Position
Below the diagonal: ui.page.main.sync uses a module listed above it, which is the healthy direction.
ui.page.main.ba uses ui.page.main.widget.glass, so a change to ui.page.main.widget.glass can break ui.page.main.ba, while a change to ui.page.main.ba can't break ui.page.main.widget.glass.
Position
Below the diagonal: ui.page.main.ba uses a module listed above it, which is the healthy direction.
112 pairs of types, where a type in ui.page.main.ba uses a type in ui.page.main.ba.support. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ui.page.main.ba uses ui.page.main.ba.support, so a change to ui.page.main.ba.support can break ui.page.main.ba, while a change to ui.page.main.ba can't break ui.page.main.ba.support.
Position
Below the diagonal: ui.page.main.ba uses a module listed above it, which is the healthy direction.
ui.page.main.ba uses ui.page.main.widget.chrome, so a change to ui.page.main.widget.chrome can break ui.page.main.ba, while a change to ui.page.main.ba can't break ui.page.main.widget.chrome.
Position
Below the diagonal: ui.page.main.ba uses a module listed above it, which is the healthy direction.
ui.page.main.ba uses ui.page.main.host.pager, so a change to ui.page.main.host.pager can break ui.page.main.ba, while a change to ui.page.main.ba can't break ui.page.main.host.pager.
Position
Below the diagonal: ui.page.main.ba uses a module listed above it, which is the healthy direction.
ui.page.main.ba uses ui.page.main.student.page.state, so a change to ui.page.main.student.page.state can break ui.page.main.ba, while a change to ui.page.main.ba can't break ui.page.main.student.page.state.
Position
Below the diagonal: ui.page.main.ba uses a module listed above it, which is the healthy direction.
core.background uses feature.github.model, so a change to feature.github.model can break core.background, while a change to core.background can't break feature.github.model.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
core.background uses ui.page.main.ba.support, so a change to ui.page.main.ba.support can break core.background, while a change to core.background can't break ui.page.main.ba.support.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
core.background uses feature.github.domain, so a change to feature.github.domain can break core.background, while a change to core.background can't break feature.github.domain.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
core.background uses feature.github.data.local, so a change to feature.github.data.local can break core.background, while a change to core.background can't break feature.github.data.local.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
core.background uses ui.page.main.sync, so a change to ui.page.main.sync can break core.background, while a change to core.background can't break ui.page.main.sync.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
core.background uses ui.page.main.ba, so a change to ui.page.main.ba can break core.background, while a change to core.background can't break ui.page.main.ba.
Position
Below the diagonal: core.background uses a module listed above it, which is the healthy direction.
ui.page.main.settings.state uses core.prefs, so a change to core.prefs can break ui.page.main.settings.state, while a change to ui.page.main.settings.state can't break core.prefs.
Position
Below the diagonal: ui.page.main.settings.state uses a module listed above it, which is the healthy direction.
ui.page.main.settings.state uses core.privilege, so a change to core.privilege can break ui.page.main.settings.state, while a change to ui.page.main.settings.state can't break core.privilege.
Position
Below the diagonal: ui.page.main.settings.state uses a module listed above it, which is the healthy direction.
ui.page.main.settings.state uses core.background, so a change to core.background can break ui.page.main.settings.state, while a change to ui.page.main.settings.state can't break core.background.
Position
Below the diagonal: ui.page.main.settings.state uses a module listed above it, which is the healthy direction.
39→40 ui.page.main.settings.state uses ui.page.main.settings.sectionpart of a loop✕
Connections
17 pairs of types, where a type in ui.page.main.settings.state uses a type in ui.page.main.settings.section.
ui.page.main.settings.state uses ui.page.main.settings.section, so a change to ui.page.main.settings.section can break ui.page.main.settings.state, while a change to ui.page.main.settings.state can't break ui.page.main.settings.section.
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.
ui.page.main.settings.section uses core.prefs, so a change to core.prefs can break ui.page.main.settings.section, while a change to ui.page.main.settings.section can't break core.prefs.
Position
Below the diagonal: ui.page.main.settings.section uses a module listed above it, which is the healthy direction.
ui.page.main.settings.section uses core.privilege, so a change to core.privilege can break ui.page.main.settings.section, while a change to ui.page.main.settings.section can't break core.privilege.
Position
Below the diagonal: ui.page.main.settings.section uses a module listed above it, which is the healthy direction.
ui.page.main.settings.section uses core.background, so a change to core.background can break ui.page.main.settings.section, while a change to ui.page.main.settings.section can't break core.background.
Position
Below the diagonal: ui.page.main.settings.section uses a module listed above it, which is the healthy direction.
ui.page.main.settings.section uses ui.page.main.settings.state, so a change to ui.page.main.settings.state can break ui.page.main.settings.section, while a change to ui.page.main.settings.section can't break ui.page.main.settings.state.
Position
Below the diagonal: ui.page.main.settings.section uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56.6 · Adequate · gated by R1 ·
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
18
Medium
A03:2025 — Software Supply Chain Failures
3
Medium
A02:2025 — Security Misconfiguration
1
Medium
Roadmap
Top priorities: Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run; 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; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
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.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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.
Resolve the 162 MethodTooLong finding(s) in God Classes — start with GitHubActionsNotificationHistoryPage.kt (2), AppLiquidButtons.kt (2), AppLiquidSearchField.kt (2).
Code Duplication: Edited copy of a member (16 corresponding lines)
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 — 20
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 — 1585
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 — 101
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 60 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1685 of 1706 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: this repository's production source spans .py, .kt, and our analyzer cannot run the .kt test suite(s) — so no coverage was collected for the repository as a whole. The Python half did build and run, and its own line coverage came back at 78.3% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
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: no test result was produced. 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 — 24 Maven/Gradle manifest(s) were read, stating a version for 66 dependency(ies) and leaving 14 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. 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 (3 contributor(s) across 3564 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 2 hold 0.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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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: it declares a published package (ui-pip/build.gradle.kts), but 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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt`, `app/src/main/java/os/kei/memory/AppMemoryRelease.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaAccountManagementSheet.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadRepository.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaDailyDoneTemplateActivity.kt`, … (+47 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.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a native UI project (feature-webdav/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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 this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X10 Duplicated predicate — 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. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
X7 Silent fallback defaults — 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
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.
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.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
143 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GitHubWidgetRenderer.layout at 88. A further 33 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 GuideLocalizedLabelsKt.guideSourceLabelRes at 126 — they are counted neither in the figure above nor in this dimension's score. 23 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/os/kei/ui/page/main/student/GuideLocalizedLabels.kt (GuideLocalizedLabelsKt.guideSourceLabelRes at 126), app/src/main/java/os/kei/ui/page/main/github/GitHubDecisionAssistLabels.kt (GitHubDecisionAssistLabelsKt.labelRes at 32), app/src/main/java/os/kei/ui/page/main/os/OsTopInfoPresentation.kt (OsTopInfoPresentationKt.topInfoDisplayValue at 31), app/src/main/java/os/kei/ui/page/main/os/OsPageEffects.kt (OsPageEffectsKt.BindOsPageEvents at 25), feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshHistoryExportService.kt (GitHubRefreshHistoryExportService.parseScopeFilter at 24), and 18 more not listed here. 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.
+ 138 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 Cyclomatic Complexity — start with GitHubWidgetRenderer.layout (cyclomatic 88), GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson (cyclomatic 85), LiquidGlassBottomBarKt.LiquidGlassBottomBar (cyclomatic 78). — 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 Cyclomatic Complexity from 6.1 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: 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.
+ 204 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with LiquidGlassBottomBarKt.LiquidGlassBottomBar (cognitive 139), GitHubWidgetRenderer.layout (cognitive 126). — 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 2 together lifts Cognitive Complexity from 5.7 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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 Classes6.5 / 10Adequate✓ 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 162 MethodTooLong finding(s) in God Classes — start with GitHubActionsNotificationHistoryPage.kt (2), AppLiquidButtons.kt (2), AppLiquidSearchField.kt (2). — One of this dimension's main actionable groups (162 warning-level).
Resolve the 76 FileTooLong finding(s) in God Classes — start with MiFocusOfficialTemplateCatalog.kt, AppLiquidButtons.kt, GitHubActionsNotificationHistoryPage.kt. — One of this dimension's main actionable groups (76 warning-level).
Resolve the 39 TooManyMethods finding(s) in God Classes — start with GitHubPageActions.kt, BaSettingsStore.kt, GitHubPageRepository.kt. — One of this dimension's main actionable groups (39 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.
426 duplicated block group(s) detected. 7.6 % of the production lines (23,165 of 303,492) are in a reported copy. A further 317 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 743 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 195 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with GitHubPageContentStateDeriver.kt (2), McpGitHubTrackingToolsHelpers.kt (2), BaCalendarPoolViewModel.kt. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 25 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with FdroidVersionListPage.kt (2), WebDavSyncCards.kt (2), AppBackgroundRecoveryStore.kt. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 24 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), GitHubDirectApkDirectoryIndexResolver.kt (2), GitHubActionsUpdateNotificationHelper.kt. — One of this dimension's main actionable groups (24 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling5.4 / 10Adequate✓ 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.
22 production modules (Gradle), 0 dependency cycle(s), 3 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; 9 module(s) off the main sequence.
Off the main sequence: :core-concurrency · ×9
Unstable project :feature-github · ×3
What to do
Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 3 Unstable project finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppMcpBaToolDelegate.kt, GitHubPageState.kt, GitHubActionsNotificationHistoryRepository.kt. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 28 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 24 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. 14 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 38 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/os/kei/ui/page/main/host/pager/MainPagerLayout.kt (25×32=800); feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt (8×55=440); app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt (16×27=432) Repeated repair below the complexity floor: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.kt (5 of 9 changes were fixes); baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt (4 of 7 changes were fixes); app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.kt (3 of 5 changes were fixes)
Resolve the 45 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainPagerLayout.kt, GitHubReleaseEvaluationEngine.kt, GitHubMainContentSection.kt. — One of this dimension's main actionable groups (45 warning-level).
Resolve the 11 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AppNavigationPlacement.kt, BaselineProfileActions.kt, BaGuideFavoriteBgmMusicContent.kt. — One of this dimension's main actionable groups (11 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 303492 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.
2 of 2 documentation facets pass in full. 54 document(s) read across 23 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.
5 of 23 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×5app/build.gradle.kts:1
What to do
Resolve the 5 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts (5). — One of this dimension's main actionable groups (5 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.
37 % of calls cross a namespace and 1 % 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).
18 finding(s): 0 critical, 0 high, 18 medium, 0 low. semgrep hit a parse error in 3 file(s) — `feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt` (line 29), `gradlew` (line 74, line 178), `scripts/qa/capture_release_fixture.sh` (line 80, lines 81–82) — 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.
REDACTED
REDACTED
What to do
Resolve the 13 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
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.
1 of 1206 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/os/kei/ui/navigation/Navigator.kt. Counted over 1206 of the 1643 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 20 Boundary-crossing change coupling finding(s) in Change Coupling — start with SettingsPage.kt (2), SettingsSectionContractsHost.kt (2), GuideLiquidCard.kt (2). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 55 Change coupling finding(s) in Change Coupling — start with BaActivityCalendarPage.kt (2), GitHubStarImportComponents.kt (2), GitHubMainContentSection.kt (2). — One of this dimension's main actionable groups (55 warning-level).
Resolve the 20 Change-coupling hub finding(s) in Change Coupling — start with BAPage.kt, MainPagerLayout.kt, SettingsPage.kt. — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (REDACTED or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a REDACTED (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d37_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 66 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.
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.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
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 call was found in the 1620 JavaScript/TypeScript, JVM production file(s) this check read across 23 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 2 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. — .github/workflows/ci-debug-apk.yml:21
`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:375
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 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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
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.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 5 plain JS — the untyped files are scripts/ba/test_model_background.mjs, scripts/ba/test_model_parts.mjs, scripts/qa/memory_lobby_player_test.mjs, scripts/qa/model_skin_bounds_test.mjs, scripts/qa/viewer_frame_presentation_test.mjs.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
scripts/qa/viewer_frame_presentation_test.mjs:69 · scripts/qa/viewer_frame_presentation_test.mjs:77 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/qa/viewer_frame_presentation_test.mjs:69
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 1 application, 0 tooling and 3 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
no import path from any entry point (1 application, 0 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — scripts/ba/test_model_background.mjs
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether 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 · 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 functions that make a cancellable request accept or pass on an AbortSignal or 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 2/5 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin 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.
`executeStreaming` suspends, but makes its request with `call.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`. — core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:822
`submitIssueViaApi` 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/os/kei/ui/page/main/feedback/FeedbackIssueRepository.kt:135
`downloadMediaSingleStream` 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/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:657
What to do
Thread an AbortSignal or the coroutine's cancellation through 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 (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.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. 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) — core-notification/src/main/java/os/kei/core/notification/live/oem/honor/HonorOrderFeedbackClient.kt:64, app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmArtworkHydration.kt:37
`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. (×8) — app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:106, app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:125, app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:220, …
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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?
Reference — by lens
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 — 4 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 — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 — ~95324 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 — 24 Maven/Gradle manifest(s) were read, stating a version for 66 dependency(ies) and leaving 14 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. 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.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 45 candidate(s) found and not reported.
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; comments in this repository's .kt, .py source were not judged.
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) and a Gradle version catalogue — 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) — 52 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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) and a Gradle version catalogue — 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 measured — polyglot repository, one half has no runner
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
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
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 2 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'.
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 data present for 2 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — no production JavaScript/TypeScript files to cover (3 test file(s) present) — nothing to measure
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
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.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 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
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
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.
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.
Boundary-crossing change coupling: MainScreenUiPrefsState.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreenUiPrefsState.kt:1— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenUiPrefsState.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 85% of the time (23 of the 27 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 23 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `99a594b5` Add custom background color intensity; `54677791` Add optional background depth motion — run `git show` on any of them.
Boundary-crossing change coupling: MainScreenNavHost.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:1— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 81% of the time (22 of the 27 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `99a594b5` Add custom background color intensity; `54677791` Add optional background depth motion — run `git show` on any of them.
Boundary-crossing change coupling: SettingsPage.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 81% of the time (22 of the 27 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `99a594b5` Add custom background color intensity; `54677791` Add optional background depth motion — run `git show` on any of them.
Boundary-crossing change coupling: GitHubShareImportFlowModels.kt ↔ GitHubShareImportFlowStore.kt app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt:1— `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt` (context main) and `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt` (context feature-github) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `75599f37` feat: add versionCode support to GitHub share import flow for improve… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `6fd3c326` feat: enhance GitHub share import flow with detailed APK manifest met… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `6af77388` feat: enhance GitHub share import with version tracking and improved … (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: GitHubShareImportWindowFlowHost.kt ↔ GitHubShareImportFlowStore.kt app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportWindowFlowHost.kt:1— `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportWindowFlowHost.kt` (context main) and `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt` (context feature-github) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `6fd3c326` feat: enhance GitHub share import flow with detailed APK manifest met… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `545a75c4` feat: implement real-time progress tracking and UI feedback for GitHu… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `620b6806` feat: add support for sending install action in GitHub share import flow (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SettingsPage.kt ↔ UiPrefs.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefs.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 70% of the time (40 of the 57 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 40 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `99a594b5` Add custom background color intensity; `54677791` Add optional background depth motion — run `git show` on any of them.
Boundary-crossing change coupling: GitHubShareImportNotificationHelper.kt ↔ GitHubShareImportFlowStore.kt app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:1— `app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt` (context main) and `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt` (context feature-github) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `6af77388` feat: enhance GitHub share import with version tracking and improved … (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `545a75c4` feat: implement real-time progress tracking and UI feedback for GitHu… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `620b6806` feat: add support for sending install action in GitHub share import flow (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: MiIslandNotificationBuilder.kt ↔ McpNotificationPayload.kt core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:1— `core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt` (context core-notification) and `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt` (context feature-mcp) sit in DIFFERENT parts of the tree yet change together 65% of the time (11 of the 17 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `52875bcf` Add BA cafe AP notifications (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/MiIslandNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `8736c841` feat: refactor GitHub APK install flow phases and improve Xiaomi noti… (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/MiIslandNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `fed32f75` feat: refactor notification dispatching with new Update mode and enha… (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/MiIslandNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SettingsSectionContractAssembler.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 63% of the time (17 of the 27 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `be169cfd` Remove MIUIX bottom bar setting; `7d6e23e9` Refine low-priority toast handling and add interruption toggle (at that commit the file was still `app/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SettingsSectionContracts.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/settings/section/SettingsSectionContracts.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/section/SettingsSectionContracts.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 63% of the time (17 of the 27 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `be169cfd` Remove MIUIX bottom bar setting; `7d6e23e9` Refine low-priority toast handling and add interruption toggle (at that commit the file was still `app/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: GitHubShareImportActionReceiver.kt ↔ GitHubShareImportFlowStore.kt app/src/main/java/os/kei/feature/github/notification/GitHubShareImportActionReceiver.kt:1— `app/src/main/java/os/kei/feature/github/notification/GitHubShareImportActionReceiver.kt` (context main) and `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt` (context feature-github) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `9dcbfca4` Refine non-MCP backend flows (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `620b6806` feat: add support for sending install action in GitHub share import flow (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`); `25825cfa` feat: add target display name handling for GitHub share import notifi… (at that commit the file was still `app/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SettingsSectionContractsHost.kt ↔ UiPrefs.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefs.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 56% of the time (9 of the 16 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `be169cfd` Remove MIUIX bottom bar setting; `7d6e23e9` Refine low-priority toast handling and add interruption toggle (at that commit the file was still `app/src/main/java/os/kei/core/prefs/UiPrefs.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: SettingsSectionContractsHost.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt:1— `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 56% of the time (9 of the 16 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `e451f2c5` feat: add focus notification float controls; `be169cfd` Remove MIUIX bottom bar setting; `7d6e23e9` Refine low-priority toast handling and add interruption toggle (at that commit the file was still `app/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: MainScreenPagerCoordinator.kt ↔ UiPrefsRepository.kt app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt:1— `app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt` (context main) and `core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt` (context core-prefs) sit in DIFFERENT parts of the tree yet change together 55% of the time (12 of the 22 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `99a594b5` Add custom background color intensity; `54677791` Add optional background depth motion; `eb974818` Extend custom background display controls — run `git show` on any of them.
Boundary-crossing change coupling: GitHubPage.kt ↔ GlassEffectRuntime.kt app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt:1— `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt` (context main) and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassEffectRuntime.kt` (context ui-liquid-glass) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `5cc2e6b3` refactor: remove unused bottom bar scroll effect reduction logic acro… (at that commit the file was still `app/src/main/java/os/kei/ui/page/main/widget/glass/GlassEffectRuntime.kt`); `f9a56310` feat: implement backdrop effect reduction during pager scroll for imp… (at that commit the file was still `app/src/main/java/os/kei/ui/page/main/widget/glass/GlassEffectRuntime.kt`); `662fba53` refactor: disable glass effect reduction during pager scroll (at that commit the file was still `app/src/main/java/os/kei/ui/page/main/widget/glass/GlassEffectRuntime.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: LegacyNotificationBuilder.kt ↔ McpNotificationPayload.kt core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:1— `core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt` (context core-notification) and `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt` (context feature-mcp) sit in DIFFERENT parts of the tree yet change together 53% of the time (9 of the 17 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `52875bcf` Add BA cafe AP notifications (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/LegacyNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `fed32f75` feat: refactor notification dispatching with new Update mode and enha… (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/LegacyNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `74777a6a` feat: enhance GitHub share import notifications with improved action … (at that commit the files were still `app/src/main/java/os/kei/mcp/framework/notification/builder/LegacyNotificationBuilder.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`) — run `git show` on any of them.
Boundary-crossing change coupling: BaApNotificationDispatcher.kt ↔ McpNotificationHelper.kt app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt` (context main) and `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` (context feature-mcp) sit in DIFFERENT parts of the tree yet change together 50% of the time (8 of the 16 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `cfb7cc32` fix(ba): make notification delivery commits durable; `d1c0c61a` fix(notification): commit delivery before cancellation; `3ae8f405` fix(notification): await Xiaomi Magic delivery — run `git show` on any of them.
Boundary-crossing change coupling: GuideLiquidCard.kt ↔ LiquidSurfaces.kt app/src/main/java/os/kei/ui/page/main/student/component/GuideLiquidCard.kt:1— `app/src/main/java/os/kei/ui/page/main/student/component/GuideLiquidCard.kt` (context main) and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt` (context ui-liquid-glass) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `fe4fcd8a` fix(glass): drop the card shadow that a scroll clip was squaring off; `e4b72213` refactor(cards): recede stacked cards behind glass instead of fading …; `75f77b5c` Restore liquid card shadow defaults — run `git show` on any of them.
Boundary-crossing change coupling: GuideLiquidCard.kt ↔ AppFeatureCards.kt app/src/main/java/os/kei/ui/page/main/student/component/GuideLiquidCard.kt:1— `app/src/main/java/os/kei/ui/page/main/student/component/GuideLiquidCard.kt` (context main) and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppFeatureCards.kt` (context ui-liquid-glass) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e4b72213` refactor(cards): recede stacked cards behind glass instead of fading …; `75f77b5c` Restore liquid card shadow defaults; `57d5c3cf` Thread liquid card shadow intensity — run `git show` on any of them.
Boundary-crossing change coupling: BaCafeApNotificationDispatcher.kt ↔ McpNotificationHelper.kt app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt` (context main) and `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` (context feature-mcp) sit in DIFFERENT parts of the tree yet 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `cfb7cc32` fix(ba): make notification delivery commits durable; `d1c0c61a` fix(notification): commit delivery before cancellation; `3ae8f405` fix(notification): await Xiaomi Magic delivery — run `git show` on any of them.
MethodTooLong: OsPageKt.OsPage app/src/main/java/os/kei/ui/page/main/os/OsPage.kt:44— MethodTooLong — OsPage runs 540 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 440 over it, 5.40× 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: MainPagerLayoutKt.MainPagerLayout app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt:78— MethodTooLong — MainPagerLayout runs 469 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 369 over it, 4.69× 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: GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:106— MethodTooLong — GitHubActionsNotificationHistoryPage runs 465 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 365 over it, 4.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GitHubMainContentSectionKt.GitHubMainContent app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:75— MethodTooLong — GitHubMainContent runs 461 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 361 over it, 4.61× 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: BaStudentGuidePageKt.BaStudentGuidePage app/src/main/java/os/kei/ui/page/main/student/page/BaStudentGuidePage.kt:102— MethodTooLong — BaStudentGuidePage runs 372 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 272 over it, 3.72× 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: LiquidSliderVariantsKt.LiquidTrackSlider ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:266— MethodTooLong — LiquidTrackSlider runs 355 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 255 over it, 3.55× 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: AboutPageKt.AboutPage app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:70— MethodTooLong — AboutPage runs 349 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 249 over it, 3.49× 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: BaCalendarPoolPageKt.BaCalendarPoolPage app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:81— MethodTooLong — BaCalendarPoolPage runs 336 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 236 over it, 3.36× 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: GuideGalleryTabContentSectionsKt.renderGuideGalleryStateContent app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:36— MethodTooLong — renderGuideGalleryStateContent runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsSearchIndexKt.buildSettingsSearchTargets app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSearchIndex.kt:45— MethodTooLong — buildSettingsSearchTargets runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× 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: GitHubPageSheetHostKt.GitHubPageSheetHost app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageSheetHost.kt:56— MethodTooLong — GitHubPageSheetHost runs 325 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 225 over it, 3.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:124— MethodTooLong — parseGuideDetailFromObjectContentJson runs 325 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 225 over it, 3.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GitHubRefreshBatchActions.refreshTrackedBatchInternal app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubRefreshBatchActions.kt:38— MethodTooLong — refreshTrackedBatchInternal runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× 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: OsGoogleSystemServiceEditorSheetKt.OsGoogleSystemServiceEditorSheet app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceEditorSheet.kt:41— MethodTooLong — OsGoogleSystemServiceEditorSheet runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: DebugLiquidFeedbackCardKt.DebugLiquidFeedbackCard app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidFeedbackCard.kt:59— MethodTooLong — DebugLiquidFeedbackCard runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× 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: BaGuideBgmBottomChromeKt.BaGuideBgmFloatingBottomChrome app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmBottomChrome.kt:64— MethodTooLong — BaGuideBgmFloatingBottomChrome runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× 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: AppLiquidButtonsKt.AppLiquidTextButton ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:545— MethodTooLong — AppLiquidTextButton runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× 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: MiFocusNotificationTemplate.applyExpandedComponent core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:311— MethodTooLong — applyExpandedComponent runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× 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: MainScreenNavHostKt.MainScreenNavHost app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:62— MethodTooLong — MainScreenNavHost runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× 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: GitHubTrackAppPickerContentKt.GitHubTrackAppPickerContent app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackAppPickerContent.kt:271— MethodTooLong — GitHubTrackAppPickerContent runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× 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: AppLiquidSearchFieldKt.AppLiquidInputField ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:53— MethodTooLong — AppLiquidInputField runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× 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: GitHubStrategySheetKt.GitHubStrategySheet app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:58— MethodTooLong — GitHubStrategySheet runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× 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: GitHubReleaseCheckService.evaluateTrackedAppInternal feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:99— MethodTooLong — evaluateTrackedAppInternal runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× 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: GitHubBackgroundRefreshCoordinator.refreshItemsInBackground app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:110— MethodTooLong — refreshItemsInBackground runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× 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: BaPageSheetHostKt.BaPageSheetHost app/src/main/java/os/kei/ui/page/main/ba/BaPageSheetHost.kt:123— MethodTooLong — BaPageSheetHost runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.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.
FileTooLong: focus/MiFocusOfficialTemplateCatalog.kt core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt— FileTooLong — 1087 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 587 over it, 2.17× 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: glass/AppLiquidButtons.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt— FileTooLong — 842 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 342 over it, 1.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: history/GitHubActionsNotificationHistoryPage.kt app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt— FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 337 over it, 1.67× 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: notification/McpNotificationHelper.kt feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt— FileTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 332 over it, 1.66× 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: domain/GitHubReleaseCheckService.kt feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt— FileTooLong — 824 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 324 over it, 1.65× 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: builder/MiIslandNotificationBuilder.kt core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt— FileTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: MiIslandNotificationBuilder (20-1040). The bar is 500 significant lines; this is 321 over it, 1.64× 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: notification/GitHubRefreshNotificationHelper.kt app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 317 over it, 1.63× 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: support/BaSettingsStore.kt app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt— FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 313 over it, 1.63× 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: segmented/SegmentedDownloadClient.kt core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt— FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: SegmentedDownloadClient (36-844). The bar is 500 significant lines; this is 308 over it, 1.62× 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/GitHubTrackStore.kt feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStore.kt— FileTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: GitHubAppPickerPreferences (102-999). The bar is 500 significant lines; this is 299 over it, 1.60× 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: notification/GitHubShareImportNotificationHelper.kt app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt— FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291 over it, 1.58× 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: glass/LiquidSliderVariants.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt— FileTooLong — 789 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 289 over it, 1.58× 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: background/AppForegroundInfoHandler.kt app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt— FileTooLong — 781 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 281 over it, 1.56× 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: history/GitHubRefreshHistoryCards.kt app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt— FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 276 over it, 1.55× 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: glass/AppFloatingSearchDock.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt— FileTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 267 over it, 1.53× 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: student/GuideVideoFullscreenActivity.kt app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt— FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded), about 69% of them inside a single declaration: GuideVideoFullscreenActivity (94-813). The bar is 500 significant lines; this is 256 over it, 1.51× 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: chrome/LiquidGlassBottomBar.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: fdroid/FdroidVersionListPage.kt app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 230 over it, 1.46× 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: release/GitHubReleaseListPage.kt app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 223 over it, 1.45× 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: versioning/VersioningEngine.kt core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt— FileTooLong — 708 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 208 over it, 1.42× 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: component/BaGuideMemoryLobbyCards.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt— FileTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 196 over it, 1.39× 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: glass/LiquidGlassDropdownItems.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 195 over it, 1.39× 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: focus/MiFocusNotificationModels.kt core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationModels.kt— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: debug/DebugLiquidCatalogCard.kt app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 164 over it, 1.33× 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: server/McpSkillContent.kt feature-mcp/src/main/java/os/kei/mcp/server/McpSkillContent.kt— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 156 over it, 1.31× 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.
Change coupling: KeiOsTestTags.kt ↔ BaselineProfileGenerator.kt app/src/main/java/os/kei/ui/testing/KeiOsTestTags.kt:1— `app/src/main/java/os/kei/ui/testing/KeiOsTestTags.kt` and `baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileGenerator.kt` change together 75% of the time (24 of the 32 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 24 shared commits counted here, the most recent 3 are `bf89e5ee` perf(profile): prepare glass and sync journeys; `c39d91df` perf(profile): consolidate journeys and isolate validated collection; `172817e7` perf(profile): make two journeys prove what they reach — run `git show` on any of them.
Change coupling: AboutBottomChrome.kt ↔ SettingsBottomChrome.kt app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:1— `app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt` and `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt` change together 100% of the time (10 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 10 shared commits counted here, the most recent 3 are `810c99a1` UI: implement compact bottom bar dock and expansion logic; `117d5877` Land M8c: extract generic TabbedPageBottomChrome from Settings/About; `2b2fa077` Remove Miuix floating bottom bar toggle, keep liquid glass as default — run `git show` on any of them.
Change coupling: BaActivityCalendarPage.kt ↔ BaPoolPage.kt app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaPoolPage.kt` change together 88% of the time (23 of the 26 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 23 shared commits counted here, the most recent 3 are `470d1473` feat(ba): merge the calendar and pool routes, and split them again on…; `516934ae` feat(background): apply the non-Home background everywhere, and floor…; `7535c7ef` refactor(nav): move the calendar and pool pages onto miuix-nav — run `git show` on any of them.
Change coupling: LegacyNotificationBuilder.kt ↔ ModernNotificationBuilder.kt core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:1— `core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt` and `core-notification/src/main/java/os/kei/core/notification/live/builder/ModernNotificationBuilder.kt` change together 81% of the time (22 of the 27 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 22 shared commits counted here, the most recent 3 are `190d9f19` fix(notification): preserve reminder alert rules; `17f258f5` refactor(notifications): drop ignored layout flag; `5377af60` fix(notification): follow selected launcher icon design — run `git show` on any of them.
Change coupling: GuideVideoFullscreenActivity.kt ↔ GuideVideoPictureInPicture.kt app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt:1— `app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt` and `app/src/main/java/os/kei/ui/page/main/student/GuideVideoPictureInPicture.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 `a9a5e430` Add reusable PIP seek controls; `e52d51cb` Add remembered loop control for memorial lobby PiP; `ac57abb4` Improve memorial lobby picture-in-picture sizing — run `git show` on any of them.
Change coupling: GitHubTrackedItemAssetPanel.kt ↔ GitHubTrackedItemAssetPanelAssetRow.kt app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanel.kt:1— `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanel.kt` and `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt` change together 77% of the time (10 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). 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 10 shared commits counted here, the most recent 3 are `f8dd963d` feat(github): install verified nested release apks; `e88a5269` feat(github): bridge fdroid install assets; `b100855e` Snapshot GitHub asset relative time labels — run `git show` on any of them.
Change coupling: BaGuideBgmAlbumContent.kt ↔ BaGuideBgmAlbumHero.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumContent.kt:1— `app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumContent.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt` change together 75% of the time (12 of the 16 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 12 shared commits counted here, the most recent 3 are `769aeb95` feat(archive): split the Play tab into an album pane and a queue pane; `3c8cd377` fix(ba): inherit favorite album liquid materials; `b9390744` Refactor BA catalog chrome state and remove sync retry sleep — run `git show` on any of them.
Change coupling: BaGuideBgmFavoriteCards.kt ↔ BaGuideBgmMiniPlayer.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmFavoriteCards.kt:1— `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmFavoriteCards.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmMiniPlayer.kt` change together 73% of the time (8 of the 11 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 `a90abcc9` perf(bgm): isolate mini-player playback ticks; `49e149ba` feat: enhance UI components with backdrop support and liquid effects …; `93ebe82f` feat: replace AppLiquid components with AppStandalone variants for im… — run `git show` on any of them.
Change coupling: MainScreen.kt ↔ BottomPage.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt:1— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt` and `app/src/main/java/os/kei/ui/page/main/model/BottomPage.kt` change together 71% of the time (10 of the 14 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 10 shared commits counted here, the most recent 3 are `9c3012b3` Refactor large pages into modular files and rename System to OS (at that commit the files were still `app/src/main/java/com/example/keios/ui/page/main/MainScreen.kt` and `app/src/main/java/com/example/keios/ui/page/main/model/BottomPage.kt`); `5276503a` trans button bar icon (at that commit the files were still `app/src/main/java/com/example/keios/ui/page/main/MainScreen.kt` and `app/src/main/java/com/example/keios/ui/page/main/model/BottomPage.kt`); `4c057411` import ba schale icon (at that commit the files were still `app/src/main/java/com/example/keios/ui/page/main/MainScreen.kt` and `app/src/main/java/com/example/keios/ui/page/main/model/BottomPage.kt`) — run `git show` on any of them.
Change coupling: McpNotificationHelper.kt ↔ McpNotificationPayload.kt feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:1— `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` and `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt` change together 71% of the time (12 of the 17 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 12 shared commits counted here, the most recent 3 are `52875bcf` Add BA cafe AP notifications (at that commit the files were still `app/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `fed32f75` feat: refactor notification dispatching with new Update mode and enha… (at that commit the files were still `app/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`); `26f410a9` docs: add focus open pending intent to notification helpers for enhan… (at that commit the files were still `app/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt` and `app/src/main/java/os/kei/mcp/notification/McpNotificationPayload.kt`) — run `git show` on any of them.
Change coupling: BaStudentGuideFetch.kt ↔ BaStudentGuideStore.kt app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:1— `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt` and `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStore.kt` change together 71% of the time (12 of the 17 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 12 shared commits counted here, the most recent 3 are `276fc5b7` feat(ba): parse migrated Spine memorial lobbies and refresh legacy ca…; `a9670533` Fix BA guide routing races and pool card click mismatches (at that commit the files were still `app/src/main/java/com/example/keios/ui/page/main/student/BaStudentGuideFetch.kt` and `app/src/main/java/com/example/keios/ui/page/main/student/BaStudentGuideStore.kt`); `5703e909` Refactor simulate tab to use parsed simulate sections (at that commit the files were still `app/src/main/java/com/example/keios/ui/page/main/student/BaStudentGuideFetch.kt` and `app/src/main/java/com/example/keios/ui/page/main/student/BaStudentGuideStore.kt`) — run `git show` on any of them.
Change coupling: BaGuideMemoryLobbyTabContent.kt ↔ BaGuideStudentBgmTabContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:1— `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt` change together 71% of the time (12 of the 17 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 12 shared commits counted here, the most recent 3 are `b4d6522e` fix(archive): give the Students, Lobby and Music lanes their own scroll; `fdc7ef37` feat(archive): flow Students, Lobby and Music across two columns on a…; `7937ad92` fix(pad): deliver the background extension effect, asymmetrically — run `git show` on any of them.
Change coupling: GuideGalleryExpressionSection.kt ↔ GuideGalleryVideoGroupControls.kt app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:1— `app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt` and `app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryVideoGroupControls.kt` change together 70% of the time (7 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 7 shared commits counted here, the most recent 3 are `35214ceb` refactor(liquid): reuse dropdown selector in gallery controls; `f441da0e` fix(accessibility): label liquid media icon actions; `c340b5c9` feat(liquid): adopt mature components in app pages — run `git show` on any of them.
Change coupling: BaPageActions.kt ↔ BaPageBindings.kt app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaPageBindings.kt` change together 67% of the time (14 of the 21 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 14 shared commits counted here, the most recent 3 are `2716ad32` Add BA cafe cooldown calibration sheets; `537f3624` Refine BA AP calibration cards; `372def57` Remove legacy BA overview card flow — run `git show` on any of them.
Change coupling: McpSkillContent.kt ↔ McpToolCatalog.kt feature-mcp/src/main/java/os/kei/mcp/server/McpSkillContent.kt:1— `feature-mcp/src/main/java/os/kei/mcp/server/McpSkillContent.kt` and `feature-mcp/src/main/java/os/kei/mcp/server/McpToolCatalog.kt` change together 67% of the time (10 of the 15 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 10 shared commits counted here, the most recent 3 are `e8c32e8a` Add Dev/Codex MCP onboarding tools and docs (at that commit the files were still `app/src/main/java/os/kei/mcp/server/McpSkillContent.kt` and `app/src/main/java/os/kei/mcp/server/McpToolCatalog.kt`); `907b26ab` feat: enhance MCP tool metadata with detailed argument specs and form… (at that commit the files were still `app/src/main/java/os/kei/mcp/server/McpSkillContent.kt` and `app/src/main/java/os/kei/mcp/server/McpToolCatalog.kt`); `ef6938a0` feat: add workflow blueprints and planning tools for enhanced task au… (at that commit the files were still `app/src/main/java/os/kei/mcp/server/McpSkillContent.kt` and `app/src/main/java/os/kei/mcp/server/McpToolCatalog.kt`) — run `git show` on any of them.
Change coupling: GitHubStarImportComponents.kt ↔ GitHubStarImportPage.kt app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportComponents.kt:1— `app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportComponents.kt` and `app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportPage.kt` change together 67% of the time (8 of the 12 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 `b04edd95` fix(github): mature star import liquid controls; `4ae7e5c7` feat: enhance GitHub star import UI with source guide and improved in…; `8d203654` feat: enhance GitHub share import flow with package name handling and… — run `git show` on any of them.
Change coupling: GitHubMainContentSection.kt ↔ GitHubTopBarSection.kt app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:1— `app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt` and `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt` change together 66% of the time (27 of the 41 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 27 shared commits counted here, the most recent 3 are `a113ba96` fix(chrome): stop the pager stealing presses, and finish the toolbar …; `62a71508` feat(github): add installed app list refresh action; `afb4c107` feat: add github debug tools sheet — run `git show` on any of them.
Change coupling: GitHubActionsSheet.kt ↔ GitHubActionsActions.kt app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:1— `app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt` and `app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsActions.kt` change together 64% of the time (9 of the 14 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 9 shared commits counted here, the most recent 3 are `47fee9a6` Split GitHub artifact install and download actions; `5d275ccd` Disable GitHub actions refresh while loading; `fbd7b461` feat: add branch selection functionality for GitHub Actions workflows — run `git show` on any of them.
Change coupling: MainActivityIntentRouting.kt ↔ MainScreen.kt app/src/main/java/os/kei/MainActivityIntentRouting.kt:1— `app/src/main/java/os/kei/MainActivityIntentRouting.kt` and `app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt` change together 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `159b6dbf` refactor(shell): host the shell runner as a nav route; `7535c7ef` refactor(nav): move the calendar and pool pages onto miuix-nav; `ab30cccb` Add WebDAV live notification routing — run `git show` on any of them.
Change coupling: BaActivityCalendarPage.kt ↔ BaCalendarPoolViewModel.kt app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt` change together 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `470d1473` feat(ba): merge the calendar and pool routes, and split them again on…; `2027fbe2` Add BA calendar pool unread badges (at that commit the file was still `app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarActivity.kt`); `09b5dfda` feat: move BA data settings to calendar pool pages (at that commit the file was still `app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarActivity.kt`) — run `git show` on any of them.
Change coupling: GitHubPageDiscoveryRepository.kt ↔ GitHubTrackActions.kt app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageDiscoveryRepository.kt:1— `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageDiscoveryRepository.kt` and `app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt` change together 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `6f84106e` fix(github): honor prerelease options when scanning APK package names; `42ba7e3b` feat(github): expose awaiting release tracking mode; `1ededb89` feat(github): improve fdroid track editor discovery — run `git show` on any of them.
Change coupling: BaOfficeController.kt ↔ BaPageActions.kt app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:1— `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt` change together 62% of the time (13 of the 21 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 13 shared commits counted here, the most recent 3 are `2716ad32` Add BA cafe cooldown calibration sheets; `537f3624` Refine BA AP calibration cards; `372def57` Remove legacy BA overview card flow — run `git show` on any of them.
Change coupling: OsPageEffects.kt ↔ OsPageViewModel.kt app/src/main/java/os/kei/ui/page/main/os/OsPageEffects.kt:1— `app/src/main/java/os/kei/ui/page/main/os/OsPageEffects.kt` and `app/src/main/java/os/kei/ui/page/main/os/OsPageViewModel.kt` change together 60% of the time (9 of the 15 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 9 shared commits counted here, the most recent 3 are `82f0637e` Move About page chrome state into the ViewModel; `41aba62e` Move BA save flows into ViewModel; `d99e149e` Refactor OS page state flow and move shell refresh work into repos — run `git show` on any of them.
Change coupling: WebDavSyncDataPorts.kt ↔ WebDavSyncEngine.kt app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncDataPorts.kt:1— `app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncDataPorts.kt` and `app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncEngine.kt` change together 60% of the time (6 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 6 shared commits counted here, the most recent 3 are `3967c166` fix(webdav): rebaseline BA account auto sync; `45d38a8c` Fix WebDAV auto-sync conflict recovery; `4b224ffb` Merge BA account WebDAV conflicts by account — run `git show` on any of them.
Change coupling: AppTopBar.kt ↔ AppNavigationPlacement.kt app/src/main/java/os/kei/ui/page/main/widget/chrome/AppTopBar.kt:1— `app/src/main/java/os/kei/ui/page/main/widget/chrome/AppTopBar.kt` and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.kt` change together 60% of the time (6 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 6 shared commits counted here, the most recent 3 are `ab2103dc` fix(pad): bring a route's back button in with its own content column; `7937ad92` fix(pad): deliver the background extension effect, asymmetrically; `e232200a` fix(nav): keep the centred tab bar clear of the trailing toolbar — run `git show` on any of them.
Hotspot: app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt:78— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in MainPagerLayoutKt.MainPagerLayout at line 78. 7 of those changes were fix/bug commits, and the other 18 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.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: feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt:65— feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in GitHubReleaseEvaluationEngine.evaluate at line 65. 4 of those changes were fix/bug commits, and the other 4 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.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/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:75— app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in GitHubMainContentSectionKt.GitHubMainContent at line 75. 6 of those changes were fix/bug commits, and the other 10 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt:216— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 78 in LiquidGlassBottomBarKt.LiquidGlassBottomBar at line 216. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:106— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage at line 106. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.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/os/kei/ui/page/main/os/components/OsPageMainList.kt app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.kt:155— app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.kt changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in OsPageMainListKt.OsPageMainList at line 155. 5 of those changes were fix/bug commits, and the other 11 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.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/os/kei/ui/page/main/github/page/GitHubPage.kt app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt:54— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in GitHubPageKt.GitHubPage at line 54. 7 of those changes were fix/bug commits, and the other 8 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.kt:137— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in LiquidSheetKt.LiquidSheetPresentation at line 137. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt:79— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in LiquidSurfacesKt.LiquidSurface at line 79. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.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/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:486— app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in GitHubReleaseListPageKt.GitHubReleaseCard at line 486. 7 of those changes were fix/bug commits, and the other 11 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.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/os/kei/ui/page/main/mcp/McpPage.kt app/src/main/java/os/kei/ui/page/main/mcp/McpPage.kt:52— app/src/main/java/os/kei/ui/page/main/mcp/McpPage.kt changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in McpPageKt.McpPage at line 52. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/mcp/McpPage.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:545— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in AppLiquidButtonsKt.AppLiquidTextButton at line 545. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.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/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:71— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in BaGuideStudentBgmTabContentKt.BaGuideStudentBgmTabContent at line 71. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.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/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt:40— app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in GuideModel3dPlayerKt.GuideModel3dPlayer at line 40. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.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/os/kei/ui/page/main/about/page/AboutPage.kt app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:70— app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in AboutPageKt.AboutPage at line 70. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:73— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in BaGuideMemoryLobbyTabContentKt.BaGuideMemoryLobbyTabContent at line 73. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:266— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in LiquidSliderVariantsKt.LiquidTrackSlider at line 266. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.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/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.kt app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.kt:63— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in GitHubTrackedItemMoreMenuKt.GitHubTrackedItemMoreActions at line 63. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:53— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in AppLiquidSearchFieldKt.AppLiquidInputField at line 53. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:59— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in BaGuideCatalogV2ListContentKt.BaGuideCatalogV2ListContent at line 59. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.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/os/kei/ui/page/main/settings/page/SettingsPage.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:69— app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SettingsPageKt.SettingsPage at line 69. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.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/os/kei/ui/page/main/host/main/MainScreen.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt:31— app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in MainScreenKt.MainScreen at line 31. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.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/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt:52— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in GuideWebMemoryLobbyPlayerKt.GuideWebMemoryLobbyPlayer at line 52. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.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/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:50— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in GitHubTrackEditFormContentKt.GitHubTrackEditFormContent at line 50. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:526— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FdroidVersionListPageKt.FdroidVersionCard at line 526. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.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: GitHubPageActions app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageActions.kt:45— TooManyMethods — 176 methods. The bar is 30 methods; this is 146 over it, 5.87× 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: BASettingsStore app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:13— TooManyMethods — 157 methods. The bar is 30 methods; this is 127 over it, 5.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.
TooManyMethods: GitHubPageRepository app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRepository.kt:136— TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× 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: UiPrefs core-prefs/src/main/java/os/kei/core/prefs/UiPrefs.kt:159— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: OsPageViewModel app/src/main/java/os/kei/ui/page/main/os/OsPageViewModel.kt:39— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× 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: BaGuideCatalogViewModel app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogViewModel.kt:49— TooManyMethods — 60 methods. The bar is 30 methods; this is 30 over it, 2.00× 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: WebDavSyncPersistence app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncStore.kt:27— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: MiFocusOfficialTemplatePresets core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:261— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: GitHubTrackActions app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:38— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: McpPageViewModel app/src/main/java/os/kei/ui/page/main/mcp/McpPageViewModel.kt:112— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: BaOfficeViewModel app/src/main/java/os/kei/ui/page/main/ba/BaOfficeViewModel.kt:28— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: VersioningEngine core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt:6— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: GitHubTrackStore feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStore.kt:111— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: BaOfficeRepository app/src/main/java/os/kei/ui/page/main/ba/BaOfficeRepository.kt:13— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GitHubActionsNightlyLinkRepository feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:22— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: OsShellRunnerViewModel app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerViewModel.kt:29— 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: GitHubConfigActions app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubConfigActions.kt:23— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 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.
TooManyMethods: BaCalendarPoolImageCache REDACTED:24— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsPageViewModel app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:139— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BaStudentGuideViewModel app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideViewModel.kt:82— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BaOfficeController app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:71— 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: GitHubShareImportNotificationHelper app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:33— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 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.
TooManyMethods: UiPrefsRepository core-prefs/src/main/java/os/kei/core/prefs/UiPrefsRepository.kt:15— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 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.
TooManyMethods: BaAccountStore app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:27— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainScreenPrefsViewModel app/src/main/java/os/kei/ui/page/main/host/main/MainScreenPrefsViewModel.kt:23— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MiIslandNotificationBuilder core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:20— ClassTooLong — 804 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 404 over it, 2.01× 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: GitHubAppPickerPreferences feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStore.kt:102— ClassTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 287 over it, 1.72× 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: SegmentedDownloadClient core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:36— ClassTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 245 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HtmlReleaseMetadata feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:23— ClassTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 228 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubActionsNightlyLinkRepository feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:22— ClassTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 218 over it, 1.55× 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: MiFocusExpandedComponent core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:3— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 203 over it, 1.51× 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: BaOfficeController app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:71— ClassTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 187 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.
ClassTooLong: GitHubTrackActions app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:38— ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 149 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: RemoteZipEntryReader feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:44— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 132 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BaOfficeViewModel app/src/main/java/os/kei/ui/page/main/ba/BaOfficeViewModel.kt:28— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 121 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GuideVideoFullscreenActivity app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt:94— ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 118 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubActionsRepository feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:24— ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 118 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BaGuideCatalogViewModel app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogViewModel.kt:49— ClassTooLong — 497 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 97 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubPageActions app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageActions.kt:45— ClassTooLong — 481 significant lines (blank, comment-only and punctuation-only lines excluded), 176 methods. The bar is 400 significant lines; this is 81 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppMcpBaToolDelegate app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:42— ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubReleaseNotesActions app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubReleaseNotesActions.kt:26— ClassTooLong — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 73 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GitHubDeepRepositoryProfileSource feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:27— ClassTooLong — 471 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 71 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OsPageViewModel app/src/main/java/os/kei/ui/page/main/os/OsPageViewModel.kt:39— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 65 over it, 1.16× 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: BaStudentGuideViewModel app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideViewModel.kt:82— ClassTooLong — 463 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 63 over it, 1.16× 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: GitHubTrackedRefreshSlowItem feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:115— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 60 over it, 1.15× 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: McpXiaomiMagicDispatchEnvironment feature-mcp/src/main/java/os/kei/mcp/notification/McpXiaomiMagicDispatcher.kt:29— ClassTooLong — 456 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 56 over it, 1.14× 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: GitHubDirectApkReleaseCheckSource feature-github/src/main/java/os/kei/feature/github/domain/GitHubDirectApkReleaseCheckSource.kt:33— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 50 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.
ClassTooLong: OsPageMainListSearchDockState app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.kt:145— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 39 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: WebDavSyncViewModel app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:19— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 32 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BaGuideBgmPlaybackCoordinator app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackCoordinator.kt:122— ClassTooLong — 431 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 31 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:177— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:177-186 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:246-255 — 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/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:177` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaStandaloneActivitySupport.kt:30— app/src/main/java/os/kei/ui/page/main/ba/BaStandaloneActivitySupport.kt:30-40 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportActivity.kt:142-151 — 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/os/kei/ui/page/main/ba/BaStandaloneActivitySupport.kt:30` 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/os/kei/ui/page/main/ba/support/BaAccountStore.kt:239— app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:239-248 | app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:268-277 — 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/back/BackNavigationRuntime.kt:239— app/src/main/java/os/kei/ui/page/main/back/BackNavigationRuntime.kt:239-248 | app/src/main/java/os/kei/ui/page/main/back/BackNavigationRuntime.kt:365-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `enabled` to `Boolean = true` in one and `Boolean` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:96— app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:96-105 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:623-632 — 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/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:96` 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:917— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:917-926 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:381-390 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:917` 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/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:167— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:167-176 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:241-250 — 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:167— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:167-176 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:179-188 — 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. 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:253— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:253-262 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:334-343 — 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/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:253` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:76— REDACTED:76-85 | REDACTED:121-130 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:200— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:200-209 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:200-209 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt` as WHOLE FILES: this scan already matched 4 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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:198` calls `readyItemOrNull` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:198` 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:50— app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:50-59 | app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:171-180 — 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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:50` 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) core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:38— core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:38-47 | core-notification/src/main/java/os/kei/core/notification/live/builder/ModernNotificationBuilder.kt:37-46 — 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 `core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:38` 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 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubAtomHeuristics.kt:139— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubAtomHeuristics.kt:139-148 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubVersionUtils.kt:284-293 — 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 (10 lines × 2) REDACTED:239— REDACTED:239-248 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:271-280 — 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 `REDACTED:239` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:241— feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:241-250 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:253-262 — 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. 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 (10 lines × 2) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:327— feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:327-336 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:339-348 — 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. 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 (10 lines × 2) REDACTED:73— REDACTED:73-82 | REDACTED:77-86 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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 `REDACTED:73` 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/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:224— app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:224-233 | app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:269-278 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (10 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCafeApToolsSheet.kt:162— app/src/main/java/os/kei/ui/page/main/ba/BaCafeApToolsSheet.kt:162-171 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeCooldownEditSheet.kt:241-250 — 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/os/kei/ui/page/main/ba/BaCafeApToolsSheet.kt:162` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerPageStateHolder.kt:117— app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerPageStateHolder.kt:117-126 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPageStateHolder.kt:242-251 — 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/os/kei/ui/page/main/os/shell/page/OsShellRunnerPageStateHolder.kt:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayParseAccumulator.kt:74— app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayParseAccumulator.kt:74-83 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayParseAccumulator.kt:84-93 — 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/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayParseAccumulator.kt:74` 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/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:295— app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:295-304 | app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:335-344 — 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/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:295` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:218— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:218-227 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:237-246 — 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/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:218` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:94— app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:94-103 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:174-183 — 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/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:94` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:104` calls `isNotBlank` and `app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:184` 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 (7 lines × 2) app/src/main/java/os/kei/core/background/AppBackgroundRecoveryStore.kt:34— app/src/main/java/os/kei/core/background/AppBackgroundRecoveryStore.kt:34-40 | app/src/main/java/os/kei/core/background/AppBackgroundRecoveryStore.kt:53-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) app/src/main/java/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:141— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:141-147 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:336-342 — 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. 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:166— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:166-173 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:157-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.
Duplicated block (7 lines × 2) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:318— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:318-324 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:339-345 — 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/os/kei/ui/page/main/github/importer/GitHubStarImportModels.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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBackGesture.kt:76— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBackGesture.kt:76-82 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryFullscreenBackGesture.kt:39-45 — 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/os/kei/ui/page/main/host/pager/MainPagerBackGesture.kt:76` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/os/OsPageSectionController.kt:214— app/src/main/java/os/kei/ui/page/main/os/OsPageSectionController.kt:214-220 | app/src/main/java/os/kei/ui/page/main/os/OsPageSectionController.kt:279-286 — 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/os/kei/ui/page/main/os/OsPageSectionController.kt:214` 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideReleaseDateParser.kt:47— app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideReleaseDateParser.kt:47-53 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideReleaseDateParser.kt:56-62 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:104— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:104-110 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:115-121 — 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/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:104` 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:132— app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:132-138 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:519-525 — 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/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:132` 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:269— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:269-275 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:323-329 — 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/os/kei/ui/page/main/sync/WebDavSyncCards.kt:269` 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 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidProgressBars.kt:437— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidProgressBars.kt:437-443 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:861-867 — 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:136— app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:136-142 | app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:281-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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:136` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:791— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:791-797 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncPlanDialog.kt:281-287 — 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 (7 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:264— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:264-270 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:460-466 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:298— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:298-304 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:336-342 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:201— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:201-207 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkVersionedDirectoryResolver.kt:127-133 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:201` 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 lines × 2) REDACTED:480— REDACTED:480-486 | REDACTED:83-89 — 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:1004— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:1004-1010 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:925-931 — 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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:1004` 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) core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:118— core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:118-124 | core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:1027-1033 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:636— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:636-642 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:484-490 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:565— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:565-571 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsUpdateCheckService.kt:161-167 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:565` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRemoteBridge.kt:128— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRemoteBridge.kt:128-134 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRemoteBridge.kt:164-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:121— app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:121-127 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:144-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/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:121` 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/os/OsPageCardHelpers.kt:12— app/src/main/java/os/kei/ui/page/main/os/OsPageCardHelpers.kt:12-18 | app/src/main/java/os/kei/ui/page/main/os/store/OsInfoCacheStore.kt:197-203 — 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 (7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:92— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:92-98 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:210-216 — 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 (9 lines × 2) app/src/main/java/os/kei/feature/github/notification/GitHubActionsUpdateNotificationHelper.kt:93— app/src/main/java/os/kei/feature/github/notification/GitHubActionsUpdateNotificationHelper.kt:93-101 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:616-624 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/support/BaPageMath.kt:128— app/src/main/java/os/kei/ui/page/main/ba/support/BaPageMath.kt:128-136 | app/src/main/java/os/kei/ui/page/main/ba/support/BaPageMath.kt:159-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.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:723— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:723-731 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:684-692 — 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 (9 lines × 2) app/src/main/java/os/kei/ui/page/main/home/HomePageSections.kt:222— app/src/main/java/os/kei/ui/page/main/home/HomePageSections.kt:222-230 | app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:202-210 — 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/os/kei/ui/page/main/home/HomePageSections.kt:222` 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 × 2) app/src/main/java/os/kei/ui/page/main/os/shell/OsShellCommandCardCodec.kt:62— app/src/main/java/os/kei/ui/page/main/os/shell/OsShellCommandCardCodec.kt:62-70 | app/src/main/java/os/kei/ui/page/main/os/shortcut/OsActivityShortcutCardCodec.kt:48-56 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) REDACTED:405— REDACTED:405-413 | REDACTED:240-248 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 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 (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:237— app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:237-245 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileFieldRules.kt:308-316 — 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 (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:221— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:221-229 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:234-242 — 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/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:221` 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 × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:41— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:41-49 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionViewBuilders.kt:163-171 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionViewBuilders.kt:106— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionViewBuilders.kt:106-114 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionViewBuilders.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/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionViewBuilders.kt:106` 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) REDACTED:263— REDACTED:263-271 | REDACTED:291-299 — 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 `REDACTED:263` 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 × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:216— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:216-224 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:201-209 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:216` 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 × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:248— app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:248-256 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:444-452 — 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/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:41— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:41-49 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:433-441 — 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/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:41` 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 (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:84— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:84-92 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:175-183 — 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/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:84` 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 (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:87— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:87-95 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:241-249 — 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/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) REDACTED:391— REDACTED:391-399 | REDACTED:226-234 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:229— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:229-237 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:229-237 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (9 lines × 2) core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:312— core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:312-320 | core-system/src/main/java/os/kei/core/shizuku/service/KeiShizukuUserService.kt:279-287 — 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 (9 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:24— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:24-32 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkVersionedDirectoryResolver.kt:23-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsBranchSelector.kt:208— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsBranchSelector.kt:208-216 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRunSelector.kt:288-296 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseApiClient.kt:183— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseApiClient.kt:183-192 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:545-553 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseApiClient.kt:183` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:228— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:228-237 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:409-417 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:228` 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 × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:174— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:174-182 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkJsonFallbackResolver.kt:46-54 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:174` 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/os/kei/ui/page/main/about/page/AboutPage.kt:414— app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:414-426 | app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPageContent.kt:81-93 — 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/os/kei/ui/page/main/about/page/AboutPage.kt:414` 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/os/kei/ui/page/main/ba/card/BaCardCommon.kt:62— app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:62-74 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppCardHeaders.kt:75-87 — 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. Note first that the copies are not typed on the same thing: `R` names `os.kei.R` in one and `os.kei.ui.liquidglass.R` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:720— app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:720-732 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:782-794 — 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/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:720` 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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:962— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:962-974 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:897-909 — 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 (13 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:416— app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:416-428 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryDiagnostics.kt:131-143 — 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/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:416` 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/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:101— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:101-113 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:260-272 — 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/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:101` 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/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:164— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:164-176 | app/src/main/java/os/kei/ui/page/main/os/components/OsImportPreviewDialog.kt:217-229 — 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/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:164` 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:128— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:128-140 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:170-182 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) app/src/main/java/os/kei/ui/page/main/mcp/dialog/McpConfirmDialogs.kt:62— app/src/main/java/os/kei/ui/page/main/mcp/dialog/McpConfirmDialogs.kt:62-74 | app/src/main/java/os/kei/ui/page/main/os/components/OsDeleteConfirmDialogs.kt:45-57 — 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/os/kei/ui/page/main/mcp/dialog/McpConfirmDialogs.kt:62` 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/os/kei/ui/page/main/mcp/skill/component/McpSkillSectionCard.kt:60— app/src/main/java/os/kei/ui/page/main/mcp/skill/component/McpSkillSectionCard.kt:60-72 | app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownContent.kt:327-339 — 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 (13 lines × 2) app/src/main/java/os/kei/ui/page/main/os/shell/OsShellCommandCardImportExport.kt:51— app/src/main/java/os/kei/ui/page/main/os/shell/OsShellCommandCardImportExport.kt:51-63 | app/src/main/java/os/kei/ui/page/main/os/shell/OsShellCommandCardImportExport.kt:95-107 — 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/os/kei/ui/page/main/os/shell/OsShellCommandCardImportExport.kt:51` 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/os/kei/ui/page/main/os/shell/page/OsShellRunnerContent.kt:89— app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerContent.kt:89-101 | app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerContent.kt:120-133 — 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/os/kei/ui/page/main/os/shell/page/OsShellRunnerContent.kt:89` 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 (13 lines × 2) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsNotifySection.kt:115— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsNotifySection.kt:115-127 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsNotifySection.kt:147-159 — 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/os/kei/ui/page/main/settings/section/SettingsNotifySection.kt:115` 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/os/kei/ui/page/main/student/media/GuideMediaImageLoader.kt:221— app/src/main/java/os/kei/ui/page/main/student/media/GuideMediaImageLoader.kt:221-233 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileLinkTitleLoader.kt:143-155 — 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 (13 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:77— app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:77-89 | app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:194-206 — 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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:77` 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/os/kei/ui/page/main/student/section/GuideSectionVoice.kt:79— app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionVoice.kt:79-91 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryVideoSection.kt:197-209 — 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/os/kei/ui/page/main/student/section/GuideSectionVoice.kt:79` 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) REDACTED:47— REDACTED:47-59 | REDACTED:41-53 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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 `REDACTED:47` 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:93— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:93-105 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidMenuSurface.kt:147-159 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:93` 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdown.kt:318— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdown.kt:318-330 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdown.kt:359-371 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdown.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 (13 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:730— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:730-742 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncHistoryCards.kt:355-367 — 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/os/kei/ui/page/main/sync/WebDavSyncHistoryCards.kt:355` 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/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:90— app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:90-102 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:108-120 — 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/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:90` 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/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:27— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:27-39 | app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:139-151 — 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/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:285— app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:285-297 | app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:311-323 — 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/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:285` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:451— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:451-461 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:477-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:275— app/src/main/java/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:275-285 | app/src/main/java/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:312-322 — 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/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:275` 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 (11 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:179— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:179-189 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:253-263 — 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/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.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 (11 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryScanCandidateRows.kt:138— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryScanCandidateRows.kt:138-148 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFdroidDiscoverySection.kt:489-499 — 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/os/kei/ui/page/main/github/sheet/GitHubRepositoryScanCandidateRows.kt:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/home/HomePageChrome.kt:441— app/src/main/java/os/kei/ui/page/main/home/HomePageChrome.kt:441-451 | app/src/main/java/os/kei/ui/page/main/home/HomePageChrome.kt:579-589 — 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/os/kei/ui/page/main/home/HomePageChrome.kt:441` 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 (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaValidation.kt:39— app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaValidation.kt:39-49 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:138-148 — 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/os/kei/ui/page/main/student/BaGuideTempMediaValidation.kt:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:61— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:61-71 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:152-162 — 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/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:61` 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 (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCard.kt:76— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCard.kt:76-86 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:217-227 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCard.kt:76` 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCardState.kt:92— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCardState.kt:92-102 | app/src/main/java/os/kei/ui/page/main/widget/support/TextCopySupport.kt:58-68 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCardState.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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `copyPayload` to `String ): (` in one and `String): ((` 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 (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHeroVisuals.kt:139— app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHeroVisuals.kt:139-149 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHeroVisuals.kt:188-198 — 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/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHeroVisuals.kt:139` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:391— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:391-401 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/GuideTabVoiceSupport.kt:59-69 — 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/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:391` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:606— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:606-617 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideNpcSatelliteArchiveContent.kt:39-49 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:606` 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 (11 lines × 2) core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:58— core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:58-68 | core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:93-103 — 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 `core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) REDACTED:29— REDACTED:29-39 | REDACTED:32-42 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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 `REDACTED:29` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) REDACTED:45— REDACTED:45-55 | REDACTED:48-58 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `record` to `GitHubActionsDownloadRecord` in one and `GitHubActionsNotificationHistoryRecord` 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 (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:379— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:379-389 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:425-435 — 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 `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:379` 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 (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:67— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:67-77 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkVersionedDirectoryResolver.kt:64-74 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:141— feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:141-151 | feature-github/src/main/java/os/kei/feature/github/install/GitHubShizukuPackageInstaller.kt:221-232 — 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 `feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:141` 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 (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:213— feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:213-223 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:303-313 — 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 `feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:213` 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) feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:468— feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:468-478 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:779-789 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:337— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:337-347 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:484-494 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:438— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:438-448 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncHistoryCards.kt:101-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:525— feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:525-535 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:542-552 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:525` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:43— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:43-58 | app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:95-110 — 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/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:43` 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/os/kei/ui/page/main/ba/BaSettingsSheet.kt:162— app/src/main/java/os/kei/ui/page/main/ba/BaSettingsSheet.kt:162-177 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferActions.kt:126-141 — 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/os/kei/ui/page/main/ba/BaSettingsSheet.kt:162` 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 (16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/GitHubAppSelectionRows.kt:217— app/src/main/java/os/kei/ui/page/main/github/GitHubAppSelectionRows.kt:217-232 | app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutActivityIcon.kt:55-70 — 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/os/kei/ui/page/main/os/shortcut/OsShortcutActivityIcon.kt:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:277— app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:277-292 | app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:306-321 — 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/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:277` 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 (16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:89— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:89-104 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:214-229 — 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/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:89` 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/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:52— app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:52-67 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:305-320 — 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/os/kei/ui/page/main/github/section/GitHubPendingShareImportSection.kt:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:120— app/src/main/java/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:120-135 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:239-254 — 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/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:120` 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/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:208— app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:208-223 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:289-304 — 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/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:208` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:117— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:117-132 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:138-153 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:117` 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:226— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:226-241 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:279-294 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:605— app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:605-620 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncHistory.kt:86-101 — 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/os/kei/ui/page/main/sync/WebDavAutoSync.kt:605` 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) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:213— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:213-228 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:423-438 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:213` 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 (16 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:335— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:335-350 | feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:380-395 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `centralDirectoryOffset` to `eocdAbsoluteOffset >=` in one and `eocdRelativeOffset >=` 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 (16 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:477— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:477-492 | feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:348-363 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:477` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:335— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:335-350 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:866-881 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:335` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:864` calls `contains` and `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:334` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:471— feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:471-486 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:499-514 — 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 `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:471` 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:163— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:163-178 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:333-348 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.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 (16 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:418— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:418-433 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:546-561 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:418` 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/os/kei/ui/page/main/github/page/action/GitHubActionsArtifactActions.kt:39— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsArtifactActions.kt:39-54 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsArtifactActions.kt:139-154 — 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/os/kei/ui/page/main/github/page/action/GitHubActionsArtifactActions.kt:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:102— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:102-117 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:180-195 — 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 (16 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:392— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:392-407 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:466-481 — 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 `feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:392` 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/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:83— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:83-98 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:192-207 — 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/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:83` 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 (5 lines × 2) app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogSamples.kt:183— app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogSamples.kt:183-187 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogSamples.kt:189-193 — 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/os/kei/ui/page/main/debug/DebugLiquidCatalogSamples.kt:183` 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 (5 lines × 2) app/src/main/java/os/kei/ui/page/main/os/shortcut/OsBuiltInActivityShortcutCards.kt:22— app/src/main/java/os/kei/ui/page/main/os/shortcut/OsBuiltInActivityShortcutCards.kt:22-26 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:84-94 — 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. 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 × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:52— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:52-56 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:204-208 — 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 (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:87— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:87-91 | REDACTED:106-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:192— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:192-198 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:178-182 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:192` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueVisuals.kt:10— app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueVisuals.kt:10-14 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPresentation.kt:82-86 — 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/os/kei/ui/page/main/feedback/FeedbackIssueVisuals.kt:26— app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueVisuals.kt:26-30 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPresentation.kt:90-94 — 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/os/kei/ui/page/main/settings/section/SettingsAccessibilityGuardSection.kt:261— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsAccessibilityGuardSection.kt:261-265 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:723-727 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) core-download/src/main/java/os/kei/core/download/segmented/PartScheduler.kt:695— core-download/src/main/java/os/kei/core/download/segmented/PartScheduler.kt:695-699 | core-download/src/main/java/os/kei/core/download/segmented/RangeRetryPolicy.kt:72-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:431— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:431-435 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:459-463 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:172— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:172-176 | REDACTED:77-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:257— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:257-261 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:527-531 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:452— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:452-456 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:521-525 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:136— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:136-140 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:691-695 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:200— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:200-204 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:184-188 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:206— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:206-210 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:190-194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:117— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:117-121 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:133-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:228— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:228-232 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:253-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:77— app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:77-81 | app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:207-211 — 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 (5 lines × 2) core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:164— core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:164-168 | core-download/src/main/java/os/kei/core/download/segmented/RangeProbe.kt:155-159 — 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. 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 (5 lines × 2) REDACTED:131— REDACTED:131-135 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubActionsRecommendedRunStore.kt:114-118 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubActionsRecommendedRunStore.kt:111` calls `optString`, `trim` and `REDACTED:130` 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 (5 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:310— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:310-314 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:591-595 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `size` to `ceil(materialSize.height).toInt() + 2) layer.compositingStrategy = if (materialSize !=` in one and `) layer.compositingStrategy = if (materialSize !=` 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.
Change-coupling hub: BAPage.kt → BaNotificationSettingsSheet.kt, BaOfficeActionCoordinator.kt, BaPageActions.kt, BaPageBindings.kt, BaPageContent.kt, BaPageEffects.kt, BaPageSheetHost.kt, BaPageUiController.kt, BaSettingsSheet.kt, BaTopBar.kt app/src/main/java/os/kei/ui/page/main/ba/BAPage.kt— `app/src/main/java/os/kei/ui/page/main/ba/BAPage.kt` changes together with 10 other files — `app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeActionCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageBindings.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageContent.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageEffects.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageSheetHost.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageUiController.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaSettingsSheet.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaTopBar.kt` — none of which declares a dependency on it: one file is the hub of 10 separate couplings, not 10 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 10.
Change-coupling hub: MainPagerLayout.kt → MainActivityIntentRouting.kt, MainScreenPrefsViewModel.kt, MainScreenPagerCoordinator.kt, MainPageRuntime.kt, MainPagerBottomBar.kt, MainPagerCoordinator.kt, MainPagerHomeOverviewState.kt, MainPagerTabJumpController.kt, SettingsBottomChrome.kt, AppManagedBackground.kt app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt— `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt` changes together with 10 other files — `app/src/main/java/os/kei/MainActivityIntentRouting.kt`, `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenPrefsViewModel.kt`, `app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPageRuntime.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerHomeOverviewState.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerTabJumpController.kt`, `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt`, `app/src/main/java/os/kei/ui/page/main/widget/chrome/AppManagedBackground.kt` — none of which declares a dependency on it: one file is the hub of 10 separate couplings, not 10 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 10.
Change-coupling hub: SettingsPage.kt → AboutPage.kt, MainScreenPrefsViewModel.kt, MainScreenUiPrefsState.kt, MainScreenPagerCoordinator.kt, SettingsBottomChrome.kt, SettingsSearchIndex.kt, SettingsBackgroundSection.kt, SettingsSectionContractAssembler.kt, SettingsPageSupport.kt app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt— `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt` changes together with 9 other files — `app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt`, `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenPrefsViewModel.kt`, `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenUiPrefsState.kt`, `app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt`, `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSearchIndex.kt`, `app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt`, `app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt`, `app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPageSupport.kt` — none of which declares a dependency on it: one file is the hub of 9 separate couplings, not 9 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 9.
Change-coupling hub: HomePage.kt → HomePageChrome.kt, HomePageContentDeriver.kt, HomePageContentState.kt, HomePageDerivedState.kt, MainPagerHomeOverviewState.kt, BottomPage.kt app/src/main/java/os/kei/ui/page/main/home/HomePage.kt— `app/src/main/java/os/kei/ui/page/main/home/HomePage.kt` changes together with 6 other files — `app/src/main/java/os/kei/ui/page/main/home/HomePageChrome.kt`, `app/src/main/java/os/kei/ui/page/main/home/state/HomePageContentDeriver.kt`, `app/src/main/java/os/kei/ui/page/main/home/state/HomePageContentState.kt`, `app/src/main/java/os/kei/ui/page/main/home/state/HomePageDerivedState.kt`, `app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerHomeOverviewState.kt`, `app/src/main/java/os/kei/ui/page/main/model/BottomPage.kt` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: OsPageScaffold.kt → BaTopBar.kt, GitHubMainContentSection.kt, GitHubTopBarSection.kt, McpPage.kt app/src/main/java/os/kei/ui/page/main/os/OsPageScaffold.kt— `app/src/main/java/os/kei/ui/page/main/os/OsPageScaffold.kt` changes together with 4 other files — `app/src/main/java/os/kei/ui/page/main/ba/BaTopBar.kt`, `app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt`, `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt`, `app/src/main/java/os/kei/ui/page/main/mcp/McpPage.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: MainScreenNavHost.kt → MainActivityIntentRouting.kt, SettingsSearchIndex.kt, SettingsSectionContractsHost.kt, SettingsSectionContracts.kt, SettingsSectionContractAssembler.kt, SettingsPageSupport.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt` changes together with 6 other files — `app/src/main/java/os/kei/MainActivityIntentRouting.kt`, `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSearchIndex.kt`, `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt`, `app/src/main/java/os/kei/ui/page/main/settings/section/SettingsSectionContracts.kt`, `app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt`, `app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPageSupport.kt` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: GitHubPage.kt → GitHubPageComponents.kt, GitHubAssetUtils.kt, GitHubPageContentStateDeriver.kt, GitHubPageEffects.kt, GitHubPageActionEnvironment.kt, GitHubMainContentSection.kt app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt— `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt` changes together with 6 other files — `app/src/main/java/os/kei/ui/page/main/github/GitHubPageComponents.kt`, `app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt`, `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt`, `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageEffects.kt`, `app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubPageActionEnvironment.kt`, `app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: BaOfficeUiState.kt → BaOfficeActionCoordinator.kt, BaOfficePageRepository.kt, BaPageBindings.kt app/src/main/java/os/kei/ui/page/main/ba/BaOfficeUiState.kt— `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeUiState.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeActionCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaOfficePageRepository.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageBindings.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: MainScreenUiPrefsState.kt → SettingsSectionContractsHost.kt, SettingsSectionContracts.kt, SettingsSectionContractAssembler.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreenUiPrefsState.kt— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenUiPrefsState.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt`, `app/src/main/java/os/kei/ui/page/main/settings/section/SettingsSectionContracts.kt`, `app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: GitHubShareImportWindowFlowHost.kt → GitHubShareImportActionReceiver.kt, GitHubShareImportActivity.kt, GitHubShareImportFlowModels.kt, GitHubShareImportSheets.kt app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportWindowFlowHost.kt— `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportWindowFlowHost.kt` changes together with 4 other files — `app/src/main/java/os/kei/feature/github/notification/GitHubShareImportActionReceiver.kt`, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportActivity.kt`, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt`, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportSheets.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: GitHubShareImportNotificationHelper.kt → GitHubShareImportActionReceiver.kt, GitHubShareImportFlowCoordinator.kt, GitHubShareImportFlowModels.kt app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt— `app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt` changes together with 3 other files — `app/src/main/java/os/kei/feature/github/notification/GitHubShareImportActionReceiver.kt`, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: MainScreenPrefsViewModel.kt → SettingsSectionContractsHost.kt, SettingsSectionContracts.kt, SettingsSectionContractAssembler.kt app/src/main/java/os/kei/ui/page/main/host/main/MainScreenPrefsViewModel.kt— `app/src/main/java/os/kei/ui/page/main/host/main/MainScreenPrefsViewModel.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSectionContractsHost.kt`, `app/src/main/java/os/kei/ui/page/main/settings/section/SettingsSectionContracts.kt`, `app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: BaStudentGuidePage.kt → BaStudentGuideStore.kt, BaStudentGuideBottomBar.kt, BaStudentGuidePagerContent.kt app/src/main/java/os/kei/ui/page/main/student/page/BaStudentGuidePage.kt— `app/src/main/java/os/kei/ui/page/main/student/page/BaStudentGuidePage.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStore.kt`, `app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideBottomBar.kt`, `app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerContent.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: OsPage.kt → OsPageModels.kt, OsPageScaffold.kt, OsPageOverlayHost.kt, OsSectionUi.kt, OsPageUiContext.kt app/src/main/java/os/kei/ui/page/main/os/OsPage.kt— `app/src/main/java/os/kei/ui/page/main/os/OsPage.kt` changes together with 5 other files — `app/src/main/java/os/kei/ui/page/main/os/OsPageModels.kt`, `app/src/main/java/os/kei/ui/page/main/os/OsPageScaffold.kt`, `app/src/main/java/os/kei/ui/page/main/os/components/OsPageOverlayHost.kt`, `app/src/main/java/os/kei/ui/page/main/os/components/OsSectionUi.kt`, `app/src/main/java/os/kei/ui/page/main/os/state/OsPageUiContext.kt` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: BaGuideCatalogV2ListContent.kt → BaGuideMemoryLobbyTabContent.kt, BaGuideStudentBgmTabContent.kt, BaGuideCatalogTabListState.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt— `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogTabListState.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: BaPageUiController.kt → BaOfficeActionCoordinator.kt, BaOfficePageRepository.kt, BaOfficeViewModel.kt, BaPageActions.kt app/src/main/java/os/kei/ui/page/main/ba/BaPageUiController.kt— `app/src/main/java/os/kei/ui/page/main/ba/BaPageUiController.kt` changes together with 4 other files — `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeActionCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaOfficePageRepository.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaOfficeViewModel.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: GitHubTrackEditFormContent.kt → GitHubPageState.kt, GitHubTrackActions.kt, GitHubTrackEditSheet.kt app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt— `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt` changes together with 3 other files — `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt`, `app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt`, `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: BaGuideCatalogPage.kt → BaGuideBgmPlaybackCoordinator.kt, BaGuideStudentBgmCards.kt, BaGuideCatalogPagePager.kt, BaGuideFavoriteBgmMusicContent.kt, BaGuideCatalogRepository.kt, BaGuideCatalogTabListState.kt app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPage.kt— `app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPage.kt` changes together with 6 other files — `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackCoordinator.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPagePager.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogRepository.kt`, `app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogTabListState.kt` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: AppLiquidButtons.kt → AppInteractiveTokens.kt, AppLiquidCheckbox.kt, AppStandaloneLiquidButtons.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt— `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt` changes together with 3 other files — `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppInteractiveTokens.kt`, `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt`, `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: GitHubPageSheetHost.kt → GitHubActionsActions.kt, GitHubApkInfoSheet.kt, GitHubTrackEditFormContent.kt, GitHubTrackEditSheet.kt app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageSheetHost.kt— `app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageSheetHost.kt` changes together with 4 other files — `app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsActions.kt`, `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSheet.kt`, `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt`, `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Duplicated block (15 lines × 2) app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:172— app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:172-186 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:206-220 — 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/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:172` 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/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:35— app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:35-49 | app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt:35-49 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt` and `app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:35` 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 (15 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:52— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:52-66 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:51-65 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:52` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:51` calls `getString` and `app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:50` 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 (15 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:43— app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:43-57 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:94-108 — 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/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:43` 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/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:166— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:166-180 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:183-197 — 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/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:352— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:352-366 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:369-383 — 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/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:352` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:668— app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:668-682 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:710-724 — 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/os/kei/ui/page/main/ba/BaOfficeController.kt:668` 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/os/kei/ui/page/main/ba/BaPageEffects.kt:93— app/src/main/java/os/kei/ui/page/main/ba/BaPageEffects.kt:93-107 | app/src/main/java/os/kei/ui/page/main/ba/BaPageEffects.kt:135-149 — 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/os/kei/ui/page/main/ba/BaPageEffects.kt:93` 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/os/kei/ui/page/main/ba/BaSettingsSheet.kt:72— app/src/main/java/os/kei/ui/page/main/ba/BaSettingsSheet.kt:72-86 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferActions.kt:92-106 — 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/os/kei/ui/page/main/ba/BaSettingsSheet.kt:72` 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/os/kei/ui/page/main/ba/card/BaCardCommon.kt:132— app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:132-146 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppCardHeaders.kt:187-201 — 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/os/kei/ui/page/main/ba/card/BaCardCommon.kt:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:147` calls `size` and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppCardHeaders.kt:202` 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 (15 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:109— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:109-123 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:135-149 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:109` 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/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:508— app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:508-522 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryDiagnostics.kt:106-120 — 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/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:508` 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/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:338— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:338-352 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerPage.kt:171-185 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:338` 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) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:181— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:181-195 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:344-358 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:181` 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 (15 lines × 2) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:259— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:259-273 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:472-486 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:259` 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 (15 lines × 2) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:373— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:373-387 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:402-416 — 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 `core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:373` 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 (15 lines × 2) feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:452— feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:452-466 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:759-773 — 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 `feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:452` 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 (15 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:751— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:751-765 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:791-805 — 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/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:103— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:103-117 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:144-158 — 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/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:103` 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/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:406— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:406-413 | REDACTED:48-56 — 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 (8 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/card/BaAccountPagerCard.kt:255— app/src/main/java/os/kei/ui/page/main/ba/card/BaAccountPagerCard.kt:255-262 | app/src/main/java/os/kei/ui/page/main/ba/card/BaAccountPagerCard.kt:273-280 — 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 (8 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:130— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:130-137 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:268-275 — 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/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:130` 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/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:299— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:299-306 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreSnapshotMapping.kt:41-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt:189— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt:189-196 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackSupport.kt:112-119 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackSupport.kt:112` 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 (8 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:112— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:112-119 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:66-73 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:112` 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/os/kei/ui/page/main/sync/WebDavSyncCards.kt:586— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:586-593 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:612-619 — 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 (8 lines × 2) REDACTED:155— REDACTED:155-162 | REDACTED:203-210 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:202` calls `trim` and `REDACTED:154` 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 (8 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:338— feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:338-345 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:365-372 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:338` 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:61— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:61-68 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetSurface.kt:68-76 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:61` 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryRepository.kt:121— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryRepository.kt:121-128 | app/src/main/java/os/kei/ui/page/main/os/OsPageCardTransferRepository.kt:26-33 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryRepository.kt:121` 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 (8 lines × 2) app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownParser.kt:317— app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownParser.kt:317-324 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.kt:181-188 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.kt:181` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:592— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:592-599 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryProfileRepository.kt:422-429 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:592` 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 (8 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:143— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:143-151 | REDACTED:68-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:163— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:163-170 | REDACTED:92-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) REDACTED:61— REDACTED:61-68 | REDACTED:55-62 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:156— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:156-163 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:164-171 — 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/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:156` 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/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:59— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:59-66 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:211-218 — 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. 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaPageFloatingDock.kt:41— app/src/main/java/os/kei/ui/page/main/ba/BaPageFloatingDock.kt:41-52 | app/src/main/java/os/kei/ui/page/main/mcp/McpPageFloatingActions.kt:38-49 — 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/os/kei/ui/page/main/ba/BaPageFloatingDock.kt:41` 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/card/BaCalendarPoolCards.kt:100— app/src/main/java/os/kei/ui/page/main/ba/card/BaCalendarPoolCards.kt:100-111 | app/src/main/java/os/kei/ui/page/main/ba/card/BaCalendarPoolCards.kt:213-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) app/src/main/java/os/kei/ui/page/main/debug/DebugTabbedPageBottomChromeStage.kt:97— app/src/main/java/os/kei/ui/page/main/debug/DebugTabbedPageBottomChromeStage.kt:97-108 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:107-118 — 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/os/kei/ui/page/main/debug/DebugTabbedPageBottomChromeStage.kt:97` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/debug/DebugTabbedPageBottomChromeStage.kt:109` calls `stringResource` and `app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:119` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:48— app/src/main/java/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:48-59 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubTrackChangeHistoryCards.kt:47-58 — 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/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:48` 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportDeliveryCoordinator.kt:154— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportDeliveryCoordinator.kt:154-165 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:254-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.
Duplicated block (12 lines × 2) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:147— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:147-158 | app/src/main/java/os/kei/ui/page/main/student/component/GuideErrorSupportingBlock.kt:19-30 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:147` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:254— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:254-265 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:251-262 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt` as WHOLE FILES: this scan already matched 4 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionCopyMeta.kt:190— app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionCopyMeta.kt:190-201 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionCopyMeta.kt:212-223 — 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/os/kei/ui/page/main/student/section/GuideSectionCopyMeta.kt:190` 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:651— app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:651-662 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:685-696 — 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 (12 lines × 2) REDACTED:323— REDACTED:323-334 | REDACTED:200-211 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:161— feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:161-172 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:195-206 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:161` 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt:382— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt:382-393 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsWorkflowSelector.kt:304-315 — 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 (12 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/card/BaCraftCard.kt:120— app/src/main/java/os/kei/ui/page/main/ba/card/BaCraftCard.kt:120-131 | app/src/main/java/os/kei/ui/page/main/ba/card/BaSlotCards.kt:411-422 — 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/os/kei/ui/page/main/ba/card/BaCraftCard.kt:120` 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/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogViewModel.kt:527— app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogViewModel.kt:527-538 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideViewModel.kt:415-426 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:287— app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:287-298 | app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:416-427 — 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/os/kei/ui/page/main/sync/WebDavAutoSync.kt:287` 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:468— feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:468-479 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidReleaseCheckSource.kt:347-358 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:468` 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 (6 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:29— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:29-34 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:254-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt:59— app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt:59-64 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt:67-74 — 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 (6 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideTabVisibility.kt:65— app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideTabVisibility.kt:65-70 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideSimulateTabContent.kt:68-73 — 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 (6 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:211— feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:211-216 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:304-309 — 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) feature-github/src/main/java/os/kei/feature/github/model/FdroidTrackModels.kt:122— feature-github/src/main/java/os/kei/feature/github/model/FdroidTrackModels.kt:122-128 | feature-github/src/main/java/os/kei/feature/github/model/GitHubTrackModels.kt:177-182 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:474— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:474-479 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/FlatLiquidBackdrop.kt:585-590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:326— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:326-331 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubReleaseNotesActions.kt:314-319 — 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/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:326` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) REDACTED:366— REDACTED:366-371 | REDACTED:213-218 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:393— app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:393-398 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:765-770 — 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/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:393` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:69— REDACTED:69-74 | REDACTED:64-69 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:260— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:260-265 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:462-467 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:273— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:273-278 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:694-699 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:146— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:146-151 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:701-706 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:146` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) feature-ba/src/main/java/os/kei/feature/ba/mcp/McpBaTools.kt:33— feature-ba/src/main/java/os/kei/feature/ba/mcp/McpBaTools.kt:33-38 | feature-ba/src/main/java/os/kei/feature/ba/mcp/McpBaTools.kt:44-49 — 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 `feature-ba/src/main/java/os/kei/feature/ba/mcp/McpBaTools.kt:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/os/kei/ui/page/main/os/OsPageRowsDeriver.kt:116— app/src/main/java/os/kei/ui/page/main/os/OsPageRowsDeriver.kt:116-121 | app/src/main/java/os/kei/ui/page/main/os/OsTopInfoData.kt:155-160 — 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) REDACTED:406— REDACTED:406-411 | REDACTED:450-455 — 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 (16 corresponding lines) · ×15
Edited copy of a member (16 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:309— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:309-324 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:442-459 — 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) baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:341— baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:341-356 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:614-633 — 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/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogImageController.kt:331— app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogImageController.kt:331-350 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileLinkTitleLoader.kt:121-136 — 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/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:234— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:234-249 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:256-287 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:146— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:146-161 | app/src/main/java/os/kei/ui/page/main/student/component/GuideErrorSupportingBlock.kt:18-35 — 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/os/kei/ui/page/main/ba/BaOfficePageRepository.kt:172— app/src/main/java/os/kei/ui/page/main/ba/BaOfficePageRepository.kt:172-188 | app/src/main/java/os/kei/ui/page/main/ba/BaPageBindings.kt:18-33 — 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/os/kei/ui/page/main/student/BaStudentGuideExtensions.kt:27— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideExtensions.kt:27-46 | app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:18-33 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:492— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:492-507 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportContent.kt:516-532 — 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/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveRepository.kt:111— app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveRepository.kt:111-126 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveRepository.kt:132-149 — 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) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:102— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:102-117 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:119-134 — 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/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:29— app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:29-45 | app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:51-66 — 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) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:355— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:355-372 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:331-346 — 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) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:264— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:264-281 | app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionRows.kt:147-162 — 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) feature-mcp/src/main/java/os/kei/mcp/server/McpServerManager.kt:369— feature-mcp/src/main/java/os/kei/mcp/server/McpServerManager.kt:369-384 | feature-mcp/src/main/java/os/kei/mcp/server/McpServerManager.kt:458-474 — 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/os/kei/ui/page/main/debug/DebugComponentLabActivity.kt:11— app/src/main/java/os/kei/ui/page/main/debug/DebugComponentLabActivity.kt:11-28 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogActivity.kt:11-26 — 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.
Duplicated block (14 lines × 2) app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:249— app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:249-262 | app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:283-296 — 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/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:249` 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/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:572— app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:572-585 | app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:300-313 — 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/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:572` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:396— app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:396-409 | app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:489-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:396` 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 (14 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:149— app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:149-162 | app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:190-203 — 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/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:149` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:247— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:247-260 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubRefreshBatchActions.kt:228-241 — 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 (14 lines × 2) app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:174— app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:174-187 | app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt:67-80 — 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 (14 lines × 2) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportBaPlanner.kt:42— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportBaPlanner.kt:42-55 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportBaPlanner.kt:135-148 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportBaPlanner.kt:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayContentParser.kt:365— app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayContentParser.kt:365-378 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:484-497 — 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/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayContentParser.kt:365` 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 (14 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:266— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:266-279 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryMediaRenderer.kt:88-101 — 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/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:266` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:336— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:336-349 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryMediaRenderer.kt:154-167 — 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/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:336` 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/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:134— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:134-147 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:196-209 — 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/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:134` 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) core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:173— core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:173-186 | core-system/src/main/java/os/kei/core/shizuku/service/KeiShizukuUserService.kt:204-217 — 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 `core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:173` 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:218— feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:218-231 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:278-291 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:218` 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidGlassBottomSheet.kt:320— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidGlassBottomSheet.kt:320-333 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidGlassBottomSheet.kt:347-360 — 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. 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 (14 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:855— app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:855-868 | app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:880-893 — 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/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:855` 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.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×13
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:58— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:58-68 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:210-224 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportAttachStoreSupport.kt:120— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportAttachStoreSupport.kt:120-135 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportAttachStoreSupport.kt:141-151 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:172— core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:172-182 | core-download/src/main/java/os/kei/core/download/segmented/RangeProbe.kt:47-59 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:269— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:269-279 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:266-276 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:527— app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:527-537 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:479-496 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) REDACTED:174— REDACTED:174-184 | REDACTED:167-177 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabHeaderState.kt:156— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabHeaderState.kt:156-168 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideNpcSatelliteProfileState.kt:392-402 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt:15— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowModels.kt:15-28 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationModels.kt:182-192 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:665— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:665-676 | core-log/src/main/java/os/kei/core/log/AppLogStore.kt:36-46 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:64— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:64-76 | REDACTED:153-163 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:57— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:57-67 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:57-67 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiRepositoryProfileSource.kt:27— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiRepositoryProfileSource.kt:27-37 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubCommunityProfileSource.kt:20-30 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:1023— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:1023-1033 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:963-973 — 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) · ×13
Edited copy of a member (8 corresponding lines) core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:163— core-download/src/main/java/os/kei/core/download/range/RemoteByteRangeClient.kt:163-170 | core-download/src/main/java/os/kei/core/download/segmented/RangeProbe.kt:154-161 — 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.
Edited copy of a member (8 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidProgressBars.kt:436— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidProgressBars.kt:436-443 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:860-867 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionLanes.kt:47— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionLanes.kt:47-54 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseLanes.kt:69-76 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:790— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:790-797 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncPlanDialog.kt:280-287 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmMediaIslandShareCompat.kt:148— app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmMediaIslandShareCompat.kt:148-159 | app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideMediaSupport.kt:32-39 — 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.
Edited copy of a member (8 corresponding lines) REDACTED:62— REDACTED:62-69 | REDACTED:27-34 — 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.
Edited copy of a member (8 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:53— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:53-62 | REDACTED:165-172 — 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.
Edited copy of a member (8 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:153— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:153-161 | REDACTED:83-90 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/asset/GitHubDirectApkInstallAssets.kt:130— app/src/main/java/os/kei/ui/page/main/github/asset/GitHubDirectApkInstallAssets.kt:130-138 | app/src/main/java/os/kei/ui/page/main/github/asset/GitHubFdroidInstallAssets.kt:172-179 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaSessionIndexStore.kt:52— app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaSessionIndexStore.kt:52-60 | REDACTED:368-375 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:999— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:999-1006 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:525-532 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/OsPageData.kt:54— app/src/main/java/os/kei/ui/page/main/os/OsPageData.kt:54-61 | app/src/main/java/os/kei/ui/page/main/os/OsTopInfoData.kt:91-99 — 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.
Edited copy of a member (8 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFetch.kt:331— app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFetch.kt:331-338 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:152-159 — 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 (12 corresponding lines) · ×13
Edited copy of a member (12 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:33— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:33-50 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:430-441 — 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/os/kei/core/background/AppBackgroundRecoveryStore.kt:33— app/src/main/java/os/kei/core/background/AppBackgroundRecoveryStore.kt:33-44 | app/src/main/java/os/kei/core/background/AppBackgroundRecoveryStore.kt:52-63 — 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) feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubRepositoryProfileSummary.kt:171— feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubRepositoryProfileSummary.kt:171-182 | feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubRepositoryProfileSummary.kt:262-273 — 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) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:206— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:206-217 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:224-238 — 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/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:70— app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:70-81 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeVisitNotificationDispatcher.kt:70-81 — 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/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:216— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:216-227 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:235-246 — 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/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:171— app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:171-182 | app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:188-201 — 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/os/kei/ui/page/main/github/section/GitHubTrackedItemDecisionCards.kt:76— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemDecisionCards.kt:76-87 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemDecisionCards.kt:97-112 — 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) feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt:237— feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt:237-248 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsArtifactManifestProbe.kt:71-82 — 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:50— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:50-61 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:107-118 — 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/os/kei/feature/github/notification/GitHubShareImportNotificationActions.kt:159— app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationActions.kt:159-170 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportPendingScheduler.kt:50-62 — 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidToolbar.kt:393— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidToolbar.kt:393-404 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:251-262 — 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) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:47— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:47-59 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkVersionedDirectoryResolver.kt:45-56 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×12
Edited copy of a member (13 corresponding lines) app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:363— app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:363-389 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:711-723 — 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/os/kei/ui/page/main/home/state/HomePageContentTextBundle.kt:151— app/src/main/java/os/kei/ui/page/main/home/state/HomePageContentTextBundle.kt:151-163 | app/src/main/java/os/kei/ui/page/main/mcp/util/McpPageUtils.kt:17-29 — 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) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppEdgeStackedCards.kt:219— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppEdgeStackedCards.kt:219-234 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetLayout.kt:25-37 — 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) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:212— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:212-224 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:196-209 — 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/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:385— app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:385-397 | app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:425-437 — 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/os/kei/ui/page/main/mcp/skill/component/McpSkillContentList.kt:264— app/src/main/java/os/kei/ui/page/main/mcp/skill/component/McpSkillContentList.kt:264-276 | app/src/main/java/os/kei/ui/page/main/os/shell/OsShellOutputRenderer.kt:162-174 — 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:523— feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:523-535 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:540-552 — 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/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:65— app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:65-81 | app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:83-95 — 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/os/kei/ui/page/main/os/shell/page/OsShellRunnerRouteEffects.kt:80— app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerRouteEffects.kt:80-92 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePlayerEffects.kt:49-66 — 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/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:166— app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:166-187 | app/src/main/java/os/kei/ui/page/main/ba/support/BaSettingsStore.kt:191-203 — 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) feature-github/src/main/java/os/kei/feature/github/model/GitHubLookupModels.kt:86— feature-github/src/main/java/os/kei/feature/github/model/GitHubLookupModels.kt:86-100 | feature-github/src/main/java/os/kei/feature/github/model/GitHubLookupModels.kt:118-130 — 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) REDACTED:187— REDACTED:187-199 | REDACTED:221-233 — 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.
Duplicated block (20 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolDataSettingsSheet.kt:124— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolDataSettingsSheet.kt:124-143 | app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:430-449 — 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/os/kei/ui/page/main/ba/BaCalendarPoolDataSettingsSheet.kt:124` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:127— app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:127-146 | app/src/main/java/os/kei/ui/page/main/ba/card/BaCafeCard.kt:163-182 — 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/os/kei/ui/page/main/ba/card/BaApCard.kt:127` 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/os/kei/ui/page/main/ba/card/BaCafeCard.kt:161` calls `cafeDailyCapacity` and `app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:126` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:154— app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:154-173 | app/src/main/java/os/kei/ui/page/main/ba/card/BaCafeCard.kt:190-209 — 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/os/kei/ui/page/main/ba/card/BaApCard.kt:154` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSections.kt:485— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSections.kt:485-504 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailSheets.kt:658-677 — 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/os/kei/ui/page/main/github/sheet/GitHubApkInfoSections.kt:485` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSections.kt:484` calls `isBlank` and `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailSheets.kt:657` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:277— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:277-296 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:326-345 — 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/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:277` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:218— app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:218-237 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:306-326 — 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/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:218` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:293— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:293-312 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:390-409 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:293` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:651— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:651-670 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:763-782 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:651` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:322— app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:322-341 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:414-433 — 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/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:322` 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 (20 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:123— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:123-142 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:387-406 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:123` 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 (20 lines × 2) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:523— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:523-542 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:557-576 — 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 `core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationTemplate.kt:523` 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 (20 lines × 2) REDACTED:122— REDACTED:122-141 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubActionsRecommendedRunStore.kt:74-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Repeated repair: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.kt:65— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.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 4 (its worst body is AppNavigationPlacementKt.appNavigationPlacementFor at line 65), 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(chrome): push page content clear of the sidebar rail”; “fix(pad): bring a route's back button in with its own content column”; “fix(nav): stop the navigation collapsing on scroll at regular width”; “fix(pad): deliver the background extension effect, asymmetrically”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/AppNavigationPlacement.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: baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:13— baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.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 10 (its worst body is BaselineProfileActionsKt.exerciseBaCatalogAndReturn at line 13), 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(profile): preflight OEM permissions and exercise Pad viewers”; “fix(profile): settle tap geometry and capture failed arrivals”; “fix(profile): validate and collect phone and tablet matrix”; “fix(profile): follow collapsed chrome and preserve physical preflight”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.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/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.kt:53— app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.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 14 (its worst body is BaGuideFavoriteBgmMusicContentKt.BaGuideFavoriteBgmMusicContent 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(bgm): restore native playback on reentry”; “fix(pad): deliver the background extension effect, asymmetrically”; “fix(pad): cap the guide catalog route, which round 1 never reached”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.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: feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubReleaseSelectionModels.kt feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubReleaseSelectionModels.kt:177— feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubReleaseSelectionModels.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 9 (its worst body is GitHubReleaseDecisionNote.from at line 177), 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(github): select releases by APK package in mixed-product repositories”; “fix(github): stop explaining a decision that surprised nobody, on every Atom card”; “fix(github): stop Atom mode claiming more than the feed can tell it”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- feature-github-engine/src/main/java/os/kei/feature/github/model/GitHubReleaseSelectionModels.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: feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:316— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.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 10 (its worst body is GitHubApiTokenReleaseStrategy.parseReleaseEntry at line 316), 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(github): stop Atom mode claiming more than the feed can tell it”; “fix(github): an update you cannot install is not an update”; “fix(github): ask the forge which release is current, but only when it matters”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt:125— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.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 AppLiquidExpandableCardsKt.AppLiquidExpandableCardFrame at line 125), 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(ui): let a card join the pile only if the pile can show all of it”; “fix(glass): apply the accordion card frame's own modifier”; “fix(ui): keep expanded cards out of edge stack”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.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/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPageContent.kt app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPageContent.kt:431— app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPageContent.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 10 (its worst body is BaGuideCatalogPageContentKt.isBaGuideCatalogInitialContentReady at line 431), 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(pad): deliver the background extension effect, asymmetrically”; “fix(pad): cap the guide catalog route, which round 1 never reached”; “fix(catalog): make the page edges a scroll edge instead of a black curtain”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogPageContent.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/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt:84— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt changed 3 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 8 (its worst body is BaGuideBgmNativeMediaController.syncQueue at line 84), 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(bgm): restore native playback on reentry”; “fix(bgm): recover missing playback artwork”; “fix(media): harden controller and stop lifecycle”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.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/os/kei/ui/page/main/student/media/BaGuideBgmMediaSessionService.kt app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmMediaSessionService.kt:154— app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmMediaSessionService.kt changed 3 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 5 (its worst body is BaGuideBgmMediaSessionCallback.onCustomCommand at line 154), 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(media): harden controller and stop lifecycle”; “fix(media): preserve artwork and OEM ownership”; “fix(media): let Media3 decide what an untrusted controller may do”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmMediaSessionService.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: feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseSelector.kt feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseSelector.kt:113— feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseSelector.kt changed 3 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 4 (its worst body is GitHubReleaseSelectionPlan.resolve at line 113), 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(github): align release plan copy visibility with its constructor”; “fix(github): stop explaining a decision that surprised nobody, on every Atom card”; “fix(github): stop Atom mode claiming more than the feed can tell it”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseSelector.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: ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt:40— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt changed 3 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 7 (its worst body is AppFloatingLiquidDockSurfaceKt.AppFloatingLiquidVerticalDockSurface at line 40), 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(dock): make the badge mean one thing, keep it inside, give it glass”; “fix(chrome): let the glass follow the finger again, and keep the page still”; “fix(chrome): stop the pager stealing presses, and finish the toolbar work”. 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-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 09:06:32 +08:00' --until='2026-10-27 09:06:32 +08:00' --full-history --no-merges -- ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×11
Edited copy of a member (14 corresponding lines) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:729— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:729-742 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncHistoryCards.kt:352-370 — 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) REDACTED:44— REDACTED:44-57 | REDACTED:47-60 — 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) REDACTED:26— REDACTED:26-39 | REDACTED:26-42 — 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/os/kei/ui/page/main/ba/support/BaAccountStore.kt:236— app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:236-250 | app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:266-279 — 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) core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:116— core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:116-131 | core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:168-181 — 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/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:119— app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:119-136 | feature-keepalive/src/main/java/os/kei/feature/keepalive/notification/AccessibilityGuardNotificationHelper.kt:15-28 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCardState.kt:89— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogEntryCardState.kt:89-102 | app/src/main/java/os/kei/ui/page/main/widget/support/TextCopySupport.kt:54-68 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSupport.kt:59— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSupport.kt:59-72 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubApkInfoSupport.kt:77-90 — 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/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:431— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:431-444 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:449-463 — 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/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:73— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:73-86 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:147-161 — 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/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:496— app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:496-509 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:532-545 — 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 (10 corresponding lines) · ×11
Edited copy of a member (10 corresponding lines) app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:333— app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:333-342 | app/src/main/java/os/kei/ui/page/main/os/store/OsInfoCacheStore.kt:33-42 — 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) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:186— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2Parser.kt:186-198 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:173-182 — 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/os/kei/core/background/AppBackgroundSchedulePolicy.kt:360— app/src/main/java/os/kei/core/background/AppBackgroundSchedulePolicy.kt:360-371 | app/src/main/java/os/kei/ui/page/main/ba/support/BaPageMath.kt:102-111 — 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/os/kei/ui/page/main/ba/BaCalendarPoolUnreadModels.kt:117— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadModels.kt:117-126 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadModels.kt:133-143 — 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/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:613— app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:613-622 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:678-687 — 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) core-system/src/main/java/os/kei/core/system/PropUtils.kt:124— core-system/src/main/java/os/kei/core/system/PropUtils.kt:124-135 | core-system/src/main/java/os/kei/core/system/PropUtils.kt:137-146 — 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/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:144— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:144-153 | app/src/main/java/os/kei/feature/ba/data/remote/GameKeeNetworkClient.kt:243-252 — 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) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:730— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:730-739 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.kt:223-232 — 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/os/kei/ui/page/main/ba/BaPoolPage.kt:144— app/src/main/java/os/kei/ui/page/main/ba/BaPoolPage.kt:144-153 | app/src/main/java/os/kei/ui/page/main/host/main/MainScreenGuideNavigation.kt:27-36 — 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/os/kei/ui/page/main/github/page/GitHubPageRepository.kt:597— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRepository.kt:597-606 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseAssetService.kt:88-99 — 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/os/kei/ui/page/main/mcp/section/McpOverviewSection.kt:125— app/src/main/java/os/kei/ui/page/main/mcp/section/McpOverviewSection.kt:125-134 | app/src/main/java/os/kei/ui/page/main/os/components/OsSectionUi.kt:52-61 — 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) · ×11
Edited copy of a member (9 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/AndroidBinaryXmlPackageNameParser.kt:231— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/AndroidBinaryXmlPackageNameParser.kt:231-239 | feature-github-engine/src/main/java/os/kei/feature/github/data/apk/AndroidBinaryXmlPackageNameParser.kt:241-249 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryViewModel.kt:456— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryViewModel.kt:456-464 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryViewModel.kt:483-491 — 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/os/kei/ui/page/main/github/profile/GitHubRepositoryProfileUiModels.kt:201— app/src/main/java/os/kei/ui/page/main/github/profile/GitHubRepositoryProfileUiModels.kt:201-209 | app/src/main/java/os/kei/ui/page/main/github/profile/GitHubRepositoryProfileUiModels.kt:242-250 — 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/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:213— app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:213-221 | app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:258-266 — 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/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:368— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:368-376 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:378-386 — 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/os/kei/ui/page/main/github/page/GitHubPageState.kt:378— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt:378-386 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt:400-408 — 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/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogListDerivedState.kt:254— app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogListDerivedState.kt:254-262 | app/src/main/java/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogListDerivedState.kt:277-285 — 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/os/kei/ui/page/main/student/BaStudentGuideExtensions.kt:58— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideExtensions.kt:58-67 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideNpcSatelliteProfileState.kt:327-335 — 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/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:233— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportCandidateCards.kt:233-243 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:317-325 — 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) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:114— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:114-122 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationModels.kt:481-490 — 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) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:165— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusExpandedComponents.kt:165-173 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusNotificationModels.kt:500-509 — 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 (19 corresponding lines) · ×10
Edited copy of a member (19 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:430— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:430-450 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:496-514 — 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/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileFieldRules.kt:192— app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileFieldRules.kt:192-213 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileFieldRules.kt:223-241 — 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/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:657— app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:657-676 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:677-695 — 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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:134— app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:134-154 | app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:280-298 — 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubDirectApkReleaseCheckSource.kt:556— feature-github/src/main/java/os/kei/feature/github/domain/GitHubDirectApkReleaseCheckSource.kt:556-574 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidReleaseCheckSource.kt:271-289 — 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) core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:173— core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:173-191 | core-system/src/main/java/os/kei/core/shizuku/service/KeiShizukuUserService.kt:204-222 — 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/os/kei/ui/page/main/settings/state/SettingsPageRepository.kt:176— app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageRepository.kt:176-194 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageRepository.kt:206-230 — 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/os/kei/ui/page/main/os/OsPageTransferCoordinator.kt:33— app/src/main/java/os/kei/ui/page/main/os/OsPageTransferCoordinator.kt:33-52 | app/src/main/java/os/kei/ui/page/main/os/OsPageTransferCoordinator.kt:54-72 — 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/os/kei/ui/page/main/ba/BaOfficeController.kt:302— app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:302-320 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:325-344 — 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/os/kei/ui/page/main/widget/chrome/AppPageLayouts.kt:252— app/src/main/java/os/kei/ui/page/main/widget/chrome/AppPageLayouts.kt:252-272 | app/src/main/java/os/kei/ui/page/main/widget/chrome/AppPageLayouts.kt:478-496 — 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.
Duplicated block (17 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:208— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:208-224 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:394-410 — 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/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:208` 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 (17 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:469— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:469-485 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubRefreshBatchActions.kt:431-447 — 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 (17 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:101— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:101-117 | app/src/main/java/os/kei/ui/page/main/mcp/sheet/McpEditSheet.kt:56-72 — 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/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:101` 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/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:32— app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:32-48 | app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:75-91 — 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/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:32` 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/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:74` calls `isFailureMessage` and `app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:31` 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 (17 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:133— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:133-149 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:141-157 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt` as WHOLE FILES: this scan already matched 4 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.
Duplicated block (17 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryAudioPlayerState.kt:206— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryAudioPlayerState.kt:206-222 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryAudioPlayerState.kt:304-320 — 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 (17 lines × 2) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:347— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:347-363 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:475-491 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:347` 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) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:105— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:105-121 | feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:141-157 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:105` 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 (17 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDistributionProfileSource.kt:73— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDistributionProfileSource.kt:73-89 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDistributionProfileSource.kt:97-113 — 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 `feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDistributionProfileSource.kt:73` 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 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:387— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:387-403 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:567-583 — 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.
Swallowed exception (caught, then discarded) core-notification/src/main/java/os/kei/core/notification/live/oem/honor/HonorOrderFeedbackClient.kt:64— `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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:106— `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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:125— `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/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:220— `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/os/kei/ui/page/main/student/page/state/BaStudentGuideRepository.kt:601— `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/os/kei/ui/page/main/student/catalog/state/BaGuideCatalogBgmCacheController.kt:161— `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/os/kei/ui/page/main/student/catalog/state/BaGuideFavoriteBgmCacheRepository.kt:59— `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/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferUseCases.kt:216— `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/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferUseCases.kt:247— `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/os/kei/ui/page/main/student/catalog/component/BaGuideBgmArtworkHydration.kt:37— `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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×9
Edited copy of a member (15 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:86— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubApkManifestInfoCacheStore.kt:86-100 | REDACTED:105-126 — 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/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:464— app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:464-478 | app/src/main/java/os/kei/ui/page/main/host/main/MainScreenNavHost.kt:481-495 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt:181— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmNativeMediaController.kt:181-200 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackSupport.kt:105-119 — 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) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:88— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:88-102 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:107-121 — 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/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:13— app/src/main/java/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:13-27 | app/src/main/java/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:33-47 — 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) core-log/src/main/java/os/kei/core/log/AppLogger.kt:98— core-log/src/main/java/os/kei/core/log/AppLogger.kt:98-112 | core-log/src/main/java/os/kei/core/log/AppLogger.kt:117-132 — 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) core-log/src/main/java/os/kei/core/log/AppLogger.kt:134— core-log/src/main/java/os/kei/core/log/AppLogger.kt:134-148 | core-log/src/main/java/os/kei/core/log/AppLogger.kt:153-168 — 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/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:141— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:141-155 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:162-180 — 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/os/kei/ui/page/main/os/OsPageViewModel.kt:320— app/src/main/java/os/kei/ui/page/main/os/OsPageViewModel.kt:320-338 | app/src/main/java/os/kei/ui/page/main/os/OsPageViewModel.kt:343-357 — 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.
Duplicated block (19 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:46— app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:46-64 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeVisitNotificationDispatcher.kt:46-64 — 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/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:46` 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 (19 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:637— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:637-655 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:669-687 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:637` 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 (19 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconRepository.kt:26— app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconRepository.kt:26-44 | app/src/main/java/os/kei/ui/page/main/os/OsActivityShortcutIconRepository.kt:132-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.
Duplicated block (19 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:805— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:805-823 | feature-github/src/main/java/os/kei/feature/github/model/GitHubTrackedIgnoreModels.kt:44-62 — 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 × 2) app/src/main/java/os/kei/ui/page/main/os/OsOverviewMetrics.kt:167— app/src/main/java/os/kei/ui/page/main/os/OsOverviewMetrics.kt:167-185 | app/src/main/java/os/kei/ui/page/main/os/OsPageDerivedState.kt:89-107 — 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/os/kei/ui/page/main/os/OsOverviewMetrics.kt:167` 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 (19 lines × 2) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:249— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:249-267 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:297-315 — 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/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:249` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:128— core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:128-146 | core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:257-275 — 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 (19 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidActionSheet.kt:105— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidActionSheet.kt:105-123 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidAlert.kt:87-105 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidActionSheet.kt:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalPresentation.kt:90— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalPresentation.kt:90-108 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidMenuPresentation.kt:115-133 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalPresentation.kt:90` 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.
Off the main sequence: :core-concurrency — :core-concurrency: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: :core-io — :core-io: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: :core-json — :core-json: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: :core-log — :core-log: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: :core-versioning — :core-versioning: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: :ui-pip — :ui-pip: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: :ui-liquid-glass — :ui-liquid-glass: abstractness 0.01, instability 0.00, distance 0.99 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: :core-prefs — :core-prefs: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: :core-download — :core-download: abstractness 0.03, instability 0.25, distance 0.72 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×8
Edited copy of a member (21 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:387— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:387-407 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:461-481 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRenderHelpers.kt:78— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRenderHelpers.kt:78-98 | REDACTED:38-58 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:242— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:242-262 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:322-343 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:417— feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:417-442 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:446-466 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubFdroidDetailSheet.kt:603— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubFdroidDetailSheet.kt:603-624 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryProfileDetailContent.kt:402-422 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveCoordinator.kt:187— app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveCoordinator.kt:187-207 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveCoordinator.kt:209-229 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:165— feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:165-185 | feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:192-212 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:196— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:196-217 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/shape/AppSquircle.kt:225-245 — These two members are one piece of code written twice and then edited apart: 21 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 (18 corresponding lines) · ×8
Edited copy of a member (18 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:200— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkDirectoryIndexResolver.kt:200-222 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubDirectApkVersionedDirectoryResolver.kt:126-143 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) REDACTED:38— REDACTED:38-59 | REDACTED:36-53 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:206— app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:206-223 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogStore.kt:287-304 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/os/kei/core/background/GitHubBackgroundRefreshJobService.kt:296— app/src/main/java/os/kei/core/background/GitHubBackgroundRefreshJobService.kt:296-319 | app/src/main/java/os/kei/core/background/WebDavAutoSyncJobService.kt:162-179 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:83— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:83-100 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:141-159 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:354— feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:354-371 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubStrategyBenchmarkService.kt:375-393 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:568— app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:568-588 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:593-610 — These two members are one piece of code written twice and then edited apart: 18 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 (18 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:582— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:582-599 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:605-626 — These two members are one piece of code written twice and then edited apart: 18 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) · ×8
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:55— app/src/main/java/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:55-74 | app/src/main/java/os/kei/ui/page/main/ba/BaDebugCalendarPoolDeriver.kt:82-101 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportComponents.kt:307— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportComponents.kt:307-328 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:496-515 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:70— app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:70-94 | app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt:124-143 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:583— app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:583-607 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsPageViewModel.kt:657-676 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/card/BaAccountPagerCard.kt:386— app/src/main/java/os/kei/ui/page/main/ba/card/BaAccountPagerCard.kt:386-405 | app/src/main/java/os/kei/ui/page/main/ba/card/BaCalendarPoolCards.kt:308-327 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:1057— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:1057-1076 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:1178-1198 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) feature-mcp/src/main/java/os/kei/mcp/notification/McpXiaomiMagicDispatcher.kt:441— feature-mcp/src/main/java/os/kei/mcp/notification/McpXiaomiMagicDispatcher.kt:441-460 | feature-mcp/src/main/java/os/kei/mcp/notification/McpXiaomiMagicDispatcher.kt:487-506 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaLiquidSurfaces.kt:240— app/src/main/java/os/kei/ui/page/main/ba/BaLiquidSurfaces.kt:240-262 | app/src/main/java/os/kei/ui/page/main/ba/BaLiquidSurfaces.kt:286-305 — 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.
Duplicated block (23 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:102— app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:102-124 | app/src/main/java/os/kei/ui/page/main/ba/BaSettingsSheet.kt:97-119 — 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/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:102` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsCards.kt:57— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsCards.kt:57-79 | app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsCards.kt:135-157 — 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/os/kei/ui/page/main/github/actions/GitHubActionsCards.kt:57` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:124— app/src/main/java/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:124-146 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubTrackChangeHistoryCards.kt:110-132 — 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/os/kei/ui/page/main/github/history/GitHubAppInstallHistoryCards.kt:124` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:431— app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:431-453 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryDiagnostics.kt:146-168 — 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/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:431` 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 lines × 2) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:45— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:45-67 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:69-91 — 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/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:9— app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:9-31 | app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:51-73 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:74` calls `isFailureMessage` and `app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:32` 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 (23 lines × 2) app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:94— app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:94-116 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:885-907 — 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 (23 lines × 2) app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:163— app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:163-185 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:195-217 — 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/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:163` 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.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×7
Edited copy of a member (32 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidBatchPackageSnapshotProvider.kt:262— feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidBatchPackageSnapshotProvider.kt:262-293 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidBatchPackageSnapshotProvider.kt:343-375 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/cache/BaCacheProviders.kt:197— app/src/main/java/os/kei/ui/page/main/settings/cache/BaCacheProviders.kt:197-228 | app/src/main/java/os/kei/ui/page/main/settings/cache/OsSystemCacheProviders.kt:113-145 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:894— app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:894-925 | app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:933-964 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueViewModel.kt:161— app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueViewModel.kt:161-194 | app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueViewModel.kt:196-227 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:683— app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:683-714 | app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:764-795 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueSubmitDialog.kt:81— app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueSubmitDialog.kt:81-113 | app/src/main/java/os/kei/ui/page/main/os/components/OsImportPreviewDialog.kt:85-116 — 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.
Edited copy of a member (32 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:155— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:155-191 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:105-136 — 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 (17 corresponding lines) · ×7
Edited copy of a member (17 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:297— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:297-314 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:335-351 — 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/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:118— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:118-138 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchContentParser.kt:15-31 — 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/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:123— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:123-141 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:150-166 — 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) baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:323— baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:323-339 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:592-612 — 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) REDACTED:186— REDACTED:186-202 | REDACTED:179-197 — 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) core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt:357— core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt:357-373 | core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt:377-398 — 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/os/kei/ui/page/main/mcp/section/McpOverviewSection.kt:79— app/src/main/java/os/kei/ui/page/main/mcp/section/McpOverviewSection.kt:79-96 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpOverviewSection.kt:102-118 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×7
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:51— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:51-56 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:203-208 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:358— app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:358-366 | core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:993-998 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/components/OsActivityVisibilityPresentation.kt:41— app/src/main/java/os/kei/ui/page/main/os/components/OsActivityVisibilityPresentation.kt:41-46 | app/src/main/java/os/kei/ui/page/main/os/components/OsShellVisibilityPresentation.kt:46-51 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutSuggestions.kt:197— app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutSuggestions.kt:197-202 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubDiscoveryFormatters.kt:32-37 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:452— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:452-457 | feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:455-460 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/ui/page/main/about/page/AboutSearchIndex.kt:353— app/src/main/java/os/kei/ui/page/main/about/page/AboutSearchIndex.kt:353-358 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:262-268 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:242— app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:242-247 | app/src/main/java/os/kei/ui/page/main/mcp/model/McpPageModels.kt:3-8 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×7
Edited copy of a member (7 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaValidation.kt:13— app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaValidation.kt:13-19 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:197-204 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutCardActions.kt:203— app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutCardActions.kt:203-209 | feature-mcp/src/main/java/os/kei/mcp/server/McpToolSupport.kt:66-73 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportDraftStore.kt:84— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportDraftStore.kt:84-90 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:241-247 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:178— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:178-185 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:43-49 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshService.kt:405— feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshService.kt:405-413 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackService.kt:192-198 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) app/src/main/java/os/kei/ui/page/main/mcp/McpPageSections.kt:193— app/src/main/java/os/kei/ui/page/main/mcp/McpPageSections.kt:193-199 | app/src/main/java/os/kei/ui/page/main/os/components/OsPageCardSink.kt:41-47 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryFacade.kt:73— feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryFacade.kt:73-79 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubStarImportService.kt:49-55 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15–16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsRecommendedRunRefreshCoordinator.kt:55— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsRecommendedRunRefreshCoordinator.kt:55-69 | app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsRecommendedRunRefreshCoordinator.kt:112-127 — 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/os/kei/ui/page/main/github/page/action/GitHubActionsRecommendedRunRefreshCoordinator.kt:55` 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–16 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:167— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:167-182 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:375-389 — 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/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:167` 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 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 (15–16 lines × 2) app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceEditorSheet.kt:63— app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceEditorSheet.kt:63-78 | app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:385-399 — 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/os/kei/ui/page/main/os/components/OsGoogleSystemServiceEditorSheet.kt:63` 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 (15–16 lines × 2) app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt:946— app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt:946-960 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryFullscreen.kt:384-399 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/student/GuideVideoFullscreenActivity.kt:946` 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 (15–16 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabContent.kt:54— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabContent.kt:54-68 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideSkillsTabContent.kt:36-51 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabContent.kt:54` 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 (15–16 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:309— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:309-324 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:444-458 — 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 (15–16 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:361— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:361-375 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:695-710 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:361` 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 (26 corresponding lines) · ×6
Edited copy of a member (26 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:105— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:105-130 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:164-194 — These two members are one piece of code written twice and then edited apart: 26 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 (26 corresponding lines) core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:133— core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:133-158 | core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:222-247 — These two members are one piece of code written twice and then edited apart: 26 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 (26 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:160— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:160-185 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:224-249 — These two members are one piece of code written twice and then edited apart: 26 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 (26 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:23— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:23-48 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:55-82 — These two members are one piece of code written twice and then edited apart: 26 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 (26 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:396— feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:396-421 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:428-454 — These two members are one piece of code written twice and then edited apart: 26 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 (26 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferGroups.kt:39— app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferGroups.kt:39-65 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferGroups.kt:76-101 — These two members are one piece of code written twice and then edited apart: 26 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 (29 corresponding lines) · ×6
Edited copy of a member (29 corresponding lines) app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:242— app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:242-270 | app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:276-304 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:48— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:48-76 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:13-41 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmPlaybackRepository.kt:85— app/src/main/java/os/kei/ui/page/main/student/media/BaGuideBgmPlaybackRepository.kt:85-113 | app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoritePlaybackStore.kt:112-143 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:298— app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:298-326 | app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:333-365 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:383— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:383-411 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:658-686 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:198— feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:198-226 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:234-263 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×6
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:275— app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:275-299 | app/src/main/java/os/kei/ui/page/main/github/asset/GitHubAssetUtils.kt:304-329 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:457— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:457-481 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryOptions.kt:485-510 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconRepository.kt:25— app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconRepository.kt:25-49 | app/src/main/java/os/kei/ui/page/main/os/OsActivityShortcutIconRepository.kt:131-155 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:263— app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:263-297 | app/src/main/java/os/kei/mcp/bridge/AppMcpSystemOsToolDelegate.kt:299-323 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmFavoriteCards.kt:47— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmFavoriteCards.kt:47-73 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmFavoriteCards.kt:124-148 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportManagedInstallProgressBlock.kt:136— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportManagedInstallProgressBlock.kt:136-166 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportProgressSheets.kt:13-37 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×6
Edited copy of a member (23 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:324— feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:324-349 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:354-376 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolDataSettingsSheet.kt:121— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolDataSettingsSheet.kt:121-143 | app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:427-449 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:328— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:328-350 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:858-881 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:29— feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsApiClient.kt:29-55 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:529-551 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:746— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:746-768 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:786-808 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) app/src/main/java/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:233— app/src/main/java/os/kei/ui/page/main/mcp/section/McpSectionBlocks.kt:233-255 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:336-364 — 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 (22 corresponding lines) · ×6
Edited copy of a member (22 corresponding lines) app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:499— app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:499-527 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogCard.kt:533-554 — 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.
Edited copy of a member (22 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadRepository.kt:70— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadRepository.kt:70-91 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadRepository.kt:101-122 — 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.
Edited copy of a member (22 corresponding lines) app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:576— app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:576-597 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:606-628 — 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.
Edited copy of a member (22 corresponding lines) app/src/main/java/os/kei/feature/ba/data/remote/GameKeeNetworkClient.kt:112— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeNetworkClient.kt:112-133 | app/src/main/java/os/kei/feature/ba/data/remote/GameKeeNetworkClient.kt:138-160 — 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.
Edited copy of a member (22 corresponding lines) core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:57— core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:57-84 | core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:92-113 — 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.
Edited copy of a member (22 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPageSupport.kt:57— app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPageSupport.kt:57-78 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt:98-122 — 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.
Duplicated block (18 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:74— app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:74-91 | app/src/main/java/os/kei/ui/page/main/ba/BaPoolPage.kt:82-99 — 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/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:74` 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 (18 lines × 2) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactSection.kt:125— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactSection.kt:125-142 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:338-359 — 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/os/kei/ui/page/main/github/actions/GitHubActionsArtifactSection.kt:125` 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 (18 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:299— app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:299-316 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryVideoGroupControls.kt:60-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:299` 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261-278 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:440-457 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261` 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 (18 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:294— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:294-311 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:354-371 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:294` 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 (18 lines × 2) app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:223— app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:223-240 | app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:311-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:223` 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 × 3) app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:45— app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:45-58 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeVisitNotificationDispatcher.kt:45-58 | app/src/main/java/os/kei/ui/page/main/ba/BaCraftNotificationDispatcher.kt:52-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:45` 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 lines × 3) app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:711— app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:711-724 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:745-758 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:779-792 — 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/os/kei/ui/page/main/ba/BaOfficeController.kt:711` 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 lines × 3) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:53— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:53-66 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:77-90 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:101-114 — 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/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetSections.kt:53` 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 (14 lines × 3) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29-42 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:52-65 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:137-150 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:63— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:63-76 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:104-117 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:145-158 — 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/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:63` 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 lines × 3) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261-274 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:440-453 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:490-503 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:261` 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.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×5
Edited copy of a member (28 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubVersionUtils.kt:31— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubVersionUtils.kt:31-58 | feature-github/src/main/java/os/kei/feature/github/model/GitHubTrackModels.kt:212-241 — 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.
Edited copy of a member (28 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:99— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:99-130 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsUpdateCheckService.kt:186-213 — 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.
Edited copy of a member (28 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:111— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:111-140 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:65-92 — 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.
Edited copy of a member (28 corresponding lines) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:127— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:127-158 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:168-195 — 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.
Edited copy of a member (28 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidRepositoryIndexClient.kt:36— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidRepositoryIndexClient.kt:36-63 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidRepositoryIndexClient.kt:77-104 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×5
Edited copy of a member (24 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:70— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:70-95 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:226-249 — 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) REDACTED:59— REDACTED:59-82 | REDACTED:62-86 — 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) feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:149— feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:149-172 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshRuntimeStore.kt:181-206 — 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) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:102— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:102-125 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:130-153 — 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) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:343— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:343-371 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:471-494 — 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 (27 corresponding lines) · ×5
Edited copy of a member (27 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPrivilegeStatusText.kt:30— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPrivilegeStatusText.kt:30-59 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPrivilegeStatusText.kt:65-91 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:132— app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:132-165 | app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:177-203 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) core-system/src/main/java/os/kei/core/privilege/RootPrivilegeBackend.kt:84— core-system/src/main/java/os/kei/core/privilege/RootPrivilegeBackend.kt:84-113 | core-system/src/main/java/os/kei/core/privilege/ShizukuPrivilegeBackend.kt:186-212 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:201— app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:201-227 | app/src/main/java/os/kei/ui/page/main/ba/card/BaSlotCards.kt:435-461 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportActivity.kt:263— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportActivity.kt:263-292 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportActivity.kt:110-136 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×5
Edited copies of one member (3 members, 15+ corresponding lines) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:114— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:114-128 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:130-148 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchCommon.kt:251-265 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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.
Edited copies of one member (3 members, 15+ corresponding lines) app/src/main/java/os/kei/core/shortcut/AppShortcuts.kt:126— app/src/main/java/os/kei/core/shortcut/AppShortcuts.kt:126-140 | app/src/main/java/os/kei/core/shortcut/AppShortcuts.kt:142-156 | app/src/main/java/os/kei/core/shortcut/AppShortcuts.kt:158-175 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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.
Edited copies of one member (3 members, 15+ corresponding lines) core-system/src/main/java/os/kei/core/system/PropUtils.kt:64— core-system/src/main/java/os/kei/core/system/PropUtils.kt:64-78 | core-system/src/main/java/os/kei/core/system/PropUtils.kt:83-99 | core-system/src/main/java/os/kei/core/system/PropUtils.kt:101-115 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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.
Edited copies of one member (3 members, 15+ corresponding lines) REDACTED:390— REDACTED:390-404 | app/src/main/java/os/kei/ui/page/main/student/BaGuideTempMediaCache.kt:28-43 | app/src/main/java/os/kei/ui/page/main/student/GameKeeMediaNetwork.kt:282-306 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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.
Edited copies of one member (3 members, 15+ corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryProfileHttpClient.kt:39— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryProfileHttpClient.kt:39-53 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitRepositoryReleaseStrategy.kt:418-432 | feature-github/src/main/java/os/kei/feature/github/domain/GitRepositoryReleaseAssetSource.kt:439-453 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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 (31 corresponding lines) · ×4
Edited copy of a member (31 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:488— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:488-522 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:452-482 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:20— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:20-70 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:76-106 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:172— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:172-214 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsPermissionKeepAliveSection.kt:415-445 — These two members are one piece of code written twice and then edited apart: 31 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 (31 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshTargetSelector.kt:20— feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshTargetSelector.kt:20-52 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshTargetSelector.kt:60-90 — These two members are one piece of code written twice and then edited apart: 31 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) · ×4
Edited copy of a member (5 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:135— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:135-139 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolSupport.kt:199-203 — 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/os/kei/ui/page/main/ba/BaAccountManagementSheet.kt:821— app/src/main/java/os/kei/ui/page/main/ba/BaAccountManagementSheet.kt:821-825 | app/src/main/java/os/kei/ui/page/main/ba/BaNotificationSettingsSheet.kt:344-352 — 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/os/kei/feature/github/notification/GitHubActionsUpdateNotificationHelper.kt:326— app/src/main/java/os/kei/feature/github/notification/GitHubActionsUpdateNotificationHelper.kt:326-330 | core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:1015-1020 — 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/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:322— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:322-326 | app/src/main/java/os/kei/ui/page/main/github/picker/GitHubTrackAppPickerModels.kt:157-162 — 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 (17 lines × 3) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:198— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:198-214 | app/src/main/java/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:229-245 | app/src/main/java/os/kei/ui/page/main/os/OsPageRowsDeriver.kt:174-190 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:198` 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 lines × 3) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:319— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:319-335 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:363-379 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:406-422 — 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/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:319` 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 lines × 3) REDACTED:82— REDACTED:82-98 | REDACTED:77-93 | REDACTED:72-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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 × 3) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:107— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:107-123 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:165-181 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:226-242 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:107` 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–15 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePrefetchController.kt:101— app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePrefetchController.kt:101-114 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePrefetchController.kt:119-133 — 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/os/kei/ui/page/main/student/page/state/BaStudentGuidePrefetchController.kt:101` 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 (14–15 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:342— app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:342-355 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:447-461 — 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/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:447` 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 (14–15 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt:200— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt:200-213 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt:215-229 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingLiquidDockSurface.kt:215` 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 (14–15 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:207— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:207-220 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:268-282 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:207` 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 (13 lines × 3) app/src/main/java/os/kei/ui/page/main/ba/BaApLimitToolsSheet.kt:50— app/src/main/java/os/kei/ui/page/main/ba/BaApLimitToolsSheet.kt:50-62 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApToolsSheet.kt:77-89 | app/src/main/java/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:118-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/ba/BaApLimitToolsSheet.kt:50` 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 (13 lines × 3) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:263— app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:263-275 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmBottomChrome.kt:492-504 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:686-698 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (13 lines × 3) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:212— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:212-224 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:422-434 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:498-510 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:212` 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 × 3) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppSwitch.kt:186— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppSwitch.kt:186-201 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:156-168 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:217-229 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppSwitch.kt:186` 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:38— app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:38-60 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:70-92 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:102-124 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:174-196 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:662— app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:662-694 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:703-728 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:737-762 | app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt:771-796 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:69— app/src/main/java/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:69-246 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:50-171 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:96-178 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:51-209 — 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 (38 corresponding lines) · ×3
Edited copy of a member (38 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:93— app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:93-133 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:883-920 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:69— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:69-110 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:81-118 — These two members are one piece of code written twice and then edited apart: 38 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 (38 corresponding lines) app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:719— app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:719-756 | app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:800-837 — These two members are one piece of code written twice and then edited apart: 38 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) · ×3
Edited copy of a member (34 corresponding lines) feature-github/src/main/java/os/kei/feature/github/install/GitHubInstallSessionWriter.kt:185— feature-github/src/main/java/os/kei/feature/github/install/GitHubInstallSessionWriter.kt:185-228 | feature-github/src/main/java/os/kei/feature/github/install/GitHubInstallSessionWriter.kt:237-270 — 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.
Edited copy of a member (34 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/install/GitHubManagedInstallRunner.kt:316— app/src/main/java/os/kei/ui/page/main/github/install/GitHubManagedInstallRunner.kt:316-349 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubManagedInstallRequestSupport.kt:67-103 — 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.
Edited copy of a member (34 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:129— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:129-166 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:188-221 — 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 (42 corresponding lines) · ×3
Edited copy of a member (42 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsRunSection.kt:36— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsRunSection.kt:36-88 | app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsWorkflowSection.kt:21-62 — These two members are one piece of code written twice and then edited apart: 42 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 (42 corresponding lines) feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:645— feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:645-686 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:696-737 — These two members are one piece of code written twice and then edited apart: 42 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 (42 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:65— app/src/main/java/os/kei/ui/page/main/ba/BaActivityCalendarPage.kt:65-106 | app/src/main/java/os/kei/ui/page/main/ba/BaPoolPage.kt:73-115 — These two members are one piece of code written twice and then edited apart: 42 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 (25 lines × 2) app/src/main/java/os/kei/ui/page/main/os/OsPageScaffold.kt:40— app/src/main/java/os/kei/ui/page/main/os/OsPageScaffold.kt:40-64 | app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePageCoordinators.kt:35-59 — 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/os/kei/ui/page/main/os/OsPageScaffold.kt:40` 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 (25 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:267— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:267-291 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:308-332 — 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 `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:267` 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 (25 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:138— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:138-162 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:190-214 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:138` 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–18 lines × 2) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:104— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:104-121 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsUpdateCheckService.kt:190-206 — 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/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:104` 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–18 lines × 2) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:163— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:163-180 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:286-302 — 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/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:163` 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/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:285` calls `cancel`, `notifyChanged` and `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:163` 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 (17–18 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:78— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:78-94 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:97-114 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:78` 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 (15 lines × 4) app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:46— app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:46-60 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:78-92 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:110-124 | app/src/main/java/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:182-196 — 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/os/kei/ui/page/main/about/section/AboutTechCardsSection.kt:46` 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 × 4) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39-53 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:119-133 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:57-71 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:104-118 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt` and `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39` 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 (15 lines × 4) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:612— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:612-626 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:83-97 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:149-163 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:201-215 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:82` calls `AppLiquidTextButton` and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:611` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–13 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:239— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:239-249 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:275-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/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:239` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–13 lines × 2) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubVersionUtils.kt:32— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubVersionUtils.kt:32-44 | feature-github/src/main/java/os/kei/feature/github/model/GitHubTrackModels.kt:213-223 — 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. 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 (11–13 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubInstalledAppRepository.kt:101— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubInstalledAppRepository.kt:101-113 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubInstalledAppRepository.kt:355-365 — 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 `feature-github/src/main/java/os/kei/feature/github/data/local/GitHubInstalledAppRepository.kt:101` 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 (10 lines × 3) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:111— app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSelectionDelegate.kt:111-120 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsService.kt:402-411 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsUpdateCheckService.kt:196-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (10 lines × 3) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:258— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:258-267 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubActionsArtifactDetailSheet.kt:292-301 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubManagedInstallConfirmSheet.kt:472-481 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:258` 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 lines × 3) feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt:226— feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt:226-235 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsArtifactManifestProbe.kt:60-69 | feature-github/src/main/java/os/kei/feature/github/install/GitHubInstallArchiveSupport.kt:50-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.
Duplicated block (9 lines × 3) app/src/main/java/os/kei/ui/page/main/student/media/GuideMediaRenderSupport.kt:44— app/src/main/java/os/kei/ui/page/main/student/media/GuideMediaRenderSupport.kt:44-52 | app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideMediaSupport.kt:22-30 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/GuideTabVoiceSupport.kt:150-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. 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 (9 lines × 3) app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidChromeCard.kt:253— app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidChromeCard.kt:253-261 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidFeedbackCard.kt:418-426 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidSearchFormCard.kt:283-291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidChromeCard.kt:253` 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:230— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:230-238 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:410-418 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:460-468 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:230` 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 × 3) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:244— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:244-248 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubActionsArtifactDetailSheet.kt:285-289 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubManagedInstallConfirmSheet.kt:458-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:251— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:251-255 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubActionsArtifactDetailSheet.kt:278-282 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubManagedInstallConfirmSheet.kt:465-469 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:251` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:72— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:72-76 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:116-120 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideGalleryFilters.kt:132-136 — 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. 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.
Low cohesion: AppMcpBaToolDelegate (LCOM4 8) app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:42— AppMcpBaToolDelegate's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: GitHubPageState (LCOM4 8) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt:30— GitHubPageState's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: GitHubActionsNotificationHistoryRepository (LCOM4 5) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryRepository.kt:21— GitHubActionsNotificationHistoryRepository's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X2 · Cancellation propagation· Suspend function with a blocking request · ×3
Suspend function with a blocking request: executeStreaming core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:822— `executeStreaming` suspends, but makes its request with `call.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: submitIssueViaApi app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueRepository.kt:135— `submitIssueViaApi` 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: downloadMediaSingleStream app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:657— `downloadMediaSingleStream` 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`.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:34— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:34-107 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:115-169 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:33-91 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:99-195 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:203-256 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:172— REDACTED:172-185 | REDACTED:242-256 | REDACTED:322-336 | REDACTED:472-486 | REDACTED:199-213 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (91 corresponding lines) · ×2
Edited copy of a member (91 corresponding lines) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:128— app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:128-218 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:237-333 — These two members are one piece of code written twice and then edited apart: 91 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 (91 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:18— app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:18-108 | app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:113-204 — These two members are one piece of code written twice and then edited apart: 91 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 (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) REDACTED:113— REDACTED:113-149 | REDACTED:149-194 — These two members are one piece of code written twice and then edited apart: 37 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 (37 corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/cache/BaCacheProviders.kt:230— app/src/main/java/os/kei/ui/page/main/settings/cache/BaCacheProviders.kt:230-275 | app/src/main/java/os/kei/ui/page/main/settings/cache/OsSystemCacheProviders.kt:75-111 — These two members are one piece of code written twice and then edited apart: 37 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 (62 corresponding lines) · ×2
Edited copy of a member (62 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:48— app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:48-109 | app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:161-227 — These two members are one piece of code written twice and then edited apart: 62 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 (62 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:159— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:159-220 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolViewModel.kt:228-289 — These two members are one piece of code written twice and then edited apart: 62 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 (53 corresponding lines) · ×2
Edited copy of a member (53 corresponding lines) REDACTED:97— REDACTED:97-157 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRefreshHistoryExportService.kt:266-318 — These two members are one piece of code written twice and then edited apart: 53 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 (53 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:171— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:171-227 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:175-227 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:112— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:112-165 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.kt:120-169 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconLoader.kt:22— app/src/main/java/os/kei/ui/page/main/github/page/GitHubAppIconLoader.kt:22-71 | app/src/main/java/os/kei/ui/page/main/os/OsActivityShortcutIconLoader.kt:89-145 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×2
Edited copy of a member (41 corresponding lines) app/src/main/java/os/kei/core/background/AppBackgroundSchedulePolicy.kt:129— app/src/main/java/os/kei/core/background/AppBackgroundSchedulePolicy.kt:129-171 | app/src/main/java/os/kei/core/background/AppBackgroundSchedulePolicy.kt:176-216 — 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/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:8— app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:8-48 | app/src/main/java/os/kei/ui/page/main/github/state/GitHubCheckStateMappers.kt:50-91 — 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 copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:15— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:15-25 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionVoice.kt:254-274 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/GuideTabVoiceSupport.kt:9-23 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) app/src/main/java/os/kei/ui/page/main/debug/DebugActivitySupport.kt:17— app/src/main/java/os/kei/ui/page/main/debug/DebugActivitySupport.kt:17-27 | app/src/main/java/os/kei/ui/page/main/feedback/FeedbackIssueActivity.kt:143-154 | app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportActivity.kt:63-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:105— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:105-134 | feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:141-170 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) scripts/perf/frame_stages.py:18— scripts/perf/frame_stages.py:18-51 | scripts/perf/switch_report.py:10-39 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×2
Edited copies of one member (3 members, 28+ corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:124— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:124-158 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:207-234 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubAtomReleaseStrategy.kt:239-266 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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.
Edited copies of one member (3 members, 28+ corresponding lines) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:58— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:58-85 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:98-126 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:139-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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, 20+ corresponding lines) · ×2
Edited copies of one member (3 members, 20+ corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:236— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubApiTokenReleaseStrategy.kt:236-255 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:148-168 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubRepositoryDiscoveryRepository.kt:170-190 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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.
Edited copies of one member (3 members, 20+ corresponding lines) core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:434— core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:434-458 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:471-490 | core-notification/src/main/java/os/kei/core/notification/focus/MiFocusOfficialTemplateCatalog.kt:503-522 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubDirectApkReleaseCheckSource.kt:361— feature-github/src/main/java/os/kei/feature/github/domain/GitHubDirectApkReleaseCheckSource.kt:361-379 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleaseCheckService.kt:465-480 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidReleaseCheckSource.kt:344-359 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:996— app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:996-1011 | app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:1013-1028 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationActions.kt:116-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidGlassBottomSheet.kt:256— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidGlassBottomSheet.kt:256-268 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetLayout.kt:13-21 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetLayout.kt:41-47 — 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.
Edited copies of one member (3 members, 7+ corresponding lines) app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:179— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:179-185 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:15-21 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:23-31 — 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 (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:21— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDecisionAssistDetailPrimitives.kt:21-25 | app/src/main/java/os/kei/ui/page/main/mcp/util/McpPageUtils.kt:31-34 — 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) core-download/src/main/java/os/kei/core/download/segmented/RateProbeIdleTracker.kt:24— core-download/src/main/java/os/kei/core/download/segmented/RateProbeIdleTracker.kt:24-27 | core-download/src/main/java/os/kei/core/download/segmented/TailIdleTracker.kt:35-39 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (32 lines × 2) app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:349— app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:349-380 | app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:507-538 — 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/os/kei/ui/page/main/about/page/AboutPage.kt:349` 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 (32 lines × 2) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:215— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:215-246 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:297-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:215` 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 (31 lines × 2) app/src/main/java/os/kei/ui/page/main/github/GitHubStrategyCards.kt:27— app/src/main/java/os/kei/ui/page/main/github/GitHubStrategyCards.kt:27-57 | app/src/main/java/os/kei/ui/page/main/github/GitHubStrategyCards.kt:65-95 — 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `guide` to `GitHubStrategyGuide` in one and `GitHubActionsStrategyGuide` 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 (31 lines × 2) app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:248— app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:248-278 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:306-336 — 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/os/kei/ui/page/main/os/shell/state/OsShellRunnerOutputState.kt:248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:386— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:386-411 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:661-686 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:386` 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 (26 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:157— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:157-182 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:218-243 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:157` 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 (24 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:103— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:103-126 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:101-124 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt` and `app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:103` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:102` calls `getString` and `app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:100` 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 (24 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:130— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:130-153 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:189-212 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:130` 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) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:184— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:184-205 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:262-283 — 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:184` 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 (22 lines × 2) core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:134— core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:134-155 | core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:223-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 `core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 2) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:411— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:411-429 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:482-501 — 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/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:411` 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 (19–20 lines × 2) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:202— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:202-221 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideSidebar.kt:179-197 — 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/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:202` 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 (18–19 lines × 2) app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:429— app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:429-447 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStore.kt:830-847 — 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/os/kei/feature/home/data/HomeOverviewRepository.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 (18–19 lines × 2) app/src/main/java/os/kei/ui/page/main/os/components/OsPageSections.kt:144— app/src/main/java/os/kei/ui/page/main/os/components/OsPageSections.kt:144-162 | app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:158-175 — 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/os/kei/ui/page/main/os/components/OsPageSections.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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/os/components/OsShellCommandCardSheets.kt:176` calls `stringResource` and `app/src/main/java/os/kei/ui/page/main/os/components/OsPageSections.kt:162` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 3) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:259— app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:259-270 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:283-294 | app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:307-318 — 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/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:259` 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 × 3) REDACTED:90— REDACTED:90-101 | REDACTED:127-138 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubActionsRecommendedRunStore.kt:79-90 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:824— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:824-833 | app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:83-93 — 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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:824` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryInlineVideoPlayerBody.kt:82` calls `aspectRatio` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:823` 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 (10–11 lines × 2) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideArchiveTabContent.kt:62— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideArchiveTabContent.kt:62-72 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideNpcSatelliteArchiveContent.kt:51-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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/os/kei/ui/page/main/student/tabcontent/render/GuideArchiveTabContent.kt:62` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideNpcSatelliteArchiveContent.kt:50` calls `GuideProfileSectionHeader`, `stringResource` and `app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideArchiveTabContent.kt:61` 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 (7–8 lines × 2) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:309— app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:309-315 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:413-420 — 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/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:309` 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 (7–8 lines × 2) core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:67— core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:67-74 | core-notification/src/main/java/os/kei/core/notification/live/builder/ModernNotificationBuilder.kt:57-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core-notification/src/main/java/os/kei/core/notification/live/builder/LegacyNotificationBuilder.kt:67` 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 (15 lines × 3) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:240— app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:240-254 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:420-434 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:470-484 — 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/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:240` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:435` calls `isNotEmpty` and `app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:486` 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 (15 lines × 3) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:30— app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:30-44 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:103-117 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:144-158 — 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/os/kei/ui/page/main/github/page/GitHubPageRefreshNotificationBridge.kt:30` 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.
GitHubWidgetRenderer.layout (cyclomatic 88) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:42— GitHubWidgetRenderer.layout has cyclomatic complexity 88 (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.
GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson (cyclomatic 85) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:124— GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson has cyclomatic complexity 85 (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.
LiquidGlassBottomBarKt.LiquidGlassBottomBar (cyclomatic 78) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt:216— LiquidGlassBottomBarKt.LiquidGlassBottomBar has cyclomatic complexity 78 (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.
GuideWeaponCardHelperKt.weaponCardForDisplay (cyclomatic 61) app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:32— GuideWeaponCardHelperKt.weaponCardForDisplay has cyclomatic complexity 61 (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.
GuideFetchArrayContentParserKt.parseGuideDetailFromArrayContentJson (cyclomatic 59) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayContentParser.kt:36— GuideFetchArrayContentParserKt.parseGuideDetailFromArrayContentJson has cyclomatic complexity 59 (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.
LiquidSheetKt.LiquidSheetPresentation (cyclomatic 57) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.kt:137— LiquidSheetKt.LiquidSheetPresentation has cyclomatic complexity 57 (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.
GitHubReleaseEvaluationEngine.evaluate (cyclomatic 55) feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt:65— GitHubReleaseEvaluationEngine.evaluate has cyclomatic complexity 55 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage (cyclomatic 51) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:106— GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage 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.
GitHubActionsWorkflowSelector.matchWorkflow (cyclomatic 50) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsWorkflowSelector.kt:136— GitHubActionsWorkflowSelector.matchWorkflow has cyclomatic complexity 50 (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.
GitHubActionsErrorLocalizationKt.localizedGitHubPageErrorMessage (cyclomatic 46) app/src/main/java/os/kei/ui/page/main/github/GitHubActionsErrorLocalization.kt:233— GitHubActionsErrorLocalizationKt.localizedGitHubPageErrorMessage has cyclomatic complexity 46 (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.
GuideFetchGalleryKt.parseGalleryItemsFromBaseData (cyclomatic 46) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:88— GuideFetchGalleryKt.parseGalleryItemsFromBaseData has cyclomatic complexity 46 (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.
GuideFetchSimulateKt.parseSimulateRowsFromBaseData (cyclomatic 46) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:114— GuideFetchSimulateKt.parseSimulateRowsFromBaseData has cyclomatic complexity 46 (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.
GuideGalleryExpressionSectionKt.GuideGalleryExpressionCardItem (cyclomatic 45) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:129— GuideGalleryExpressionSectionKt.GuideGalleryExpressionCardItem has cyclomatic complexity 45 (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.
SegmentedDownloadClient.downloadPart (cyclomatic 44) core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:374— SegmentedDownloadClient.downloadPart has cyclomatic complexity 44 (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.
GuideGalleryTabContentSectionsKt.renderGuideGalleryStateContent (cyclomatic 43) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:36— GuideGalleryTabContentSectionsKt.renderGuideGalleryStateContent has cyclomatic complexity 43 (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.
GitHubActionsRunSelector.matchRun (cyclomatic 42) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRunSelector.kt:103— GitHubActionsRunSelector.matchRun has cyclomatic complexity 42 (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.
AboutPageKt.AboutPage (cyclomatic 41) app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:70— AboutPageKt.AboutPage has cyclomatic complexity 41 (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.
GuideFetchVoiceKt.parseVoiceDataFromBaseData (cyclomatic 41) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:81— GuideFetchVoiceKt.parseVoiceDataFromBaseData has cyclomatic complexity 41 (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.
GuideModel3dPlayerKt.GuideModel3dPlayer (cyclomatic 41) app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt:40— GuideModel3dPlayerKt.GuideModel3dPlayer has cyclomatic complexity 41 (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.
GitHubActionsArtifactSelector.matchArtifact (cyclomatic 41) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt:107— GitHubActionsArtifactSelector.matchArtifact has cyclomatic complexity 41 (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.
GitHubActionsErrorLocalizationKt.localizedGitHubActionsErrorMessage (cyclomatic 40) app/src/main/java/os/kei/ui/page/main/github/GitHubActionsErrorLocalization.kt:10— GitHubActionsErrorLocalizationKt.localizedGitHubActionsErrorMessage has cyclomatic complexity 40 (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.
HomePageContentDeriverKt.deriveHomePageContentState (cyclomatic 40) app/src/main/java/os/kei/ui/page/main/home/state/HomePageContentDeriver.kt:18— HomePageContentDeriverKt.deriveHomePageContentState has cyclomatic complexity 40 (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.
GitHubTrackEditFormContentKt.GitHubTrackEditFormContent (cyclomatic 39) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:50— GitHubTrackEditFormContentKt.GitHubTrackEditFormContent has cyclomatic complexity 39 (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.
OsTopInfoDataKt.topInfoTopicOf (cyclomatic 39) app/src/main/java/os/kei/ui/page/main/os/OsTopInfoData.kt:44— OsTopInfoDataKt.topInfoTopicOf has cyclomatic complexity 39 (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.
BaGuideStudentBgmTabContentKt.BaGuideStudentBgmTabContent (cyclomatic 37) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:71— BaGuideStudentBgmTabContentKt.BaGuideStudentBgmTabContent has cyclomatic complexity 37 (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.
BaCalendarPoolPageKt.BaCalendarPoolPage (cyclomatic 36) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:81— BaCalendarPoolPageKt.BaCalendarPoolPage has cyclomatic complexity 36 (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.
GuideSectionSkillKt.GuideSkillCardItem (cyclomatic 36) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionSkill.kt:53— GuideSectionSkillKt.GuideSkillCardItem has cyclomatic complexity 36 (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.
GuideGalleryMediaRendererKt.GuideGalleryCardContent (cyclomatic 36) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryMediaRenderer.kt:53— GuideGalleryMediaRendererKt.GuideGalleryCardContent has cyclomatic complexity 36 (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.
OsOverviewMetricsKt.buildOsOverviewUiState (cyclomatic 35) app/src/main/java/os/kei/ui/page/main/os/OsOverviewMetrics.kt:90— OsOverviewMetricsKt.buildOsOverviewUiState has cyclomatic complexity 35 (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.
GitHubAtomReleaseStrategy.parseAtomFeed (cyclomatic 34) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubAtomReleaseStrategy.kt:377— GitHubAtomReleaseStrategy.parseAtomFeed has cyclomatic complexity 34 (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.
AppLiquidButtonsKt.AppLiquidTextButton (cyclomatic 34) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:545— AppLiquidButtonsKt.AppLiquidTextButton has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiquidSurfacesKt.LiquidSurface (cyclomatic 34) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt:79— LiquidSurfacesKt.LiquidSurface has cyclomatic complexity 34 (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.
MainPagerLayoutKt.MainPagerLayout (cyclomatic 32) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt:78— MainPagerLayoutKt.MainPagerLayout has cyclomatic complexity 32 (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.
BaGuideMemoryLobbyTabContentKt.BaGuideMemoryLobbyTabContent (cyclomatic 32) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:73— BaGuideMemoryLobbyTabContentKt.BaGuideMemoryLobbyTabContent has cyclomatic complexity 32 (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.
GuideSectionGalleryKt.GuideGalleryCardItem (cyclomatic 32) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionGallery.kt:41— GuideSectionGalleryKt.GuideGalleryCardItem has cyclomatic complexity 32 (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.
GlassStyleKt.glassStyle (cyclomatic 32) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:47— GlassStyleKt.glassStyle has cyclomatic complexity 32 (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.
frame-presentation.keiosCreateFramePresenter.present (cyclomatic 32) app/src/main/assets/ba3d/frame-presentation.js:28— frame-presentation.keiosCreateFramePresenter.present has cyclomatic complexity 32 (threshold 15). Of this number, 27 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubPageContentStateDeriver.build (cyclomatic 31) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:46— GitHubPageContentStateDeriver.build has cyclomatic complexity 31 (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.
SettingsSearchCardRendererKt.SettingsSearchCardContent (cyclomatic 31) app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSearchCardRenderer.kt:52— SettingsSearchCardRendererKt.SettingsSearchCardContent has cyclomatic complexity 31 (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.
BaGuideBgmBottomChromeKt.BaGuideBgmFloatingBottomChrome (cyclomatic 31) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmBottomChrome.kt:64— BaGuideBgmBottomChromeKt.BaGuideBgmFloatingBottomChrome has cyclomatic complexity 31 (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.
GuideFetchGiftKt.parseGiftPreferenceRowsFromBaseData (cyclomatic 31) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGift.kt:86— GuideFetchGiftKt.parseGiftPreferenceRowsFromBaseData has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GuideMediaSaveRequestBuilderKt.inferGuideMediaExtFromLocalFile (cyclomatic 31) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaSaveRequestBuilder.kt:102— GuideMediaSaveRequestBuilderKt.inferGuideMediaExtFromLocalFile has cyclomatic complexity 31 (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.
GitHubTrackActions.applyTrackSheet (cyclomatic 30) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:507— GitHubTrackActions.applyTrackSheet has cyclomatic complexity 30 (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.
GuideGalleryAudioPlayerStateKt.BindGuideGalleryAudioPlayerEffects (cyclomatic 29) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryAudioPlayerState.kt:188— GuideGalleryAudioPlayerStateKt.BindGuideGalleryAudioPlayerEffects 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.
GuideGalleryFullscreenKt.GuideImageFullscreenDialog (cyclomatic 29) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryFullscreen.kt:72— GuideGalleryFullscreenKt.GuideImageFullscreenDialog has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebDavPayloadValidationKt.validateWebDavPayload (cyclomatic 28) app/src/main/java/os/kei/ui/page/main/sync/WebDavPayloadValidation.kt:9— WebDavPayloadValidationKt.validateWebDavPayload has cyclomatic complexity 28 (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.
GitHubRefreshBatchActions.refreshTrackedBatchInternal (cyclomatic 27) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubRefreshBatchActions.kt:38— GitHubRefreshBatchActions.refreshTrackedBatchInternal has cyclomatic complexity 27 (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.
GitHubMainContentSectionKt.GitHubMainContent (cyclomatic 27) app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:75— GitHubMainContentSectionKt.GitHubMainContent has cyclomatic complexity 27 (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.
HomePageDerivedStateKt.rememberHomePageOverviewCardState (cyclomatic 27) app/src/main/java/os/kei/ui/page/main/home/state/HomePageDerivedState.kt:246— HomePageDerivedStateKt.rememberHomePageOverviewCardState has cyclomatic complexity 27 (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.
SettingsBackgroundSectionKt.SettingsBackgroundSection (cyclomatic 27) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:67— SettingsBackgroundSectionKt.SettingsBackgroundSection 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.
MiIslandNotificationBuilder.build (cyclomatic 27) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:127— MiIslandNotificationBuilder.build has cyclomatic complexity 27 (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.
GitHubTrackStoreSerializersKt.parseTrackedItem (cyclomatic 27) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:33— GitHubTrackStoreSerializersKt.parseTrackedItem has cyclomatic complexity 27 (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.
GitHubPageDiscoveryRepository.buildTrackedItem (cyclomatic 26) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageDiscoveryRepository.kt:67— GitHubPageDiscoveryRepository.buildTrackedItem has cyclomatic complexity 26 (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.
BaGuideCatalogV2ListContentKt.BaGuideCatalogV2ListContent (cyclomatic 26) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:59— BaGuideCatalogV2ListContentKt.BaGuideCatalogV2ListContent has cyclomatic complexity 26 (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.
AppFloatingSearchDockMotionKt.rememberAppFloatingVerticalSearchDockMotion (cyclomatic 26) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDockMotion.kt:28— AppFloatingSearchDockMotionKt.rememberAppFloatingVerticalSearchDockMotion has cyclomatic complexity 26 (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.
AppLiquidSearchFieldKt.AppLiquidInputField (cyclomatic 26) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:53— AppLiquidSearchFieldKt.AppLiquidInputField 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.
GitHubWidgetConfigurationScreenKt.GitHubWidgetConfigurationScreen (cyclomatic 25) app/src/main/java/os/kei/appwidget/github/GitHubWidgetConfigurationScreen.kt:41— GitHubWidgetConfigurationScreenKt.GitHubWidgetConfigurationScreen has cyclomatic complexity 25 (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.
GitHubWidgetRenderer.renderProjects (cyclomatic 25) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:262— GitHubWidgetRenderer.renderProjects 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.
GuideSkillCardHelperKt.parseBaseSkillDrafts (cyclomatic 25) app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:89— GuideSkillCardHelperKt.parseBaseSkillDrafts has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaStudentGuideRepository.loadGuide (cyclomatic 25) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideRepository.kt:304— BaStudentGuideRepository.loadGuide 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.
AppLiquidButtonsKt.AppLiquidIconButtonContainer (cyclomatic 25) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:265— AppLiquidButtonsKt.AppLiquidIconButtonContainer has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GuideWebMemoryLobbyPlayerKt.GuideWebMemoryLobbyPlayer (cyclomatic 24) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt:52— GuideWebMemoryLobbyPlayerKt.GuideWebMemoryLobbyPlayer has cyclomatic complexity 24 (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.
MiIslandNotificationBuilder.resolvePresentation (cyclomatic 24) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:539— MiIslandNotificationBuilder.resolvePresentation has cyclomatic complexity 24 (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.
GitHubActionsRunSelector.inspectRun (cyclomatic 24) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRunSelector.kt:15— GitHubActionsRunSelector.inspectRun has cyclomatic complexity 24 (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.
GitHubActionsRunTracker.buildTrackingPlan (cyclomatic 24) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRunTracker.kt:9— GitHubActionsRunTracker.buildTrackingPlan has cyclomatic complexity 24 (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.
McpGitHubTrackingTools.filterTrackedItems (cyclomatic 24) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:223— McpGitHubTrackingTools.filterTrackedItems has cyclomatic complexity 24 (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.
viewer.presentationRegion (cyclomatic 24) app/src/main/assets/ba3d/viewer.js:221— viewer.presentationRegion has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 224). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
GitHubPageKt.GitHubPage (cyclomatic 23) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt:54— GitHubPageKt.GitHubPage has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubTrackedItemHeaderActionsKt.gitHubTrackedItemHeaderActionState (cyclomatic 23) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemHeaderActions.kt:138— GitHubTrackedItemHeaderActionsKt.gitHubTrackedItemHeaderActionState has cyclomatic complexity 23 (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.
OsGoogleSystemServiceSuggestionResolverKt.rememberOsGoogleSystemServiceSuggestionUiState (cyclomatic 23) app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceSuggestionResolver.kt:38— OsGoogleSystemServiceSuggestionResolverKt.rememberOsGoogleSystemServiceSuggestionUiState has cyclomatic complexity 23 (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.
BaStudentGuideMediaSaveActionsKt.BindBaStudentGuideMediaSaveEvents (cyclomatic 23) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideMediaSaveActions.kt:24— BaStudentGuideMediaSaveActionsKt.BindBaStudentGuideMediaSaveEvents has cyclomatic complexity 23 (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.
WebDavSyncCardsKt.WebDavSyncBatchActionsCard (cyclomatic 23) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:316— WebDavSyncCardsKt.WebDavSyncBatchActionsCard has cyclomatic complexity 23 (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.
OsPageMainListKt.OsPageMainList (cyclomatic 22) app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.kt:155— OsPageMainListKt.OsPageMainList 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.
GuideFetchVoiceKt.parseVoiceCvByLanguageFromBaseData (cyclomatic 22) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:262— GuideFetchVoiceKt.parseVoiceCvByLanguageFromBaseData has cyclomatic complexity 22 (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.
GuideGalleryTabContentStateKt.resolveGuideGalleryTabState (cyclomatic 22) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentState.kt:56— GuideGalleryTabContentStateKt.resolveGuideGalleryTabState has cyclomatic complexity 22 (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.
AppMarkdownParserKt.parseAppMarkdownBlocks (cyclomatic 22) app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownParser.kt:24— AppMarkdownParserKt.parseAppMarkdownBlocks 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.
MiIslandNotificationBuilder.buildFocusExtras (cyclomatic 22) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:256— MiIslandNotificationBuilder.buildFocusExtras has cyclomatic complexity 22 (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.
AppSwitchKt.LiquidSwitchToggle (cyclomatic 22) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppSwitch.kt:178— AppSwitchKt.LiquidSwitchToggle 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.
SheetStylesKt.SheetChoiceCard (cyclomatic 22) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/SheetStyles.kt:386— SheetStylesKt.SheetChoiceCard 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.
McpPageKt.McpPage (cyclomatic 21) app/src/main/java/os/kei/ui/page/main/mcp/McpPage.kt:52— McpPageKt.McpPage has cyclomatic complexity 21 (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.
McpSkillMarkdownParserKt.buildSkillSections (cyclomatic 21) app/src/main/java/os/kei/ui/page/main/mcp/skill/support/McpSkillMarkdownParser.kt:11— McpSkillMarkdownParserKt.buildSkillSections has cyclomatic complexity 21 (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.
GitHubRepositoryHealthEvaluator.evaluate (cyclomatic 21) feature-github-engine/src/main/java/os/kei/feature/github/domain/GitHubRepositoryHealthEvaluator.kt:10— GitHubRepositoryHealthEvaluator.evaluate has cyclomatic complexity 21 (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. This is NOT this file's highest cyclomatic complexity: GitHubRepositoryHealthEvaluator.impactFor (cyclomatic 32) 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.
GitHubRepositoryProfileCacheJsonKt.inferCapabilities (cyclomatic 21) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubRepositoryProfileCacheJson.kt:481— GitHubRepositoryProfileCacheJsonKt.inferCapabilities has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubTrackedRefreshBatchRunner.run (cyclomatic 21) feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:175— GitHubTrackedRefreshBatchRunner.run has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppFloatingSearchDockKt.AppFloatingSearchDock (cyclomatic 21) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:89— AppFloatingSearchDockKt.AppFloatingSearchDock has cyclomatic complexity 21 (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.
AppLiquidCheckboxKt.AppLiquidCheckbox (cyclomatic 21) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:45— AppLiquidCheckboxKt.AppLiquidCheckbox has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiquidSliderVariantsKt.LiquidTrackSlider (cyclomatic 21) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:266— LiquidSliderVariantsKt.LiquidTrackSlider has cyclomatic complexity 21 (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.
GitHubWidgetProjectionKt.projectGitHubWidget (cyclomatic 20) app/src/main/java/os/kei/appwidget/github/GitHubWidgetProjection.kt:13— GitHubWidgetProjectionKt.projectGitHubWidget has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitHubActionsNotificationHistoryActionBarKt.GitHubActionsNotificationHistoryActionBar (cyclomatic 20) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:39— GitHubActionsNotificationHistoryActionBarKt.GitHubActionsNotificationHistoryActionBar has cyclomatic complexity 20 (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.
HomePageDerivedStateKt.rememberHomePageHeroMotionState (cyclomatic 20) app/src/main/java/os/kei/ui/page/main/home/state/HomePageDerivedState.kt:66— HomePageDerivedStateKt.rememberHomePageHeroMotionState has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OsGoogleSystemServiceSuggestionSheetKt.OsGoogleSystemServiceSuggestionSheet (cyclomatic 20) app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceSuggestionSheet.kt:37— OsGoogleSystemServiceSuggestionSheetKt.OsGoogleSystemServiceSuggestionSheet has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VivoAtomicAdapter.plan (cyclomatic 20) core-notification/src/main/java/os/kei/core/notification/live/oem/vivo/VivoAtomicAdapter.kt:35— VivoAtomicAdapter.plan has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppDropdownControlsKt.AppDropdownSelector (cyclomatic 20) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:118— AppDropdownControlsKt.AppDropdownSelector has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitHubStarImportComponentsKt.StarImportStatusCard (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportComponents.kt:331— GitHubStarImportComponentsKt.StarImportStatusCard 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.
GitHubStarImportModelsKt.buildStarImportCandidateListUiState (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:146— GitHubStarImportModelsKt.buildStarImportCandidateListUiState has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubTrackedItemAssetPanelKt.GitHubTrackedItemAssetPanel (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanel.kt:36— GitHubTrackedItemAssetPanelKt.GitHubTrackedItemAssetPanel 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.
GitHubStrategySheetKt.GitHubStrategySheet (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:58— GitHubStrategySheetKt.GitHubStrategySheet 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.
SettingsPermissionKeepAliveSupportKt.resolveOemAutoStartVendor (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPermissionKeepAliveSupport.kt:662— SettingsPermissionKeepAliveSupportKt.resolveOemAutoStartVendor 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.
BaGuideStudentBgmCardsKt.BaGuideStudentBgmCard (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:153— BaGuideStudentBgmCardsKt.BaGuideStudentBgmCard 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.
GuideFetchSimulateKt.collectSimulateSupplementIcons (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:30— GuideFetchSimulateKt.collectSimulateSupplementIcons has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GuideFetchJsonContentTokenizerKt.tokenizeGuideBaseRows (cyclomatic 19) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentTokenizer.kt:20— GuideFetchJsonContentTokenizerKt.tokenizeGuideBaseRows has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppFloatingSearchDockKt.AppFloatingVerticalSearchActionDock (cyclomatic 19) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:226— AppFloatingSearchDockKt.AppFloatingVerticalSearchActionDock 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.
model-skin-bounds.createSkinBounds::build (cyclomatic 19) app/src/main/assets/ba3d/model-skin-bounds.js:9— model-skin-bounds.createSkinBounds::build has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubActionsArtifactCardKt.GitHubActionsArtifactCard (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactCard.kt:33— GitHubActionsArtifactCardKt.GitHubActionsArtifactCard 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.
GitHubReleaseListPageKt.GitHubReleaseCard (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:486— GitHubReleaseListPageKt.GitHubReleaseCard 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.
GitHubTrackedItemMoreMenuKt.GitHubTrackedItemMoreActions (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.kt:63— GitHubTrackedItemMoreMenuKt.GitHubTrackedItemMoreActions 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.
MainScreenKt.MainScreen (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt:31— MainScreenKt.MainScreen 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.
SettingsCacheSectionKt.SettingsCacheSection (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsCacheSection.kt:30— SettingsCacheSectionKt.SettingsCacheSection has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebDavSyncCardsKt.WebDavSyncItemRow (cyclomatic 18) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:489— WebDavSyncCardsKt.WebDavSyncItemRow 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.
GitHubApkPackageNameScanRepository.loadScanReleaseApkAssets (cyclomatic 18) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubApkPackageNameScanRepository.kt:25— GitHubApkPackageNameScanRepository.loadScanReleaseApkAssets has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubRepositoryDiscoveryService.withAppSearchScore (cyclomatic 18) feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:301— GitHubRepositoryDiscoveryService.withAppSearchScore 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.
McpKeepAliveService.onStartCommand (cyclomatic 18) feature-mcp/src/main/java/os/kei/mcp/service/McpKeepAliveService.kt:48— McpKeepAliveService.onStartCommand has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebDavSyncClient.request (cyclomatic 18) feature-webdav/src/main/java/os/kei/feature/webdav/client/WebDavSyncClient.kt:216— WebDavSyncClient.request has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LiquidGlassActionMenuKt.LiquidGlassActionMenu (cyclomatic 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:153— LiquidGlassActionMenuKt.LiquidGlassActionMenu 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.
LiquidGlassDropdownItemsKt.LiquidGlassDropdownRowContent (cyclomatic 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:411— LiquidGlassDropdownItemsKt.LiquidGlassDropdownRowContent 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.
LiquidSurfacesKt.AppLiquidFloatingSurface (cyclomatic 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt:542— LiquidSurfacesKt.AppLiquidFloatingSurface 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.
SheetGlassNode.draw (cyclomatic 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/SheetGlassBackdrop.kt:281— SheetGlassNode.draw 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.
AppForegroundInfoHandler.cleanupGitHubRefreshRuntimeAndNotification (cyclomatic 17) app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:286— AppForegroundInfoHandler.cleanupGitHubRefreshRuntimeAndNotification has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PredictiveBackOemCompat.resolveRomFamily (cyclomatic 17) app/src/main/java/os/kei/core/platform/PredictiveBackOemCompat.kt:107— PredictiveBackOemCompat.resolveRomFamily has cyclomatic complexity 17 (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.
GitHubAssetPanelActions.loadApkAssets (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:30— GitHubAssetPanelActions.loadApkAssets has cyclomatic complexity 17 (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.
GitHubAssetPanelActions.loadFdroidApkAssets (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:192— GitHubAssetPanelActions.loadFdroidApkAssets has cyclomatic complexity 17 (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.
GitHubTrackAppPickerContentKt.GitHubTrackAppPickerContent (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackAppPickerContent.kt:271— GitHubTrackAppPickerContentKt.GitHubTrackAppPickerContent has cyclomatic complexity 17 (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.
MainPagerBottomBarKt.MainPagerBottomBar (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:60— MainPagerBottomBarKt.MainPagerBottomBar has cyclomatic complexity 17 (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.
OsShellRunnerPageActionsKt.rememberOsShellRunnerPageActionsInternal (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerPageActions.kt:80— OsShellRunnerPageActionsKt.rememberOsShellRunnerPageActionsInternal has cyclomatic complexity 17 (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.
BaGuideCatalogTransferActionsKt.rememberBaGuideCatalogJsonExportAction (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferActions.kt:39— BaGuideCatalogTransferActionsKt.rememberBaGuideCatalogJsonExportAction has cyclomatic complexity 17 (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.
GuideProfileTabContentKt.renderGuideProfileTabContent (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabContent.kt:32— GuideProfileTabContentKt.renderGuideProfileTabContent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GuideSimulateDataAssemblerKt.expandSimulateRows (cyclomatic 17) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateDataAssembler.kt:100— GuideSimulateDataAssemblerKt.expandSimulateRows has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubPackageRepositoryResolver.withPackageSearchScore (cyclomatic 17) feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:208— GitHubPackageRepositoryResolver.withPackageSearchScore has cyclomatic complexity 17 (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.
GitHubReleasePackageScope.resolve (cyclomatic 17) feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleasePackageScope.kt:26— GitHubReleasePackageScope.resolve has cyclomatic complexity 17 (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.
BaPageEffectsKt.BaPageCommonEffects (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/ba/BaPageEffects.kt:166— BaPageEffectsKt.BaPageCommonEffects 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.
FdroidVersionListPageKt.FdroidVersionCard (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:526— FdroidVersionListPageKt.FdroidVersionCard has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GitHubTrackEditorPersistenceKt.persistTrackEditorSave (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackEditorPersistence.kt:23— GitHubTrackEditorPersistenceKt.persistTrackEditorSave 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.
GitHubOverviewSectionKt.GitHubOverviewCard (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/github/section/GitHubOverviewSection.kt:69— GitHubOverviewSectionKt.GitHubOverviewCard 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.
SettingsPageKt.SettingsPage (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:69— SettingsPageKt.SettingsPage 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.
SettingsVisualSectionKt.SettingsVisualSection (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsVisualSection.kt:29— SettingsVisualSectionKt.SettingsVisualSection has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaGuideBgmAlbumHeroKt.BaGuideBgmAlbumHero (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:40— BaGuideBgmAlbumHeroKt.BaGuideBgmAlbumHero 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.
GuideFetchParserCommonKt.mapGuideTabByLabel (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:51— GuideFetchParserCommonKt.mapGuideTabByLabel 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. This is NOT this file's highest cyclomatic complexity: GuideFetchParserCommonKt.guideGalleryCategoryOrder (cyclomatic 18) 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.
AppMarkdownParserKt.parseAppMarkdownInlineTokens (cyclomatic 16) app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownParser.kt:251— AppMarkdownParserKt.parseAppMarkdownInlineTokens 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.
GitHubActionsRepository.fetchWorkflowArtifactSnapshotOnCurrentDispatcher (cyclomatic 16) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:354— GitHubActionsRepository.fetchWorkflowArtifactSnapshotOnCurrentDispatcher 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.
GitHubTrackChangeHistoryService.significantChangeFields (cyclomatic 16) feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackChangeHistoryService.kt:142— GitHubTrackChangeHistoryService.significantChangeFields 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.
McpGitHubTrackingToolsHelpersKt.sortTrackedItems (cyclomatic 16) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:169— McpGitHubTrackingToolsHelpersKt.sortTrackedItems 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. This shape REPEATS in the file: one other method here (McpGitHubTrackingToolsHelpersKt.sortCheckRows) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: McpGitHubTrackingToolsHelpersKt.parseGitHubTrackedFilterMode (cyclomatic 29) 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.
McpGitHubTrackingToolsHelpersKt.sortCheckRows (cyclomatic 16) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:266— McpGitHubTrackingToolsHelpersKt.sortCheckRows 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. This shape REPEATS in the file: one other method here (McpGitHubTrackingToolsHelpersKt.sortTrackedItems) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: McpGitHubTrackingToolsHelpersKt.parseGitHubTrackedFilterMode (cyclomatic 29) 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.
model-skin-bounds.createSkinBounds.<returned closure> (cyclomatic 16) app/src/main/assets/ba3d/model-skin-bounds.js:35— model-skin-bounds.createSkinBounds.<returned closure> has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LiquidGlassBottomBarKt.LiquidGlassBottomBar (cognitive 139) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt:216— LiquidGlassBottomBarKt.LiquidGlassBottomBar has cognitive complexity 139 (threshold 15). Drivers by points: if/else 93 (120 pts), boolean chains 17, match/switch 1 (2 pts) (nesting depth added 28). 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.
GitHubWidgetRenderer.layout (cognitive 126) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:42— GitHubWidgetRenderer.layout has cognitive complexity 126 (threshold 15). Drivers by points: if/else 74 (101 pts), boolean chains 14, match/switch 7 (11 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.
GuideWeaponCardHelperKt.weaponCardForDisplay (cognitive 120) app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.kt:32— GuideWeaponCardHelperKt.weaponCardForDisplay has cognitive complexity 120 (threshold 15). Drivers by points: if/else 44 (99 pts), boolean chains 16, match/switch 2 (4 pts), loops 1 (nesting depth added 57). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson (cognitive 106) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentParser.kt:124— GuideFetchJsonContentParserKt.parseGuideDetailFromObjectContentJson has cognitive complexity 106 (threshold 15). Drivers by points: if/else 51 (69 pts), boolean chains 36, match/switch 1 (nesting depth added 18). 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.
GuideFetchGalleryKt.parseGalleryItemsFromBaseData (cognitive 103) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:88— GuideFetchGalleryKt.parseGalleryItemsFromBaseData has cognitive complexity 103 (threshold 15). Drivers by points: if/else 40 (87 pts), loops 5 (9 pts), boolean chains 4, match/switch 1 (3 pts) (nesting depth added 53). 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.
GuideFetchArrayContentParserKt.parseGuideDetailFromArrayContentJson (cognitive 95) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchArrayContentParser.kt:36— GuideFetchArrayContentParserKt.parseGuideDetailFromArrayContentJson has cognitive complexity 95 (threshold 15). Drivers by points: if/else 36 (66 pts), loops 9 (15 pts), boolean chains 9, match/switch 3 (5 pts) (nesting depth added 38). 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.
GuideFetchVoiceKt.parseVoiceDataFromBaseData (cognitive 92) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:81— GuideFetchVoiceKt.parseVoiceDataFromBaseData has cognitive complexity 92 (threshold 15). Drivers by points: if/else 34 (74 pts), loops 7 (13 pts), boolean chains 5 (nesting depth added 46). 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.
SegmentedDownloadClient.downloadPart (cognitive 82) core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:374— SegmentedDownloadClient.downloadPart has cognitive complexity 82 (threshold 15). Drivers by points: if/else 38 (72 pts), loops 4 (5 pts), boolean chains 4, error handling 1 (nesting depth added 35). 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.
AppLiquidButtonsKt.AppLiquidTextButton (cognitive 80) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:545— AppLiquidButtonsKt.AppLiquidTextButton has cognitive complexity 80 (threshold 15). Drivers by points: if/else 39 (69 pts), boolean chains 9, match/switch 1 (2 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.
LiquidSheetKt.LiquidSheetPresentation (cognitive 80) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheet.kt:137— LiquidSheetKt.LiquidSheetPresentation has cognitive complexity 80 (threshold 15). Drivers by points: if/else 64 (72 pts), boolean chains 7, match/switch 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GuideGalleryExpressionSectionKt.GuideGalleryExpressionCardItem (cognitive 73) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryExpressionSection.kt:129— GuideGalleryExpressionSectionKt.GuideGalleryExpressionCardItem has cognitive complexity 73 (threshold 15). Drivers by points: if/else 44 (56 pts), boolean chains 12, match/switch 3 (5 pts) (nesting depth added 14). 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.
GuideFetchSimulateKt.parseSimulateRowsFromBaseData (cognitive 70) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:114— GuideFetchSimulateKt.parseSimulateRowsFromBaseData has cognitive complexity 70 (threshold 15). Drivers by points: if/else 25 (53 pts), boolean chains 11, loops 3, match/switch 2 (3 pts) (nesting depth added 29). 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.
GitHubTrackEditFormContentKt.GitHubTrackEditFormContent (cognitive 69) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFormContent.kt:50— GitHubTrackEditFormContentKt.GitHubTrackEditFormContent has cognitive complexity 69 (threshold 15). Drivers by points: if/else 44 (62 pts), boolean chains 4, match/switch 3 (nesting depth added 18). 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.
AppLiquidButtonsKt.AppLiquidIconButtonContainer (cognitive 67) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:265— AppLiquidButtonsKt.AppLiquidIconButtonContainer has cognitive complexity 67 (threshold 15). Drivers by points: if/else 32 (61 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 30). 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.
AppLiquidSearchFieldKt.AppLiquidInputField (cognitive 67) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:53— AppLiquidSearchFieldKt.AppLiquidInputField has cognitive complexity 67 (threshold 15). Drivers by points: if/else 39 (64 pts), boolean chains 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlassStyleKt.glassStyle (cognitive 67) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:47— GlassStyleKt.glassStyle has cognitive complexity 67 (threshold 15). Drivers by points: if/else 44 (66 pts), match/switch 1 (nesting depth added 22). 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.
GuideGalleryMediaRendererKt.GuideGalleryCardContent (cognitive 64) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryMediaRenderer.kt:53— GuideGalleryMediaRendererKt.GuideGalleryCardContent has cognitive complexity 64 (threshold 15). Drivers by points: if/else 36 (52 pts), boolean chains 10, match/switch 1 (2 pts) (nesting depth added 17). 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.
GuideModel3dPlayerKt.GuideModel3dPlayer (cognitive 62) app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dPlayer.kt:40— GuideModel3dPlayerKt.GuideModel3dPlayer has cognitive complexity 62 (threshold 15). Drivers by points: if/else 32 (47 pts), boolean chains 11, match/switch 1 (2 pts), error handling 1, 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.
GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage (cognitive 59) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryPage.kt:106— GitHubActionsNotificationHistoryPageKt.GitHubActionsNotificationHistoryPage has cognitive complexity 59 (threshold 15). Drivers by points: if/else 27 (43 pts), match/switch 7 (12 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideFetchGiftKt.parseGiftPreferenceRowsFromBaseData (cognitive 59) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGift.kt:86— GuideFetchGiftKt.parseGiftPreferenceRowsFromBaseData has cognitive complexity 59 (threshold 15). Drivers by points: if/else 24 (48 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideGalleryTabContentSectionsKt.renderGuideGalleryStateContent (cognitive 58) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentSections.kt:36— GuideGalleryTabContentSectionsKt.renderGuideGalleryStateContent has cognitive complexity 58 (threshold 15). Drivers by points: if/else 31 (44 pts), boolean chains 14 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideSectionSkillKt.GuideSkillCardItem (cognitive 54) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionSkill.kt:53— GuideSectionSkillKt.GuideSkillCardItem has cognitive complexity 54 (threshold 15). Drivers by points: if/else 32 (45 pts), boolean chains 6, match/switch 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaGuideStudentBgmTabContentKt.BaGuideStudentBgmTabContent (cognitive 52) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.kt:71— BaGuideStudentBgmTabContentKt.BaGuideStudentBgmTabContent has cognitive complexity 52 (threshold 15). Drivers by points: if/else 38 (44 pts), boolean chains 8 (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.
LiquidSurfacesKt.LiquidSurface (cognitive 51) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt:79— LiquidSurfacesKt.LiquidSurface has cognitive complexity 51 (threshold 15). Drivers by points: if/else 33 (39 pts), boolean chains 9, match/switch 3 (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.
AboutPageKt.AboutPage (cognitive 50) app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:70— AboutPageKt.AboutPage has cognitive complexity 50 (threshold 15). Drivers by points: if/else 26 (35 pts), match/switch 5 (13 pts), boolean chains 2 (nesting depth added 17). 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.
GitHubReleaseEvaluationEngine.evaluate (cognitive 50) feature-github-engine/src/main/java/os/kei/feature/github/engine/release/GitHubReleaseEvaluationEngine.kt:65— GitHubReleaseEvaluationEngine.evaluate has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 36, if/else 8, match/switch 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GuideGalleryAudioPlayerStateKt.BindGuideGalleryAudioPlayerEffects (cognitive 49) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryAudioPlayerState.kt:188— GuideGalleryAudioPlayerStateKt.BindGuideGalleryAudioPlayerEffects has cognitive complexity 49 (threshold 15). Drivers by points: if/else 28 (43 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppLiquidCheckboxKt.AppLiquidCheckbox (cognitive 48) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:45— AppLiquidCheckboxKt.AppLiquidCheckbox has cognitive complexity 48 (threshold 15). Drivers by points: if/else 34 (48 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainPagerLayoutKt.MainPagerLayout (cognitive 47) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt:78— MainPagerLayoutKt.MainPagerLayout has cognitive complexity 47 (threshold 15). Drivers by points: if/else 36 (40 pts), boolean chains 5, match/switch 2 (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.
GuideFetchJsonContentTokenizerKt.tokenizeGuideBaseRows (cognitive 47) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentTokenizer.kt:20— GuideFetchJsonContentTokenizerKt.tokenizeGuideBaseRows has cognitive complexity 47 (threshold 15). Drivers by points: if/else 12 (40 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (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.
BaGuideMemoryLobbyTabContentKt.BaGuideMemoryLobbyTabContent (cognitive 46) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:73— BaGuideMemoryLobbyTabContentKt.BaGuideMemoryLobbyTabContent has cognitive complexity 46 (threshold 15). Drivers by points: if/else 28 (35 pts), boolean chains 11 (nesting depth added 7). 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.
GitHubActionsWorkflowSelector.matchWorkflow (cognitive 45) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsWorkflowSelector.kt:136— GitHubActionsWorkflowSelector.matchWorkflow has cognitive complexity 45 (threshold 15). Drivers by points: if/else 28 (34 pts), boolean chains 9, match/switch 2 (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.
HomePageContentDeriverKt.deriveHomePageContentState (cognitive 43) app/src/main/java/os/kei/ui/page/main/home/state/HomePageContentDeriver.kt:18— HomePageContentDeriverKt.deriveHomePageContentState has cognitive complexity 43 (threshold 15). Drivers by points: if/else 32 (34 pts), match/switch 7 (8 pts), boolean chains 1 (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.
AppSwitchKt.LiquidSwitchToggle (cognitive 43) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppSwitch.kt:178— AppSwitchKt.LiquidSwitchToggle has cognitive complexity 43 (threshold 15). Drivers by points: if/else 36 (43 pts) (nesting depth added 7). 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.
BaCalendarPoolPageKt.BaCalendarPoolPage (cognitive 42) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolPage.kt:81— BaCalendarPoolPageKt.BaCalendarPoolPage has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (23 pts), match/switch 9 (12 pts), boolean chains 7 (nesting depth added 4). 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.
viewer.presentationRegion (cognitive 42) app/src/main/assets/ba3d/viewer.js:221— viewer.presentationRegion has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 3 (12 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 17). Most of this is not in the body itself: 12 of the 42 points are its own statements and the rest belongs to one function literal inside it that branches (line 224). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SheetStylesKt.SheetChoiceCard (cognitive 41) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/SheetStyles.kt:386— SheetStylesKt.SheetChoiceCard has cognitive complexity 41 (threshold 15). Drivers by points: if/else 37 (39 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubActionsRunSelector.matchRun (cognitive 40) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRunSelector.kt:103— GitHubActionsRunSelector.matchRun has cognitive complexity 40 (threshold 15). Drivers by points: if/else 24 (30 pts), boolean chains 8, match/switch 2 (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.
HomePageDerivedStateKt.rememberHomePageOverviewCardState (cognitive 37) app/src/main/java/os/kei/ui/page/main/home/state/HomePageDerivedState.kt:246— HomePageDerivedStateKt.rememberHomePageOverviewCardState has cognitive complexity 37 (threshold 15). Drivers by points: if/else 33 (35 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GuideSkillCardHelperKt.parseBaseSkillDrafts (cognitive 37) app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:89— GuideSkillCardHelperKt.parseBaseSkillDrafts has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (33 pts), boolean chains 3, match/switch 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideSectionGalleryKt.GuideGalleryCardItem (cognitive 37) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionGallery.kt:41— GuideSectionGalleryKt.GuideGalleryCardItem has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 12, match/switch 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubAtomReleaseStrategy.parseAtomFeed (cognitive 36) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubAtomReleaseStrategy.kt:377— GitHubAtomReleaseStrategy.parseAtomFeed has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 14, if/else 3 (13 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideFetchVoiceKt.parseVoiceCvByLanguageFromBaseData (cognitive 35) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:262— GuideFetchVoiceKt.parseVoiceCvByLanguageFromBaseData has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (26 pts), loops 3 (5 pts), boolean chains 4 (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.
WebDavSyncClient.request (cognitive 35) feature-webdav/src/main/java/os/kei/feature/webdav/client/WebDavSyncClient.kt:216— WebDavSyncClient.request has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (25 pts), error handling 2 (4 pts), boolean chains 3, loops 2 (3 pts) (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.
LiquidSurfacesKt.AppLiquidFloatingSurface (cognitive 35) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.kt:542— LiquidSurfacesKt.AppLiquidFloatingSurface has cognitive complexity 35 (threshold 15). Drivers by points: if/else 28 (32 pts), boolean chains 2, 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.
BaGuideCatalogV2ListContentKt.BaGuideCatalogV2ListContent (cognitive 34) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:59— BaGuideCatalogV2ListContentKt.BaGuideCatalogV2ListContent has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (26 pts), boolean chains 8 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubActionsArtifactSelector.matchArtifact (cognitive 34) feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt:107— GitHubActionsArtifactSelector.matchArtifact has cognitive complexity 34 (threshold 15). Drivers by points: if/else 21 (23 pts), boolean chains 7, match/switch 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubWidgetRenderer.renderProjects (cognitive 33) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:262— GitHubWidgetRenderer.renderProjects has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 8, match/switch 2 (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.
MiIslandNotificationBuilder.resolvePresentation (cognitive 33) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:539— MiIslandNotificationBuilder.resolvePresentation has cognitive complexity 33 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 9 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubRefreshBatchActions.refreshTrackedBatchInternal (cognitive 32) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubRefreshBatchActions.kt:38— GitHubRefreshBatchActions.refreshTrackedBatchInternal has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 6, error handling 2, match/switch 1 (2 pts) (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.
GitHubTrackedRefreshBatchRunner.run (cognitive 32) feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.kt:175— GitHubTrackedRefreshBatchRunner.run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppFloatingSearchDockKt.AppFloatingSearchDock (cognitive 32) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:89— AppFloatingSearchDockKt.AppFloatingSearchDock has cognitive complexity 32 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 6 (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.
GuideWebMemoryLobbyPlayerKt.GuideWebMemoryLobbyPlayer (cognitive 31) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideWebMemoryLobbyPlayer.kt:52— GuideWebMemoryLobbyPlayerKt.GuideWebMemoryLobbyPlayer has cognitive complexity 31 (threshold 15). Drivers by points: if/else 22 (26 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.
AppDropdownControlsKt.AppDropdownSelector (cognitive 31) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppDropdownControls.kt:118— AppDropdownControlsKt.AppDropdownSelector has cognitive complexity 31 (threshold 15). Drivers by points: if/else 22 (24 pts), boolean chains 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubTrackActions.applyTrackSheet (cognitive 30) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackActions.kt:507— GitHubTrackActions.applyTrackSheet has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (22 pts), match/switch 4, boolean chains 3, error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SettingsCacheSectionKt.SettingsCacheSection (cognitive 30) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsCacheSection.kt:30— SettingsCacheSectionKt.SettingsCacheSection has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 6, match/switch 1 (2 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.
GuideGalleryFullscreenKt.GuideImageFullscreenDialog (cognitive 30) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryFullscreen.kt:72— GuideGalleryFullscreenKt.GuideImageFullscreenDialog has cognitive complexity 30 (threshold 15). Drivers by points: if/else 19, boolean chains 10, match/switch 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.
AppLiquidSearchMaterialKt.appLiquidSearchMaterialColors (cognitive 30) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchMaterial.kt:49— AppLiquidSearchMaterialKt.appLiquidSearchMaterialColors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 24 (30 pts) (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.
FdroidVersionListPageKt.FdroidVersionCard (cognitive 29) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:526— FdroidVersionListPageKt.FdroidVersionCard has cognitive complexity 29 (threshold 15). Drivers by points: if/else 20 (27 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OsGoogleSystemServiceSuggestionSheetKt.OsGoogleSystemServiceSuggestionSheet (cognitive 29) app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceSuggestionSheet.kt:37— OsGoogleSystemServiceSuggestionSheetKt.OsGoogleSystemServiceSuggestionSheet has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 3, match/switch 1 (2 pts) (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.
SettingsBackgroundSectionKt.SettingsBackgroundSection (cognitive 29) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsBackgroundSection.kt:67— SettingsBackgroundSectionKt.SettingsBackgroundSection has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 4, match/switch 3 (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.
BaGuideBgmBottomChromeKt.BaGuideBgmFloatingBottomChrome (cognitive 29) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmBottomChrome.kt:64— BaGuideBgmBottomChromeKt.BaGuideBgmFloatingBottomChrome has cognitive complexity 29 (threshold 15). Drivers by points: if/else 22, match/switch 6, boolean chains 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.
GuideFetchSimulateKt.collectSimulateSupplementIcons (cognitive 29) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:30— GuideFetchSimulateKt.collectSimulateSupplementIcons has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (4 pts), loops 2, boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppMarkdownParserKt.parseAppMarkdownBlocks (cognitive 29) app/src/main/java/os/kei/ui/page/main/widget/markdown/AppMarkdownParser.kt:24— AppMarkdownParserKt.parseAppMarkdownBlocks has cognitive complexity 29 (threshold 15). Drivers by points: if/else 23 (29 pts) (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.
GitHubMainContentSectionKt.GitHubMainContent (cognitive 28) app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:75— GitHubMainContentSectionKt.GitHubMainContent has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21, match/switch 4, boolean chains 3. 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.
MainPagerBottomBarKt.MainPagerBottomBar (cognitive 28) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:60— MainPagerBottomBarKt.MainPagerBottomBar has cognitive complexity 28 (threshold 15). Drivers by points: if/else 23 (25 pts), match/switch 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OsPageMainListKt.OsPageMainList (cognitive 28) app/src/main/java/os/kei/ui/page/main/os/components/OsPageMainList.kt:155— OsPageMainListKt.OsPageMainList has cognitive complexity 28 (threshold 15). Drivers by points: if/else 27, match/switch 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.
BaStudentGuideRepository.loadGuide (cognitive 28) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuideRepository.kt:304— BaStudentGuideRepository.loadGuide has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 8, match/switch 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.
WebDavSyncCardsKt.WebDavSyncBatchActionsCard (cognitive 28) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:316— WebDavSyncCardsKt.WebDavSyncBatchActionsCard has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15, boolean chains 10, match/switch 3. 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.
AppFloatingSearchDockMotionKt.rememberAppFloatingVerticalSearchDockMotion (cognitive 28) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDockMotion.kt:28— AppFloatingSearchDockMotionKt.rememberAppFloatingVerticalSearchDockMotion has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 4, match/switch 3 (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.
LiquidSliderVariantsKt.LiquidTrackSlider (cognitive 28) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:266— LiquidSliderVariantsKt.LiquidTrackSlider has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 6 (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.
GitHubStrategySheetKt.GitHubStrategySheet (cognitive 27) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubStrategySheet.kt:58— GitHubStrategySheetKt.GitHubStrategySheet has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (21 pts), match/switch 4, boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BaGuideBgmAlbumHeroKt.BaGuideBgmAlbumHero (cognitive 27) app/src/main/java/os/kei/ui/page/main/student/catalog/component/bgm/BaGuideBgmAlbumHero.kt:40— BaGuideBgmAlbumHeroKt.BaGuideBgmAlbumHero has cognitive complexity 27 (threshold 15). Drivers by points: if/else 27. 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.
WebDavPayloadValidationKt.validateWebDavPayload (cognitive 27) app/src/main/java/os/kei/ui/page/main/sync/WebDavPayloadValidation.kt:9— WebDavPayloadValidationKt.validateWebDavPayload has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13, match/switch 5 (8 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 5). 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.
BaLiquidSurfacesKt.BaLiquidSurfaceColumn (cognitive 26) app/src/main/java/os/kei/ui/page/main/ba/BaLiquidSurfaces.kt:53— BaLiquidSurfacesKt.BaLiquidSurfaceColumn has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 5 (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.
GitHubReleaseListPageKt.GitHubReleaseCard (cognitive 26) app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:486— GitHubReleaseListPageKt.GitHubReleaseCard has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22 (24 pts), boolean chains 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BaGuideStudentBgmCardsKt.BaGuideStudentBgmCard (cognitive 26) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:153— BaGuideStudentBgmCardsKt.BaGuideStudentBgmCard has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (18 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 3). 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.
VivoAtomicAdapter.plan (cognitive 26) core-notification/src/main/java/os/kei/core/notification/live/oem/vivo/VivoAtomicAdapter.kt:35— VivoAtomicAdapter.plan has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 7 (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.
GitHubActionsArtifactCardKt.GitHubActionsArtifactCard (cognitive 25) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactCard.kt:33— GitHubActionsArtifactCardKt.GitHubActionsArtifactCard has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HomePageDerivedStateKt.rememberHomePageHeroMotionState (cognitive 25) app/src/main/java/os/kei/ui/page/main/home/state/HomePageDerivedState.kt:66— HomePageDerivedStateKt.rememberHomePageHeroMotionState has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 2 (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.
GuideProfileTabContentKt.renderGuideProfileTabContent (cognitive 25) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideProfileTabContent.kt:32— GuideProfileTabContentKt.renderGuideProfileTabContent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppForegroundInfoHandler.cleanupGitHubRefreshRuntimeAndNotification (cognitive 24) app/src/main/java/os/kei/core/background/AppForegroundInfoHandler.kt:286— AppForegroundInfoHandler.cleanupGitHubRefreshRuntimeAndNotification has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, match/switch 1 (3 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.
GitHubActionsErrorLocalizationKt.localizedGitHubPageErrorMessage (cognitive 24) app/src/main/java/os/kei/ui/page/main/github/GitHubActionsErrorLocalization.kt:233— GitHubActionsErrorLocalizationKt.localizedGitHubPageErrorMessage has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 17, if/else 5 (6 pts), match/switch 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BaStudentGuideStore.loadInfoSnapshot (cognitive 24) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStore.kt:111— BaStudentGuideStore.loadInfoSnapshot has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaGuideBgmArtworkHydrationKt.hydrateBaGuideBgmArtwork (cognitive 24) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmArtworkHydration.kt:20— BaGuideBgmArtworkHydrationKt.hydrateBaGuideBgmArtwork has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaGuideBgmMiniPlayerKt.BaGuideBgmMiniPlayer (cognitive 24) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmMiniPlayer.kt:54— BaGuideBgmMiniPlayerKt.BaGuideBgmMiniPlayer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (23 pts), match/switch 1 (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.
GitHubWidgetConfigurationScreenKt.GitHubWidgetConfigurationScreen (cognitive 23) app/src/main/java/os/kei/appwidget/github/GitHubWidgetConfigurationScreen.kt:41— GitHubWidgetConfigurationScreenKt.GitHubWidgetConfigurationScreen has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 10, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubWidgetProjectionKt.projectGitHubWidget (cognitive 23) app/src/main/java/os/kei/appwidget/github/GitHubWidgetProjection.kt:13— GitHubWidgetProjectionKt.projectGitHubWidget has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 9 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubPageKt.GitHubPage (cognitive 23) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPage.kt:54— GitHubPageKt.GitHubPage has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 11. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubAssetPanelActions.loadFdroidApkAssets (cognitive 23) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:192— GitHubAssetPanelActions.loadFdroidApkAssets has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubTrackedItemsListShellKt.GitHubTrackedItemsListShell (cognitive 23) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemsListShell.kt:40— GitHubTrackedItemsListShellKt.GitHubTrackedItemsListShell has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (22 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.
GuideSkillDescriptionRichTextKt.buildSkillDescriptionRichText (cognitive 23) app/src/main/java/os/kei/ui/page/main/student/section/GuideSkillDescriptionRichText.kt:64— GuideSkillDescriptionRichTextKt.buildSkillDescriptionRichText has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, 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.
GitHubApkPackageNameScanRepository.loadScanReleaseApkAssets (cognitive 23) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubApkPackageNameScanRepository.kt:25— GitHubApkPackageNameScanRepository.loadScanReleaseApkAssets has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, loops 1, match/switch 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.
LiquidGlassDropdownItemsKt.LiquidGlassDropdownRowContent (cognitive 23) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:411— LiquidGlassDropdownItemsKt.LiquidGlassDropdownRowContent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 2, match/switch 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.
GitHubActionsErrorLocalizationKt.localizedGitHubActionsErrorMessage (cognitive 22) app/src/main/java/os/kei/ui/page/main/github/GitHubActionsErrorLocalization.kt:10— GitHubActionsErrorLocalizationKt.localizedGitHubActionsErrorMessage has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 19, if/else 2, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BaStudentGuideStoreCodecKt.decodeVoiceEntriesFromArray (cognitive 22) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:144— BaStudentGuideStoreCodecKt.decodeVoiceEntriesFromArray has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideFetchParserCommonKt.extractGuideTabIcons (cognitive 22) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:92— GuideFetchParserCommonKt.extractGuideTabIcons has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, loops 2 (4 pts), match/switch 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.
GuideMediaSaveRequestBuilderKt.inferGuideMediaExtFromLocalFile (cognitive 22) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaSaveRequestBuilder.kt:102— GuideMediaSaveRequestBuilderKt.inferGuideMediaExtFromLocalFile has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, if/else 5 (6 pts), match/switch 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GuideGalleryVideoSectionKt.GuideInlineVideoPlayer (cognitive 22) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryVideoSection.kt:230— GuideGalleryVideoSectionKt.GuideInlineVideoPlayer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3, 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.
SegmentedDownloadClient.runWorker (cognitive 22) core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:277— SegmentedDownloadClient.runWorker has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1, loops 1 (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.
GitHubTrackStoreSerializersKt.parseTrackedItem (cognitive 22) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStoreSerializers.kt:33— GitHubTrackStoreSerializersKt.parseTrackedItem has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, match/switch 6, boolean chains 3. 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.
McpKeepAliveService.onStartCommand (cognitive 22) feature-mcp/src/main/java/os/kei/mcp/service/McpKeepAliveService.kt:48— McpKeepAliveService.onStartCommand has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, match/switch 1 (nesting depth added 6). 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.
SheetGlassNode.draw (cognitive 22) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/SheetGlassBackdrop.kt:281— SheetGlassNode.draw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 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.
GitHubWidgetRenderer.renderMetrics (cognitive 21) app/src/main/java/os/kei/appwidget/github/GitHubWidgetRenderer.kt:334— GitHubWidgetRenderer.renderMetrics 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.
BaCraftSlotEditSheetKt.BaCraftSlotEditSheet (cognitive 21) app/src/main/java/os/kei/ui/page/main/ba/BaCraftSlotEditSheet.kt:68— BaCraftSlotEditSheetKt.BaCraftSlotEditSheet has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubAssetPanelActions.loadApkAssets (cognitive 21) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubAssetPanelActions.kt:30— GitHubAssetPanelActions.loadApkAssets has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubConfigActions.applyLookupConfig (cognitive 21) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubConfigActions.kt:237— GitHubConfigActions.applyLookupConfig has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, match/switch 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.
OsGoogleSystemServiceSuggestionResolverKt.rememberOsGoogleSystemServiceSuggestionUiState (cognitive 21) app/src/main/java/os/kei/ui/page/main/os/components/OsGoogleSystemServiceSuggestionResolver.kt:38— OsGoogleSystemServiceSuggestionResolverKt.rememberOsGoogleSystemServiceSuggestionUiState has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 9, match/switch 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SettingsComponentEffectsSectionKt.SettingsComponentEffectsSection (cognitive 21) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsComponentEffectsSection.kt:20— SettingsComponentEffectsSectionKt.SettingsComponentEffectsSection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4 (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.
GuideGalleryTabContentStateKt.resolveGuideGalleryTabState (cognitive 21) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideGalleryTabContentState.kt:56— GuideGalleryTabContentStateKt.resolveGuideGalleryTabState has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 6, match/switch 4. 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.
GuideSimulateDataAssemblerKt.expandSimulateRows (cognitive 21) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateDataAssembler.kt:100— GuideSimulateDataAssemblerKt.expandSimulateRows has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, 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.
WebDavSyncCardsKt.WebDavSyncItemRow (cognitive 21) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:489— WebDavSyncCardsKt.WebDavSyncItemRow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18, match/switch 2, boolean chains 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.
MiIslandNotificationBuilder.build (cognitive 21) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:127— MiIslandNotificationBuilder.build has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (8 pts), match/switch 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubBackgroundRefreshService.runDueRefresh (cognitive 21) feature-github/src/main/java/os/kei/feature/github/domain/GitHubBackgroundRefreshService.kt:53— GitHubBackgroundRefreshService.runDueRefresh has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubReleasePackageScope.resolve (cognitive 21) feature-github/src/main/java/os/kei/feature/github/domain/GitHubReleasePackageScope.kt:26— GitHubReleasePackageScope.resolve has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 6, match/switch 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WebDavSyncSession.execute (cognitive 21) feature-webdav/src/main/java/os/kei/feature/webdav/sync/WebDavSyncSession.kt:44— WebDavSyncSession.execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (5 pts), boolean chains 2, error handling 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppFloatingSearchDockKt.AppFloatingVerticalSearchActionDock (cognitive 21) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.kt:226— AppFloatingSearchDockKt.AppFloatingVerticalSearchActionDock has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, boolean chains 5, match/switch 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.
LiquidGlassActionMenuKt.LiquidGlassActionMenu (cognitive 21) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:153— LiquidGlassActionMenuKt.LiquidGlassActionMenu has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14, boolean chains 6, match/switch 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.
model-skin-bounds.createSkinBounds::build (cognitive 21) app/src/main/assets/ba3d/model-skin-bounds.js:9— model-skin-bounds.createSkinBounds::build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, loops 2 (3 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.
BaCalendarPoolRepository.syncCalendar (cognitive 20) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:116— BaCalendarPoolRepository.syncCalendar has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), error handling 2, boolean chains 1 (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. This shape REPEATS in the file: one other method here (BaCalendarPoolRepository.syncPool) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BaCalendarPoolRepository.syncPool (cognitive 20) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:296— BaCalendarPoolRepository.syncPool has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), error handling 2, boolean chains 1 (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. This shape REPEATS in the file: one other method here (BaCalendarPoolRepository.syncCalendar) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GitHubTrackEditorPersistenceKt.persistTrackEditorSave (cognitive 20) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubTrackEditorPersistence.kt:23— GitHubTrackEditorPersistenceKt.persistTrackEditorSave has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 6 (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.
GitHubTrackAppPickerContentKt.GitHubTrackAppPickerContent (cognitive 20) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackAppPickerContent.kt:271— GitHubTrackAppPickerContentKt.GitHubTrackAppPickerContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15, boolean chains 5. 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.
MainScreenKt.MainScreen (cognitive 20) app/src/main/java/os/kei/ui/page/main/host/main/MainScreen.kt:31— MainScreenKt.MainScreen has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17, match/switch 2, boolean chains 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.
McpPageOverviewStateKt.rememberMcpPageOverviewState (cognitive 20) app/src/main/java/os/kei/ui/page/main/mcp/state/McpPageOverviewState.kt:33— McpPageOverviewStateKt.rememberMcpPageOverviewState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17, boolean chains 2, match/switch 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.
OsShortcutCardActionsKt.putShortcutIntentExtra (cognitive 20) app/src/main/java/os/kei/ui/page/main/os/shortcut/OsShortcutCardActions.kt:146— OsShortcutCardActionsKt.putShortcutIntentExtra has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 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.
SettingsPageKt.SettingsPage (cognitive 20) app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:69— SettingsPageKt.SettingsPage has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BaGuideCatalogFilterModelsKt.parseFilterAttributes (cognitive 20) app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:264— BaGuideCatalogFilterModelsKt.parseFilterAttributes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaGuideBgmPlaybackCoordinator.updateNativeMediaNotificationEnabled (cognitive 20) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideBgmPlaybackCoordinator.kt:245— BaGuideBgmPlaybackCoordinator.updateNativeMediaNotificationEnabled has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MiIslandNotificationBuilder.buildFocusExtras (cognitive 20) core-notification/src/main/java/os/kei/core/notification/live/builder/MiIslandNotificationBuilder.kt:256— MiIslandNotificationBuilder.buildFocusExtras has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 5, match/switch 3. 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.
GitHubReleaseNotesHtmlMarkdownConverter.htmlAttribute (cognitive 20) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.kt:190— GitHubReleaseNotesHtmlMarkdownConverter.htmlAttribute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubRepositoryHealthEvaluator.evaluate (cognitive 20) feature-github-engine/src/main/java/os/kei/feature/github/domain/GitHubRepositoryHealthEvaluator.kt:10— GitHubRepositoryHealthEvaluator.evaluate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 7, match/switch 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.
GitHubRepositoryProfileCacheJsonKt.inferCapabilities (cognitive 20) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubRepositoryProfileCacheJson.kt:481— GitHubRepositoryProfileCacheJsonKt.inferCapabilities has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 9. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AppLiquidSearchFieldKt.AppLiquidSearchSurface (cognitive 20) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:414— AppLiquidSearchFieldKt.AppLiquidSearchSurface has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiquidGlassActionMenuKt.actionMenuContentColor (cognitive 20) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassActionMenu.kt:708— LiquidGlassActionMenuKt.actionMenuContentColor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 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.
frame-presentation.keiosCreateFramePresenter.present (cognitive 20) app/src/main/assets/ba3d/frame-presentation.js:28— frame-presentation.keiosCreateFramePresenter.present has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, ternaries 6, boolean chains 5. Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. 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.
LauncherIconSwitcher.apply (cognitive 19) app/src/main/java/os/kei/core/icon/LauncherIconController.kt:59— LauncherIconSwitcher.apply has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 4 (7 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.
GitHubRefreshNotificationHelper.resolveScopeText (cognitive 19) app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:521— GitHubRefreshNotificationHelper.resolveScopeText has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 1 (nesting depth added 6). 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.
BaRuntimeTickerCoordinator.run (cognitive 19) app/src/main/java/os/kei/ui/page/main/ba/BaRuntimeTickerCoordinator.kt:22— BaRuntimeTickerCoordinator.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 5, 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.
BaSlotCardsKt.BaCraftSlotCard (cognitive 19) app/src/main/java/os/kei/ui/page/main/ba/card/BaSlotCards.kt:211— BaSlotCardsKt.BaCraftSlotCard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (16 pts), match/switch 2, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubOverviewSectionKt.GitHubOverviewCard (cognitive 19) app/src/main/java/os/kei/ui/page/main/github/section/GitHubOverviewSection.kt:69— GitHubOverviewSectionKt.GitHubOverviewCard has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitHubTrackedItemHeaderActionsKt.gitHubTrackedItemHeaderActionState (cognitive 19) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemHeaderActions.kt:138— GitHubTrackedItemHeaderActionsKt.gitHubTrackedItemHeaderActionState has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 5, match/switch 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GitHubTrackedItemMoreMenuKt.GitHubTrackedItemMoreActions (cognitive 19) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemMoreMenu.kt:63— GitHubTrackedItemMoreMenuKt.GitHubTrackedItemMoreActions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 5, match/switch 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.
SettingsSearchCardRendererKt.SettingsSearchCardContent (cognitive 19) app/src/main/java/os/kei/ui/page/main/settings/page/SettingsSearchCardRenderer.kt:52— SettingsSearchCardRendererKt.SettingsSearchCardContent has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 6 (nesting depth added 6). 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.
BaGuideCatalogTransferActionsKt.rememberBaGuideCatalogJsonExportAction (cognitive 19) app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogTransferActions.kt:39— BaGuideCatalogTransferActionsKt.rememberBaGuideCatalogJsonExportAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, error handling 2, boolean chains 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.
BaGuideFavoriteBgmMusicContentKt.BaGuideFavoriteBgmMusicContent (cognitive 19) app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideFavoriteBgmMusicContent.kt:53— BaGuideFavoriteBgmMusicContentKt.BaGuideFavoriteBgmMusicContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16 (17 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.
BaStudentGuidePageActionsKt.rememberBaStudentGuidePageActions (cognitive 19) app/src/main/java/os/kei/ui/page/main/student/page/state/BaStudentGuidePageActions.kt:27— BaStudentGuidePageActionsKt.rememberBaStudentGuidePageActions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2 (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.
GuideMediaCopySupportKt.copyGuideMediaFromSourceToZipEntry (cognitive 19) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:156— GuideMediaCopySupportKt.copyGuideMediaFromSourceToZipEntry has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, error handling 2, 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.
GuideGalleryVideoSectionKt.GuideGalleryVideoGroupCardItem (cognitive 19) app/src/main/java/os/kei/ui/page/main/student/section/gallery/GuideGalleryVideoSection.kt:53— GuideGalleryVideoSectionKt.GuideGalleryVideoGroupCardItem has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17 (18 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.
TextCopySupportKt.copyModeAwareRow (cognitive 19) app/src/main/java/os/kei/ui/page/main/widget/support/TextCopySupport.kt:70— TextCopySupportKt.copyModeAwareRow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaCalendarPoolCardsKt.BaPoolEntryPanel (cognitive 18) app/src/main/java/os/kei/ui/page/main/ba/card/BaCalendarPoolCards.kt:195— BaCalendarPoolCardsKt.BaPoolEntryPanel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 3, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitHubStarImportModelsKt.buildStarImportCandidateListUiState (cognitive 18) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportModels.kt:146— GitHubStarImportModelsKt.buildStarImportCandidateListUiState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, 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.
GitHubTrackedItemAssetPanelKt.GitHubTrackedItemAssetPanel (cognitive 18) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanel.kt:36— GitHubTrackedItemAssetPanelKt.GitHubTrackedItemAssetPanel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, match/switch 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.
OsOverviewMetricsKt.buildOsOverviewUiState (cognitive 18) app/src/main/java/os/kei/ui/page/main/os/OsOverviewMetrics.kt:90— OsOverviewMetricsKt.buildOsOverviewUiState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, boolean chains 6, match/switch 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.
OsShellRunnerPageActionsKt.rememberOsShellRunnerPageActionsInternal (cognitive 18) app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerPageActions.kt:80— OsShellRunnerPageActionsKt.rememberOsShellRunnerPageActionsInternal has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 3). 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.
SettingsLogSectionKt.SettingsLogSection (cognitive 18) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsLogSection.kt:31— SettingsLogSectionKt.SettingsLogSection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5 (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.
SettingsVisualSectionKt.SettingsVisualSection (cognitive 18) app/src/main/java/os/kei/ui/page/main/settings/section/SettingsVisualSection.kt:29— SettingsVisualSectionKt.SettingsVisualSection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, match/switch 2 (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.
GuideModel3dScreenKt.GuideModel3dScreen (cognitive 18) app/src/main/java/os/kei/ui/page/main/student/model3d/GuideModel3dScreen.kt:30— GuideModel3dScreenKt.GuideModel3dScreen has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 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.
GuideMediaCopySupportKt.copyGuideMediaFromSourceToOutput (cognitive 18) app/src/main/java/os/kei/ui/page/main/student/page/support/GuideMediaCopySupport.kt:44— GuideMediaCopySupportKt.copyGuideMediaFromSourceToOutput has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, error handling 2, 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.
GuideProfileUiKt.GuideProfileInfoItem (cognitive 18) app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileUi.kt:83— GuideProfileUiKt.GuideProfileInfoItem has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppInfoRowsKt.AppInfoRow (cognitive 18) app/src/main/java/os/kei/ui/page/main/widget/core/AppInfoRows.kt:37— AppInfoRowsKt.AppInfoRow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LiveNotificationPayload.content (cognitive 18) core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:133— LiveNotificationPayload.content has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (LiveNotificationPayload.expandedContent) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
LiveNotificationPayload.expandedContent (cognitive 18) core-notification/src/main/java/os/kei/core/notification/live/LiveNotificationPayload.kt:222— LiveNotificationPayload.expandedContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (LiveNotificationPayload.content) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
WebDavSyncSession.reconcile (cognitive 18) feature-webdav/src/main/java/os/kei/feature/webdav/sync/WebDavSyncSession.kt:156— WebDavSyncSession.reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, match/switch 1 (nesting depth added 8). 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.
LiquidInfoBlockKt.LiquidInfoBlockContent (cognitive 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidInfoBlock.kt:150— LiquidInfoBlockKt.LiquidInfoBlockContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (18 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.
SheetStylesKt.SheetExpandableCard (cognitive 18) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/SheetStyles.kt:612— SheetStylesKt.SheetExpandableCard has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaAccountManagementSheetKt.BaAccountEditorCard (cognitive 17) app/src/main/java/os/kei/ui/page/main/ba/BaAccountManagementSheet.kt:256— BaAccountManagementSheetKt.BaAccountEditorCard has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 2 (4 pts), boolean chains 2 (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.
BaCardCommonKt.BaCardHeader (cognitive 17) app/src/main/java/os/kei/ui/page/main/ba/card/BaCardCommon.kt:52— BaCardCommonKt.BaCardHeader 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.
BaCalendarPoolMappingKt.findImageLinkRecursively (cognitive 17) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:48— BaCalendarPoolMappingKt.findImageLinkRecursively has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitHubRefreshHistoryCardsKt.rememberSlowRefreshDiagnosticPillLabels (cognitive 17) app/src/main/java/os/kei/ui/page/main/github/history/GitHubRefreshHistoryCards.kt:642— GitHubRefreshHistoryCardsKt.rememberSlowRefreshDiagnosticPillLabels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GitHubPageContentStateDeriver.build (cognitive 17) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageContentStateDeriver.kt:46— GitHubPageContentStateDeriver.build has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 7 (12 pts), boolean chains 5 (nesting depth added 5). 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.
GitHubPageEffectsKt.BindGitHubPageLifecycleCoordinator (cognitive 17) app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageEffects.kt:51— GitHubPageEffectsKt.BindGitHubPageLifecycleCoordinator has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16 (17 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaGuideImageCache.loadBitmap (cognitive 17) REDACTED:123— BaGuideImageCache.loadBitmap has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 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.
GuideFetchParserCommonKt.firstImageFromAny (cognitive 17) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:13— GuideFetchParserCommonKt.firstImageFromAny has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GuideFetchParserCommonKt.extractEditorTextLines (cognitive 17) app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchParserCommon.kt:167— GuideFetchParserCommonKt.extractEditorTextLines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1 (2 pts), match/switch 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.
GuideSectionCopyMetaKt.GuideProfileMetaLine (cognitive 17) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionCopyMeta.kt:152— GuideSectionCopyMetaKt.GuideProfileMetaLine has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), match/switch 2, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GuideArchiveTabContentKt.renderGuideArchiveTabContent (cognitive 17) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideArchiveTabContent.kt:30— GuideArchiveTabContentKt.renderGuideArchiveTabContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (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.
GuideVoiceTabContentKt.renderGuideVoiceTabContent (cognitive 17) app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideVoiceTabContent.kt:42— GuideVoiceTabContentKt.renderGuideVoiceTabContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3 (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.
SegmentedDownloadClient.downloadSingleStream (cognitive 17) core-download/src/main/java/os/kei/core/download/segmented/SegmentedDownloadClient.kt:605— SegmentedDownloadClient.downloadSingleStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VivoAtomicDispatcher.execute (cognitive 17) core-notification/src/main/java/os/kei/core/notification/live/oem/vivo/VivoAtomicDispatcher.kt:58— VivoAtomicDispatcher.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (4 pts), boolean chains 1, match/switch 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.
GitHubActionsRepository.fetchWorkflowArtifactSnapshotOnCurrentDispatcher (cognitive 17) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsRepository.kt:354— GitHubActionsRepository.fetchWorkflowArtifactSnapshotOnCurrentDispatcher has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, match/switch 1 (2 pts), error handling 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.
GitHubShareIntentParser.parseSharedReleaseUrl (cognitive 17) feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareIntentParser.kt:62— GitHubShareIntentParser.parseSharedReleaseUrl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
LiquidGlassBottomBarKt.LiquidGlassBottomBarItem (cognitive 17) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/chrome/LiquidGlassBottomBar.kt:117— LiquidGlassBottomBarKt.LiquidGlassBottomBarItem has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 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.
AppCardHeadersKt.AppCardHeader (cognitive 17) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppCardHeaders.kt:45— AppCardHeadersKt.AppCardHeader has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 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.
LiquidGlassDropdownItemsKt.liquidGlassDropdownItemColors (cognitive 17) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:288— LiquidGlassDropdownItemsKt.liquidGlassDropdownItemColors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BaDailyDoneShortcutSectionKt.BaDailyDoneShortcutSection (cognitive 16) app/src/main/java/os/kei/ui/page/main/ba/BaDailyDoneShortcutSection.kt:49— BaDailyDoneShortcutSectionKt.BaDailyDoneShortcutSection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), 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.
BaPageEffectsKt.BaPageCommonEffects (cognitive 16) app/src/main/java/os/kei/ui/page/main/ba/BaPageEffects.kt:166— BaPageEffectsKt.BaPageCommonEffects has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaSlotCardsKt.BaCooldownSlotCard (cognitive 16) app/src/main/java/os/kei/ui/page/main/ba/card/BaSlotCards.kt:71— BaSlotCardsKt.BaCooldownSlotCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 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.
GitHubStarImportControlsKt.StarImportListControlCard (cognitive 16) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportControls.kt:47— GitHubStarImportControlsKt.StarImportListControlCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, boolean chains 3. 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.
GitHubActionsArtifactActions.downloadActionsArtifact (cognitive 16) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsArtifactActions.kt:32— GitHubActionsArtifactActions.downloadActionsArtifact has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, error handling 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.
GitHubBackgroundRefreshCoordinator.refreshItemsInBackground (cognitive 16) app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubBackgroundRefreshCoordinator.kt:110— GitHubBackgroundRefreshCoordinator.refreshItemsInBackground has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, error handling 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.
GitHubTrackedItemAssetPanelAssetRowKt.GitHubTrackedItemAssetRow (cognitive 16) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemAssetPanelAssetRow.kt:41— GitHubTrackedItemAssetPanelAssetRowKt.GitHubTrackedItemAssetRow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
McpSkillMarkdownParserKt.buildSkillSections (cognitive 16) app/src/main/java/os/kei/ui/page/main/mcp/skill/support/McpSkillMarkdownParser.kt:11— McpSkillMarkdownParserKt.buildSkillSections has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OsTopInfoDataKt.topInfoTopicOf (cognitive 16) app/src/main/java/os/kei/ui/page/main/os/OsTopInfoData.kt:44— OsTopInfoDataKt.topInfoTopicOf has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 14, if/else 1, match/switch 1. 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.
BaGuideSpineHttpCache.open (cognitive 16) app/src/main/java/os/kei/ui/page/main/student/BaGuideSpineHttpCache.kt:82— BaGuideSpineHttpCache.open has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 2, error handling 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.
BaStudentGuideStoreCodecKt.decodeGuideRowsFromArray (cognitive 16) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideStoreCodec.kt:28— BaStudentGuideStoreCodecKt.decodeGuideRowsFromArray has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 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.
GuideFetchWebMemoryLobbyKt.extractWebMemoryLobbies (cognitive 16) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchWebMemoryLobby.kt:11— GuideFetchWebMemoryLobbyKt.extractWebMemoryLobbies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, match/switch 1 (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.
GuideProfileSameNameParserKt.extractSameNameGuideLink (cognitive 16) app/src/main/java/os/kei/ui/page/main/student/tabcontent/profile/GuideProfileSameNameParser.kt:44— GuideProfileSameNameParserKt.extractSameNameGuideLink has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, loops 1 (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.
WebDavSyncCardsKt.WebDavSyncAutoSyncCard (cognitive 16) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:158— WebDavSyncCardsKt.WebDavSyncAutoSyncCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (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.
AppTopBarKt.AppTopBarSection (cognitive 16) app/src/main/java/os/kei/ui/page/main/widget/chrome/AppTopBar.kt:24— AppTopBarKt.AppTopBarSection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1 (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.
AppOverviewCardsKt.AppOverviewInlineMetricTile (cognitive 16) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:221— AppOverviewCardsKt.AppOverviewInlineMetricTile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. 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.
AppOverviewPillBatchKt.AppOverviewBatchedLiquidPillFlow (cognitive 16) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.kt:325— AppOverviewPillBatchKt.AppOverviewBatchedLiquidPillFlow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, boolean chains 3. 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.
BaselineProfileActionsKt.exerciseBaCatalogAndReturn (cognitive 16) baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:13— BaselineProfileActionsKt.exerciseBaCatalogAndReturn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (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.
BaselineProfileActionsKt.waitForStableTagBounds (cognitive 16) baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:467— BaselineProfileActionsKt.waitForStableTagBounds has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (2 pts), boolean chains 1, 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.
VersioningEngine.similarityScore (cognitive 16) core-versioning/src/main/java/os/kei/core/versioning/VersioningEngine.kt:693— VersioningEngine.similarityScore has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
JsonScanner.readStringBody (cognitive 16) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:439— JsonScanner.readStringBody has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (6 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.
GitHubRepositoryDiscoveryService.withAppSearchScore (cognitive 16) feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:301— GitHubRepositoryDiscoveryService.withAppSearchScore has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), match/switch 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WebDavSyncSession.restore (cognitive 16) feature-webdav/src/main/java/os/kei/feature/webdav/sync/WebDavSyncSession.kt:116— WebDavSyncSession.restore has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppLiquidButtonsKt.glassContainerOverlayAlpha (cognitive 16) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:921— AppLiquidButtonsKt.glassContainerOverlayAlpha has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Near-duplicate member pair (142 shared lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:282— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:282-542 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:578-899 — These two members are variants of one another: 142 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.
Near-duplicate member pair (60 shared lines) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:141— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:141-370 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:135-361 — These two members are variants of one another: 60 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 (20 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (20 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactSection.kt:54— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsArtifactSection.kt:54-143 | app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:43-98 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:149-365 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackSheets.kt:79-235 | app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt:65-97 | app/src/main/java/os/kei/ui/page/main/os/components/OsPageOverlaySheets.kt:107-218 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:50-171 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:96-178 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:51-209 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:127-384 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmNowPlayingMiniPlayer.kt:35-85 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogBottomChromeRoute.kt:38-60 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerContent.kt:68-140 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:362-406 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt:61-83 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:604-636 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:71-116 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:137-167 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:189-220 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:88-278 — These 20 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 20 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 20 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:88— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:88-253 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:33-112 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:117-326 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:84-260 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:262-401 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentTokenizer.kt:23-102 — These 6 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 6 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 6 times.
D4 · Code Duplication· Edited copy of a member (172 corresponding lines) · ×1
Edited copy of a member (172 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:123— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:123-294 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolRepository.kt:303-485 — These two members are one piece of code written twice and then edited apart: 172 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 (81 corresponding lines) · ×1
Edited copy of a member (81 corresponding lines) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:174— feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:174-264 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingToolsHelpers.kt:270-350 — These two members are one piece of code written twice and then edited apart: 81 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 (94 corresponding lines) · ×1
Edited copy of a member (94 corresponding lines) app/src/main/java/os/kei/ui/page/main/back/BackNavigationRuntime.kt:238— app/src/main/java/os/kei/ui/page/main/back/BackNavigationRuntime.kt:238-333 | app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBackGesture.kt:62-155 — These two members are one piece of code written twice and then edited apart: 94 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 (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:210— feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:210-257 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:303-351 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (86 corresponding lines) · ×1
Edited copy of a member (86 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:30— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:30-115 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolSyncNotifier.kt:139-224 — These two members are one piece of code written twice and then edited apart: 86 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 (90 corresponding lines) · ×1
Edited copy of a member (90 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemVersionSections.kt:136— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemVersionSections.kt:136-225 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTrackedItemVersionSections.kt:235-325 — These two members are one piece of code written twice and then edited apart: 90 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:100— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:100-168 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideSidebar.kt:80-145 — These two members are one piece of code written twice and then edited apart: 66 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 (67 corresponding lines) · ×1
Edited copy of a member (67 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:130— app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:130-196 | app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolMapping.kt:201-267 — These two members are one piece of code written twice and then edited apart: 67 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 (70 corresponding lines) · ×1
Edited copy of a member (70 corresponding lines) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:176— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:176-246 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideSidebar.kt:153-222 — These two members are one piece of code written twice and then edited apart: 70 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) core-system/src/main/java/os/kei/core/system/AppCommandExecutor.kt:66— core-system/src/main/java/os/kei/core/system/AppCommandExecutor.kt:66-130 | core-system/src/main/java/os/kei/core/system/AppCommandExecutor.kt:151-216 — These two members are one piece of code written twice and then edited apart: 65 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 (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolListSections.kt:65— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolListSections.kt:65-151 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolListSections.kt:166-253 — These two members are one piece of code written twice and then edited apart: 87 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryScanCandidateRows.kt:50— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubRepositoryScanCandidateRows.kt:50-110 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditFdroidDiscoverySection.kt:410-471 — These two members are one piece of code written twice and then edited apart: 61 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 (58 corresponding lines) · ×1
Edited copy of a member (58 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:126— app/src/main/java/os/kei/ui/page/main/ba/card/BaApCard.kt:126-183 | app/src/main/java/os/kei/ui/page/main/ba/card/BaCafeCard.kt:160-233 — These two members are one piece of code written twice and then edited apart: 58 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 (59 corresponding lines) · ×1
Edited copy of a member (59 corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:60— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:60-124 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidToastSurface.kt:51-109 — These two members are one piece of code written twice and then edited apart: 59 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchMediaImageExtractors.kt:21— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchMediaImageExtractors.kt:21-57 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchMediaVideoExtractors.kt:7-41 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:28— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:28-87 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:93-143 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:77— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:77-126 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:76-124 — These two members are one piece of code written twice and then edited apart: 49 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:306— feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:306-350 | feature-github-engine/src/main/java/os/kei/feature/github/data/apk/RemoteZipEntryReader.kt:357-395 — 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 (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:428— app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt:428-460 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubTrackStore.kt:828-860 — These two members are one piece of code written twice and then edited apart: 33 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, 36+ corresponding lines) · ×1
Edited copies of one member (3 members, 36+ corresponding lines) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:104— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:104-139 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:155-197 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSliderVariants.kt:216-263 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 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, 39+ corresponding lines) · ×1
Edited copies of one member (3 members, 39+ corresponding lines) app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:295— app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:295-335 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:341-379 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncViewModel.kt:381-422 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 39 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) app/src/main/java/os/kei/ui/page/main/about/section/AboutRuntimeCardsSection.kt:128— app/src/main/java/os/kei/ui/page/main/about/section/AboutRuntimeCardsSection.kt:128-163 | app/src/main/java/os/kei/ui/page/main/about/section/AboutRuntimeCardsSection.kt:174-209 — 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 copies of one member (4 members, 32+ corresponding lines) · ×1
Edited copies of one member (4 members, 32+ corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolNotificationDispatcher.kt:46— app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolNotificationDispatcher.kt:46-80 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolNotificationDispatcher.kt:92-123 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolNotificationDispatcher.kt:135-169 | app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolNotificationDispatcher.kt:181-212 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 32 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, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) REDACTED:86— REDACTED:86-111 | REDACTED:121-147 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubActionsRecommendedRunStore.kt:73-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 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 (5 members, 41+ corresponding lines) · ×1
Edited copies of one member (5 members, 41+ corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:24— app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:24-66 | app/src/main/java/os/kei/ui/page/main/ba/BaApNotificationDispatcher.kt:136-177 | app/src/main/java/os/kei/ui/page/main/ba/BaArenaRefreshNotificationDispatcher.kt:23-64 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeApNotificationDispatcher.kt:24-65 | app/src/main/java/os/kei/ui/page/main/ba/BaCafeVisitNotificationDispatcher.kt:24-64 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 41 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) app/src/main/java/os/kei/ui/page/main/os/components/OsKeyValueSectionCards.kt:69— app/src/main/java/os/kei/ui/page/main/os/components/OsKeyValueSectionCards.kt:69-109 | app/src/main/java/os/kei/ui/page/main/os/components/OsTopInfoSectionCards.kt:179-218 — These two members are one piece of code written twice and then edited apart: 40 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, 35+ corresponding lines) · ×1
Edited copies of one member (4 members, 35+ corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:257— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:257-291 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:298-332 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:367-402 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubDeepRepositoryProfileSource.kt:409-444 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:163— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:163-188 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackDialogs.kt:276-302 | app/src/main/java/os/kei/ui/page/main/os/components/OsImportPreviewDialog.kt:216-240 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 27+ corresponding lines) · ×1
Edited copies of one member (4 members, 27+ corresponding lines) app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:149— app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:149-178 | app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:190-216 | app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:229-255 | app/src/main/java/os/kei/feature/github/notification/GitHubRefreshNotificationHelper.kt:268-294 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 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 (4 members, 21+ corresponding lines) · ×1
Edited copies of one member (4 members, 21+ corresponding lines) app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:231— app/src/main/java/os/kei/ui/page/main/github/importer/GitHubStarImportConfirmDialog.kt:231-251 | app/src/main/java/os/kei/ui/page/main/mcp/dialog/McpConfirmDialogs.kt:61-82 | app/src/main/java/os/kei/ui/page/main/os/components/OsDeleteConfirmDialogs.kt:44-65 | app/src/main/java/os/kei/ui/page/main/os/shell/page/OsShellRunnerSheets.kt:229-249 — 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 (7 members, 16+ corresponding lines) · ×1
Edited copies of one member (7 members, 16+ corresponding lines) app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:84— app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:84-99 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:108-123 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:132-147 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:156-171 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:180-195 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:204-219 | app/src/main/java/os/kei/ui/page/main/mcp/section/McpToolSections.kt:228-243 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:34— app/src/main/java/os/kei/ui/page/main/about/page/AboutBottomChrome.kt:34-59 | app/src/main/java/os/kei/ui/page/main/settings/page/SettingsBottomChrome.kt:34-56 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncBottomChrome.kt:25-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportRouter.kt:101— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportRouter.kt:101-114 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportRouter.kt:116-125 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportRouter.kt:127-136 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportRouter.kt:138-147 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPermissionKeepAliveSupport.kt:603— app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPermissionKeepAliveSupport.kt:603-621 | app/src/main/java/os/kei/ui/page/main/settings/support/SettingsPermissionKeepAliveSupport.kt:623-638 | core-system/src/main/java/os/kei/core/system/HyperOsSettingsIntents.kt:24-42 | core-system/src/main/java/os/kei/core/system/HyperOsSettingsIntents.kt:44-63 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:209— app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:209-228 | app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:234-247 | app/src/main/java/os/kei/ui/page/main/os/shell/OsShellRunnerRepository.kt:427-443 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:116— feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:116-127 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:143-154 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:170-181 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:195-206 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:160— app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:160-176 | app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:183-203 | app/src/main/java/os/kei/ui/page/main/os/OsPageCardCoordinator.kt:208-225 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:272— app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:272-284 | app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:292-304 | app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:312-324 | app/src/main/java/os/kei/ui/page/main/ba/BaReminderCoordinator.kt:332-344 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:140— app/src/main/java/os/kei/feature/ba/data/remote/GameKeeBaContentDetail.kt:140-149 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFetch.kt:668-679 | app/src/main/java/os/kei/ui/page/main/student/catalog/BaGuideCatalogFilterModels.kt:335-348 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:625— baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:625-633 | baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:635-643 | baselineprofile/src/main/java/os/kei/baselineprofile/BaselineProfileActions.kt:645-653 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:107— app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:107-123 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:136-153 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:168-186 | app/src/main/java/os/kei/feature/github/notification/GitHubShareImportNotificationHelper.kt:201-220 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 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, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) app/src/main/java/os/kei/ui/page/main/github/page/GitHubTrackedExpansionStateController.kt:54— app/src/main/java/os/kei/ui/page/main/github/page/GitHubTrackedExpansionStateController.kt:54-65 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubTrackedExpansionStateController.kt:70-81 | app/src/main/java/os/kei/ui/page/main/github/page/GitHubTrackedExpansionStateController.kt:86-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 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 (5 members, 8+ corresponding lines) · ×1
Edited copies of one member (5 members, 8+ corresponding lines) app/src/main/java/os/kei/core/export/ExportJobResult.kt:44— app/src/main/java/os/kei/core/export/ExportJobResult.kt:44-53 | app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:128-135 | app/src/main/java/os/kei/feature/ba/data/remote/GameKeeNetworkClient.kt:254-261 | core-log/src/main/java/os/kei/core/log/AppLogger.kt:193-201 | feature-keepalive/src/main/java/os/kei/feature/keepalive/accessibility/AccessibilityGuardHistoryStore.kt:392-400 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:814— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:814-821 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.kt:277-285 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkHtmlParser.kt:218-226 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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.
Duplicated block (59 lines × 2) app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:399— app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:399-457 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:470-528 — 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/os/kei/ui/page/main/github/section/GitHubMainContentSection.kt:399` 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 (57 lines × 2) app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:227— app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:227-283 | app/src/main/java/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:285-341 — 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/os/kei/ui/page/main/github/history/GitHubActionsNotificationHistoryActionBar.kt:227` 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 (55 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:459— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:459-513 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:802-856 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:459` 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 (41–45 lines × 2) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:101— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:101-145 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideSidebar.kt:81-121 — 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/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:101` 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 (38–39 lines × 2) feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:220— feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:220-257 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:313-351 — 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 `feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:220` 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 (36 lines × 2) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:129— app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:129-164 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:238-273 — 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/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:129` 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 (34–36 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:132— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:132-165 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:179-214 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:132` 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 (33–35 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:471— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:471-503 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:518-552 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:471` 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 (32–33 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:412— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:412-443 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:749-781 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:412` 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 first that the copies are not typed on the same thing: the declarations holding them bind `null` to `modifier = modifier .then( if (onLongClick !=` in one and `modifier = modifier .then( if (longClick !=` 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 (31–32 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:286— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:286-316 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:585-616 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note 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 (30 lines × 3) app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:100— app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:100-129 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:107-136 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:143-172 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt` and `app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:100` 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 (29–30 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:229— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:229-257 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:225-254 — 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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:229` 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 (30 lines × 2) app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:189— app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:189-218 | app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:304-333 — 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/os/kei/ui/page/main/widget/core/AppOverviewCards.kt:189` 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 (29 lines × 4) app/src/main/java/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:131— app/src/main/java/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:131-159 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:90-118 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:97-125 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:138-166 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt` and `app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 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/os/kei/ui/page/main/mcp/skill/state/McpSkillPageTextBundle.kt:131` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28–29 lines × 2) app/src/main/java/os/kei/ui/page/main/debug/DebugComponentLabPage.kt:69— app/src/main/java/os/kei/ui/page/main/debug/DebugComponentLabPage.kt:69-96 | app/src/main/java/os/kei/ui/page/main/debug/DebugLiquidCatalogPage.kt:45-73 — 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/os/kei/ui/page/main/debug/DebugComponentLabPage.kt:69` 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 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 (27 lines × 2) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubCheckLogicSections.kt:337— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubCheckLogicSections.kt:337-363 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubCheckLogicSections.kt:374-400 — 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/os/kei/ui/page/main/github/sheet/GitHubCheckLogicSections.kt:337` 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 (21–26 lines × 6) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:102— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:102-127 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:140-160 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:168-193 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:201-226 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:272-292 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:305-325 — all 6 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:102` 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 (23–25 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:326— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:326-348 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:308-332 — 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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:326` 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 (24–25 lines × 2) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:177— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:177-200 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:244-268 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:244` 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 (22–24 lines × 4) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:403— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:403-424 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:460-482 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:740-762 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:803-826 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:460` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–22 lines × 2) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:93— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:93-114 | app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerSidebar.kt:183-201 — 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/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:93` 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 (21 lines × 2) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:196— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:196-216 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:244-264 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt` and `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 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/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:196` 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–20 lines × 2) app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:545— app/src/main/java/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:545-562 | app/src/main/java/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:507-526 — 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/os/kei/ui/page/main/github/fdroid/FdroidVersionListPage.kt:545` 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–18 lines × 3) app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDroidSourcesSheet.kt:53— app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDroidSourcesSheet.kt:53-69 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:196-213 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackSheets.kt:106-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubDroidSourcesSheet.kt:53` 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 (16–18 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideBottomBar.kt:85— app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideBottomBar.kt:85-100 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuideSidebar.kt:161-178 — 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 (17 lines × 10) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82-98 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:338-358 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:155-171 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:162-178 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:193-209 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerContent.kt:124-140 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:620-636 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:100-116 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:151-167 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:204-220 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt` and `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 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/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82` 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–17 lines × 2) feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:125— feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:125-138 | feature-github/src/main/java/os/kei/feature/github/install/GitHubShizukuPackageInstaller.kt:203-219 — 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 `feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:125` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `feature-github/src/main/java/os/kei/feature/github/install/GitHubShizukuPackageInstaller.kt:202` calls `closeQuietly` and `feature-github/src/main/java/os/kei/feature/github/install/GitHubRootPackageInstaller.kt:123` 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 (16 lines × 14) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82-97 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:338-357 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:155-170 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:162-177 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:193-208 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:162-177 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmNowPlayingMiniPlayer.kt:70-85 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogBottomChromeRoute.kt:45-60 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerContent.kt:124-139 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt:68-83 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:620-635 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:100-115 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:151-166 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:204-219 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt` and `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 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/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82` 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–16 lines × 4) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:429— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:429-443 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:482-497 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:767-781 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:826-841 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidButtons.kt:429` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `modifier = modifier .then( if (onLongClick !=` in one and `modifier = modifier .then( if (longClick !=` 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 (14–16 lines × 3) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:50— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:50-65 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubActionsArtifactDetailSheet.kt:93-106 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubFdroidDetailSheet.kt:71-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:50` 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 (16 lines × 3) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320-335 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:337-352 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:354-369 — 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/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320` 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–16 lines × 3) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:41— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:41-56 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:59-73 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:106-121 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt` and `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:41` 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 × 20) app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82— app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82-96 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:167-181 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt:338-356 | app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackSheets.kt:194-211 | app/src/main/java/os/kei/ui/page/main/host/main/coordinator/MainScreenPagerCoordinator.kt:83-97 | app/src/main/java/os/kei/ui/page/main/os/components/OsPageOverlaySheets.kt:182-196 | app/src/main/java/os/kei/ui/page/main/os/shell/state/OsShellRunnerTextBundle.kt:155-169 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageOverlayState.kt:162-176 | app/src/main/java/os/kei/ui/page/main/os/state/OsPageTextBundle.kt:193-207 | app/src/main/java/os/kei/ui/page/main/settings/state/SettingsSectionContractAssembler.kt:162-176 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmNowPlayingMiniPlayer.kt:70-84 | app/src/main/java/os/kei/ui/page/main/student/catalog/page/BaGuideCatalogBottomChromeRoute.kt:45-59 | app/src/main/java/os/kei/ui/page/main/student/page/component/BaStudentGuidePagerContent.kt:124-138 | feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.kt:375-389 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidExpandableCards.kt:68-82 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidSearchField.kt:620-634 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:100-114 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:151-165 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppStandaloneLiquidButtons.kt:204-218 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidGlassDropdownItems.kt:94-108 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt` and `app/src/main/java/os/kei/ui/page/main/github/sheet/GitHubTrackEditSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 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/os/kei/ui/page/main/github/actions/GitHubActionsSheet.kt:82` 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 (8–15 lines × 2) app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:375— app/src/main/java/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:375-389 | app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncCards.kt:716-723 — 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/os/kei/ui/page/main/sync/WebDavConnectionCards.kt:375` 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 × 5) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:321— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:321-334 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:338-351 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:355-368 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:117-130 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogMoreActionPopup.kt:138-151 — there are 5 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 5 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/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:321` 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–14 lines × 2) app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:96— app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt:96-108 | app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.kt:267-280 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 2) app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:38— app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:38-51 | app/src/main/java/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:84-95 — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportOsPlanner.kt:38` 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 × 4) app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:137— app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:137-149 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:166-178 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:288-300 | app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:316-328 — 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/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:137` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:285` calls `cancel` and `app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportFlowCoordinator.kt:163` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 2) app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:257— app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:257-268 | app/src/main/java/os/kei/ui/page/main/host/pager/MainPagerLayout.kt:306-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/os/kei/ui/page/main/host/pager/MainPagerBottomBar.kt:257` 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 (12 lines × 9) baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29— baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29-40 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:52-63 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:137-148 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:181-192 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:212-223 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:344-355 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:380-391 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:422-433 | baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:498-509 — all 9 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 `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:193` calls `dwellOnHome` and `baselineprofile/src/main/java/os/kei/baselineprofile/MainNavigationFrameBenchmarks.kt:41` 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 (12 lines × 5) app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39— app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39-50 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:119-130 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:57-68 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:104-115 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt:206-217 — before extracting anything, compare `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt` and `app/src/main/java/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateSectionCards.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/os/kei/ui/page/main/student/tabcontent/simulate/GuideSimulateMediaCards.kt:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 3) app/src/main/java/os/kei/ui/page/main/ba/BaOfficePageRepository.kt:174— app/src/main/java/os/kei/ui/page/main/ba/BaOfficePageRepository.kt:174-185 | app/src/main/java/os/kei/ui/page/main/ba/BaPageBindings.kt:20-30 | app/src/main/java/os/kei/ui/page/main/ba/BaSettingsPersistenceRepository.kt:163-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8–12 lines × 3) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:112— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:112-119 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidToastSurface.kt:98-105 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetSurface.kt:131-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/sheet/LiquidSheetSurface.kt:128` calls `offsetProvider` and `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidToastSurface.kt:96` 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 (10–12 lines × 2) app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:24— app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:24-35 | app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:56-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:66` calls `withContext` and `app/src/main/java/os/kei/ui/page/main/student/BaStudentGuideFetch.kt:36` 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 (11–12 lines × 2) app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionSkill.kt:287— app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionSkill.kt:287-297 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionWeapon.kt:166-177 — 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/os/kei/ui/page/main/student/section/GuideSectionSkill.kt:287` 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 (4–12 lines × 3) REDACTED:62— REDACTED:62-72 | REDACTED:65-76 | REDACTED:99-102 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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 `REDACTED:62` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:99` calls `loadIndex` and `REDACTED:62` 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 (11 lines × 4) app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320— app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320-330 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:337-347 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:354-364 | app/src/main/java/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:371-381 — 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/os/kei/ui/page/main/github/section/GitHubTopBarSection.kt:320` 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 (4–11 lines × 4) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:167— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:167-170 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:37-46 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:125-135 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentTokenizer.kt:37-47 — there are 4 copies across 3 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/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:37` calls `optJSONObject` and `app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:167` 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 (9–10 lines × 2) REDACTED:146— REDACTED:146-154 | REDACTED:97-106 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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 `REDACTED:97` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:94` calls `put` and `REDACTED:143` 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 (9 lines × 4) feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:41— feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:41-49 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:65-73 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:90-98 | feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:129-137 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:99` calls `argBoolean`, `get` and `feature-github/src/main/java/os/kei/feature/github/mcp/McpGitHubTrackingTools.kt:50` 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 (3–9 lines × 3) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:17— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:17-19 | app/src/main/java/os/kei/ui/page/main/student/section/GuideSectionVoice.kt:255-263 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/GuideTabVoiceSupport.kt:10-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:17` 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–9 lines × 2) feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:435— feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidMetadataSidecar.kt:435-443 | feature-github/src/main/java/os/kei/feature/github/data/local/fdroid/FdroidRepoCacheModels.kt:500-507 — 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 (10–11 lines × 3) app/src/main/java/os/kei/ui/page/main/about/model/AboutManifestDetails.kt:240— app/src/main/java/os/kei/ui/page/main/about/model/AboutManifestDetails.kt:240-249 | app/src/main/java/os/kei/ui/page/main/about/model/AboutManifestDetails.kt:262-272 | app/src/main/java/os/kei/ui/page/main/about/model/AboutManifestDetails.kt:280-289 — 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/os/kei/ui/page/main/about/model/AboutManifestDetails.kt:240` 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 (7 lines × 5) REDACTED:179— REDACTED:179-185 | REDACTED:250-256 | REDACTED:330-336 | REDACTED:480-486 | REDACTED:207-213 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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 `REDACTED:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideTabVisibility.kt:50— app/src/main/java/os/kei/ui/page/main/student/page/support/BaStudentGuideTabVisibility.kt:50-55 | app/src/main/java/os/kei/ui/page/main/student/tabcontent/render/GuideVoiceTabContent.kt:82-88 — 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/os/kei/ui/page/main/student/page/support/BaStudentGuideTabVisibility.kt:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:130— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:130-135 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:229-234 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:262-267 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:295-300 — 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 `ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/GlassStyle.kt:130` 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 (3–5 lines × 7) app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:101— app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:101-104 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:124-128 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:72-74 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchSimulate.kt:167-169 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:87-92 | app/src/main/java/os/kei/ui/page/main/student/fetch/GuideFetchVoice.kt:320-322 | app/src/main/java/os/kei/ui/page/main/student/fetch/parser/GuideFetchJsonContentTokenizer.kt:25-29 — there are 7 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 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/os/kei/ui/page/main/student/fetch/GuideFetchGallery.kt:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 9) REDACTED:100— REDACTED:100-105 | REDACTED:52-57 | REDACTED:216-220 | REDACTED:274-278 | REDACTED:377-381 | REDACTED:527-531 | REDACTED:281-285 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubStarImportApkVerificationCacheStore.kt:197-201 | REDACTED:231-235 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:362— app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:362-369 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyCards.kt:198-205 | app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmCards.kt:143-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideCatalogV2ListContent.kt:362` 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 (8 lines × 7) core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:117— core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:117-124 | core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:128-135 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseApiClient.kt:196-203 | feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:557-564 | feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubShareImportResolver.kt:352-359 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubPackageRepositoryResolver.kt:375-382 | feature-github/src/main/java/os/kei/feature/github/domain/GitHubRepositoryDiscoveryService.kt:218-225 — there are 7 copies across 6 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 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core-io/src/main/java/os/kei/core/io/OkHttpCallCancellable.kt:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) REDACTED:203— REDACTED:203-210 | REDACTED:260-268 | REDACTED:513-521 | REDACTED:217-225 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 86 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 5) feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:314— feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:314-322 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidPackageApiClient.kt:235-243 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidRepositoryIndexClient.kt:185-193 | feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidSearchApiClient.kt:102-110 | feature-github/src/main/java/os/kei/feature/github/domain/fdroid/FdroidAppSearchService.kt:454-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-github/src/main/java/os/kei/feature/github/data/remote/fdroid/FdroidIndexV2StreamParser.kt:314` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 6) ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:128— ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:128-132 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/dialog/LiquidModalSurface.kt:136-140 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppLiquidCheckbox.kt:270-274 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidMenuSurface.kt:256-260 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidToastSurface.kt:123-127 | ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidToastSurface.kt:131-135 — there are 6 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetJsonMapper.kt:75— feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetJsonMapper.kt:75-81 | REDACTED:241-247 | feature-github/src/main/java/os/kei/feature/github/data/local/GitHubShareImportFlowStore.kt:273-279 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetJsonMapper.kt:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×1
Edited copy of a member (2 corresponding lines) scripts/perf/frame_stages.py:55— scripts/perf/frame_stages.py:55-56 | scripts/perf/switch_report.py:43-44 — 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.
Duplicated block (21–23 lines × 2) scripts/perf/frame_stages.py:18— scripts/perf/frame_stages.py:18-40 | scripts/perf/switch_report.py:10-30 — 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.
No structured logging — No logging call was found in the 1620 JavaScript/TypeScript, JVM production file(s) this check read across 23 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplicated block (5 lines × 2 locations) scripts/qa/viewer_frame_presentation_test.mjs:69— scripts/qa/viewer_frame_presentation_test.mjs:69 · scripts/qa/viewer_frame_presentation_test.mjs:77 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~8 LoC) scripts/ba/test_model_background.mjs— no import path from any entry point (1 application, 0 tooling, 3 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Duplicated predicate app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:128— `!effectiveLoading && visibleFilteredEntries.isEmpty()` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt, app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.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 core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt:223— `!force && now - lastPublishedNanos < SNAPSHOT_INTERVAL_NANOS` appears character-identically in 2 files — core-system/src/main/java/os/kei/core/privilege/RootShellCommandRunner.kt, core-system/src/main/java/os/kei/core/shizuku/service/KeiShizukuUserService.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/os/kei/ui/page/main/github/page/action/GitHubActionsRunStatusDelegate.kt:62— `!isCurrentTarget(item) || state.actionsSelectedWorkflowId != workflow.id` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsRunStatusDelegate.kt, app/src/main/java/os/kei/ui/page/main/github/page/action/GitHubActionsSheetLoader.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/os/kei/ui/page/main/sync/WebDavAutoSync.kt:612— `!outcome.isSuccess && !outcome.requiresReview` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/sync/WebDavAutoSync.kt, app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncHistory.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/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt:604— `!refractionHeight.isFinite() || !refractionAmount.isFinite()` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/home/HomeOverviewGlassBatch.kt, app/src/main/java/os/kei/ui/page/main/widget/core/AppOverviewPillBatch.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/os/kei/ui/page/main/about/page/AboutPage.kt:355— `!searchExpanded && pagerState.isScrollInProgress` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/about/page/AboutPage.kt, app/src/main/java/os/kei/ui/page/main/settings/page/SettingsPage.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/os/kei/ui/page/main/widget/chrome/CompactBottomBarDock.kt:101— `!transition.currentState || !transition.targetState` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/widget/chrome/CompactBottomBarDock.kt, ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/AppFloatingSearchDock.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 feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt:229— `"universal" in name && "release" in name` appears character-identically in 3 files — feature-github-engine/src/main/java/os/kei/feature/github/engine/apk/GitHubApkInspectionEngine.kt, feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsArtifactManifestProbe.kt, feature-github/src/main/java/os/kei/feature/github/install/GitHubInstallArchiveSupport.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 REDACTED:52— `(normalizedOwner.isBlank() || record.owner.equals(normalizedOwner, ignoreCase = true)) && (normalizedRepo.isBlank() || record.repo.equals(no…` appears character-identically in 2 files — REDACTED, REDACTED. 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/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt:407— `(srcWidth / sample) > safeMax || (srcHeight / sample) > safeMax` appears character-identically in 3 files — app/src/main/java/os/kei/feature/ba/data/remote/GameKeeFetchHelper.kt, app/src/main/java/os/kei/ui/page/main/ba/support/BaCalendarPoolRenderHelpers.kt, REDACTED. 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 feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:158— `batchTimedOut.get() && batchTimeoutMs > 0L` appears character-identically in 2 files — feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt, feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.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 ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppStatusPrimitives.kt:157— `borderWidth > 0.dp && borderColor.isSpecified && borderColor.alpha > 0f` appears character-identically in 2 files — ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/core/AppStatusPrimitives.kt, ui-liquid-glass/src/main/java/os/kei/ui/page/main/widget/glass/LiquidSurfaces.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/os/kei/ui/page/main/ba/BaOfficeController.kt:261— `cafeLastHourMs <= 0L || cafeLastHourMs > currentHour` appears character-identically in 3 files — app/src/main/java/os/kei/ui/page/main/ba/BaOfficeController.kt, app/src/main/java/os/kei/ui/page/main/ba/BaPageActions.kt, app/src/main/java/os/kei/ui/page/main/ba/support/BaPageMath.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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:209— `callbacks.isEmpty() && generation != lookupGeneration` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt, app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.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 feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt:734— `cleaned.startsWith("https://", ignoreCase = true) || cleaned.startsWith("http://", ignoreCase = true)` appears character-identically in 2 files — feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseAssetRepository.kt, feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubReleaseNotesHtmlMarkdownConverter.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 ui-liquid-glass/src/main/java/os/kei/ui/animation/DampedDragAnimation.kt:160— `consumeDragChanges && dragAmount != Offset.Zero` appears character-identically in 2 files — ui-liquid-glass/src/main/java/os/kei/ui/animation/DampedDragAnimation.kt, ui-liquid-glass/src/main/java/os/kei/ui/animation/InteractiveHighlight.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/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt:249— `context.checkSelfPermission(Manifest.permission.POST_NOTIFICATIONS) == PackageManager.PERMISSION_GRANTED && NotificationManagerCompat.from(c…` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/sync/WebDavSyncNotificationDispatcher.kt, feature-mcp/src/main/java/os/kei/mcp/notification/McpNotificationHelper.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/os/kei/ui/page/main/github/page/GitHubPageState.kt:405— `current == null || current <= 0L || addedAtMillis < current` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt, app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportAttachStoreSupport.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/os/kei/ui/page/main/github/page/GitHubPageState.kt:383— `current == null || current <= 0L || firstInstallAtMillis < current` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/github/page/GitHubPageState.kt, app/src/main/java/os/kei/ui/page/main/github/share/GitHubShareImportAttachStoreSupport.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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt:73— `currentStates[entry.contentId] == null && entry.contentId !in cachePrewarmCheckedContentIds` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyLookupCoordinator.kt, app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmLookupCoordinator.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 feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt:268— `deadlineNs != Long.MAX_VALUE && System.nanoTime() >= deadlineNs` appears character-identically in 2 files — feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsRecommendedRunRefreshService.kt, feature-github/src/main/java/os/kei/feature/github/domain/GitHubTrackedRefreshBatchRunner.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/os/kei/ui/page/main/student/GuideSkillCardHelper.kt:57— `draft.descriptionByLevel.isNotEmpty() || draft.fallbackDescription.isNotBlank()` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/student/GuideSkillCardHelper.kt, app/src/main/java/os/kei/ui/page/main/student/GuideWeaponCardHelper.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/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt:127— `effectiveLoading && allStudentEntries.isEmpty()` appears character-identically in 2 files — app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideMemoryLobbyTabContent.kt, app/src/main/java/os/kei/ui/page/main/student/catalog/component/BaGuideStudentBgmTabContent.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 feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt:388— `end == value.length || !value[end].isAsciiLetterOrDigit()` appears character-identically in 2 files — feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsArtifactSelector.kt, feature-github/src/main/java/os/kei/feature/github/domain/GitHubActionsWorkflowSelector.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 core-system/src/main/java/os/kei/core/system/AppCommandExecutor.kt:32— `exitCode == 0 && !timedOut && !cancelled` appears character-identically in 2 files — core-system/src/main/java/os/kei/core/system/AppCommandExecutor.kt, core-system/src/main/java/os/kei/core/system/RuntimeCommandExecutor.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.
Silent fallback default in catch app/src/main/java/os/kei/mcp/bridge/AppMcpBaToolDelegate.kt:590— `parseBgmFavoriteAudioUrls` 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/os/kei/mcp/bridge/AppMcpWebDavToolPlugin.kt:159— `safeWebDavHost` swallows every exception into `""` — 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/os/kei/ui/page/main/about/util/AboutPageUtils.kt:14— `formatTime` swallows every exception into `""` — 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/os/kei/ui/page/main/ba/support/BaCalendarPoolRenderHelpers.kt:196— `formatBaDateTimeNoYearInTimeZone` swallows every exception into `"-"` — 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/os/kei/ui/page/main/github/asset/GitHubDirectApkInstallAssets.kt:137— `assetNameFromUrl` swallows every exception into `""` — 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/os/kei/ui/page/main/github/asset/GitHubFdroidInstallAssets.kt:148— `resolveFdroidApkDownloadUrl` swallows every exception into `""` — 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/os/kei/ui/page/main/github/asset/GitHubFdroidInstallAssets.kt:178— `fdroidAssetNameFromUrl` swallows every exception into `""` — 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/os/kei/ui/page/main/github/release/GitHubReleaseListPage.kt:1008— `shortReleaseDate` swallows every exception into `""` — 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/os/kei/ui/page/main/jsonimport/KeiOSJsonImportPreviewSupport.kt:266— `buildJsonImportBgmSamples` 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/os/kei/ui/page/main/os/OsLowLevelInfoRows.kt:47— `settingsGlobalString` swallows every exception into `""` — 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/os/kei/ui/page/main/os/OsLowLevelInfoRows.kt:56— `webViewProvider` swallows every exception into `""` — 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/os/kei/ui/page/main/os/OsLowLevelInfoRows.kt:67— `fingerprintedPartitions` swallows every exception into `""` — 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/os/kei/ui/page/main/os/OsLowLevelInfoRows.kt:77— `sdkExtensions` swallows every exception into `""` — 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/os/kei/ui/page/main/os/OsLowLevelInfoRows.kt:264— `dataStorageCapacity` swallows every exception into `""` — 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/os/kei/ui/page/main/os/OsPageData.kt:130— `packageVersionName` swallows every exception into `""` — 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/os/kei/ui/page/main/os/shell/OsShellCommandBuiltInMerge.kt:49— `readDeletedBuiltInShellCardIds` swallows every exception into `emptySet()` — 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/os/kei/ui/page/main/os/shell/OsShellCommandCardCodec.kt:70— `decodeCards` 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/os/kei/ui/page/main/os/shortcut/OsActivityShortcutCardCodec.kt:56— `decodeCards` 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/os/kei/ui/page/main/os/store/OsShortcutCardStore.kt:127— `decodeIntentExtras` 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/os/kei/ui/page/main/settings/state/SettingsPageRepository.kt:49— `listCacheEntries` 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/os/kei/ui/page/main/settings/support/SettingsPageSupport.kt:352— `formatLogTime` swallows every exception into `""` — 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 REDACTED:399— `totalFileBytes` swallows every exception into `0L` — 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 REDACTED:163— `latestSyncedAtMs` swallows every exception into `0L` — 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 REDACTED:234— `totalFileBytes` swallows every exception into `0L` — 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/os/kei/ui/page/main/student/BaStudentGuideStore.kt:530— `readGuideSyncedAtMsFromMetaRaw` swallows every exception into `0L` — 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.
+ 14 more in this group — see findings.md.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×5
Projects may be oversized for their cohesion app/build.gradle.kts:1— `app` (207193 LoC, 3083 module-visible types across 131 directories) overshoots its size bounds. 5 of 23 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 5.7/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.
Projects may be oversized for their cohesion feature-github/build.gradle.kts:1— `feature-github` (32558 LoC, 674 module-visible types across 9 directories) overshoots its size bounds. 5 of 23 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 5.7/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.
Projects may be oversized for their cohesion ui-liquid-glass/build.gradle.kts:1— `ui-liquid-glass` (24784 LoC, 282 module-visible types across 12 directories) overshoots its size bounds. 5 of 23 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 5.7/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.
Projects may be oversized for their cohesion core-notification/build.gradle.kts:1— `core-notification` (7240 LoC, 314 module-visible types across 7 directories) overshoots its size bounds. 5 of 23 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 5.7/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.
Projects may be oversized for their cohesion feature-github-engine/build.gradle.kts:1— `feature-github-engine` (9010 LoC, 288 module-visible types across 7 directories) overshoots its size bounds. 5 of 23 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 5.7/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.
Hand-rolled JSON/XML parsing via regex feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubHtmlRepositoryProfileSource.kt:246— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex feature-github-engine/src/main/java/os/kei/feature/github/data/remote/GitHubHtmlRepositoryProfileSource.kt:249— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex feature-github/src/main/java/os/kei/feature/github/data/remote/GitHubActionsNightlyLinkRepository.kt:790— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
No ADRs found app/build.gradle.kts:81— 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 81).
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 1206 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1206 of the 1643 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: app/src/main/java/os/kei/ui/navigation/Navigator.kt. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file app/src/main/java/os/kei/ui/navigation/Navigator.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
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 .github/workflows/ci-debug-apk.yml:21— 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 2 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:375— `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 functions that make a request accept an AbortSignal or the coroutine's cancellation · ×1
Not all functions that make a request accept an AbortSignal or the coroutine's cancellation — Only 2/5 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin 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.
Silent fallback default on parse failure app/src/main/java/os/kei/ui/page/main/ba/support/BaAccountStore.kt:51— `loadAccounts` answers `emptyList()` when `SerializationException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. 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.
Subsumed condition operand app/src/main/java/os/kei/ui/page/main/student/media/GuideBgmFavoriteStore.kt:334— `normalizedDisplayTitle.startsWith("回忆大厅BGM")` can never decide this `||` — every value satisfying `normalizedDisplayTitle.startsWith("回忆大厅BGM")` also satisfies `normalizedDisplayTitle.startsWith("回忆大厅")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
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) and a Gradle version catalogue — 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 52 file(s) — `app/src/main/java/os/kei/feature/home/data/HomeOverviewRepository.kt`, `app/src/main/java/os/kei/memory/AppMemoryRelease.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaAccountManagementSheet.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaCalendarPoolUnreadRepository.kt`, `app/src/main/java/os/kei/ui/page/main/ba/BaDailyDoneTemplateActivity.kt`, … (+47 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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) and a Gradle version catalogue — not scanned yet).
0
—
Run 01a1e931-0d78-7712-9e9e-831b93295db1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 20 · Warnings: 1585 · Recommendations: 101 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 11:07 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.