Public report of v1tzor/StudyAssistant, published 22 October 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.10.5). Watchdog 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, 22 October 2026, 11:53 UTC · Survey ID cd_90bcf6e004c54015a8a25308cebcd2bc
v1tzor/StudyAssistant
Measured 22 October 2026, 11:45 UTC, at code version fea4593
Knowledge freshness is not measured: History too condensed to judge knowledge freshness.
CAI scoreAt riskDown 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 141,749 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 2.0 person-years · Weakest lens: Production Readiness, 59
Findings by how serious they are
8 critical494 serious40 minor
16 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 11:45 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
66of 70 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
517of 542 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
70dimensions across 7 lenses, read from 141,749 lines of product code in 32 projects.
v1tzor/StudyAssistant scores 69 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 59 and is rated Adequate. Its Security & performance tooling dimension scores 3 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to 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 and to resolve the 1 No ADRs found finding(s) in ADR Quality, and if Production Readiness rose to 70, the score would rise from 69 to about 74.
Eight findings are critical: five in Dependency Vulnerabilities, two in Secrets (history) and one in Static Analysis (SAST).
Watchdog couldn't measure 13 dimensions in this code, among them Code Coverage, Test Reliability and License Compliance, so they are left out of the score. The product code is 141,749 lines, which would take an estimated 2.0 person-years, around €300,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.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Rebuild cost: about €300,000 · Estimate
Cost to rebuild
€99,000 to €500,000, for 1,647 to 5,224 hours of work, about 2.0 person-years for 1 to 4 engineers
Difficulty of the problem
High, 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
×1.0 at a score of 69. 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: 141,749 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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 €300,000 to build again, about 2.0 person-years of work. Its weakest lens is Production Readiness, at 59 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph 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.
1290 modules, with 3459 dependencies between them. 18 loops run through 38 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1250 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
core.common.architecture.component uses core.common.architecture.store.BaseComposeStore, so a change to core.common.architecture.store.BaseComposeStore can break core.common.architecture.component, while a change to core.common.architecture.component can't break core.common.architecture.store.BaseComposeStore.
Position
Below the diagonal: core.common.architecture.component uses a module listed above it, which is the healthy direction.
core.common.architecture.store.work uses core.common.functional, so a change to core.common.functional can break core.common.architecture.store.work, while a change to core.common.architecture.store.work can't break core.common.functional.
Position
Below the diagonal: core.common.architecture.store.work uses a module listed above it, which is the healthy direction.
core.common.managers uses core.common.functional, so a change to core.common.functional can break core.common.managers, while a change to core.common.managers can't break core.common.functional.
Position
Below the diagonal: core.common.managers uses a module listed above it, which is the healthy direction.
11→23 core.domain.entities.goals uses core.domain.entities.taskspart of a loop✕
Connections
4 pairs of types, where a type in core.domain.entities.goals uses a type in core.domain.entities.tasks.
core.domain.entities.goals uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break core.domain.entities.goals, while a change to core.domain.entities.goals can't break core.domain.entities.tasks.
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.
core.domain.entities.settings uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.settings, while a change to core.domain.entities.settings can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.settings uses a module listed above it, which is the healthy direction.
core.domain.entities.subject uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.subject, while a change to core.domain.entities.subject can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.subject uses a module listed above it, which is the healthy direction.
13→18 core.domain.entities.subject uses core.domain.entities.employeepart of a loop✕
Connections
1 pair of types, where a type in core.domain.entities.subject uses a type in core.domain.entities.employee.
core.domain.entities.subject uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.domain.entities.subject, while a change to core.domain.entities.subject can't break core.domain.entities.employee.
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.
editor.impl.domain.entities uses core.common.functional, so a change to core.common.functional can break editor.impl.domain.entities, while a change to editor.impl.domain.entities can't break core.common.functional.
Position
Below the diagonal: editor.impl.domain.entities uses a module listed above it, which is the healthy direction.
core.common.architecture.store uses core.common.architecture.store.communicators, so a change to core.common.architecture.store.communicators can break core.common.architecture.store, while a change to core.common.architecture.store can't break core.common.architecture.store.communicators.
Position
Below the diagonal: core.common.architecture.store uses a module listed above it, which is the healthy direction.
core.common.architecture.store uses core.common.architecture.component, so a change to core.common.architecture.component can break core.common.architecture.store, while a change to core.common.architecture.store can't break core.common.architecture.component.
Position
Below the diagonal: core.common.architecture.store uses a module listed above it, which is the healthy direction.
core.common.architecture.store uses core.common.managers, so a change to core.common.managers can break core.common.architecture.store, while a change to core.common.architecture.store can't break core.common.managers.
Position
Below the diagonal: core.common.architecture.store uses a module listed above it, which is the healthy direction.
core.common.architecture.store.work.WorkResult uses core.common.architecture.store.work, so a change to core.common.architecture.store.work can break core.common.architecture.store.work.WorkResult, while a change to core.common.architecture.store.work.WorkResult can't break core.common.architecture.store.work.
Position
Below the diagonal: core.common.architecture.store.work.WorkResult uses a module listed above it, which is the healthy direction.
core.common.inject uses core.common.architecture.component, so a change to core.common.architecture.component can break core.common.inject, while a change to core.common.inject can't break core.common.architecture.component.
Position
Below the diagonal: core.common.inject uses a module listed above it, which is the healthy direction.
core.domain.entities.employee uses core.common.functional, so a change to core.common.functional can break core.domain.entities.employee, while a change to core.domain.entities.employee can't break core.common.functional.
Position
Below the diagonal: core.domain.entities.employee uses a module listed above it, which is the healthy direction.
core.domain.entities.employee uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.employee, while a change to core.domain.entities.employee can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.employee uses a module listed above it, which is the healthy direction.
core.domain.entities.employee uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.domain.entities.employee, while a change to core.domain.entities.employee can't break core.domain.entities.subject.
Position
Below the diagonal: core.domain.entities.employee uses a module listed above it, which is the healthy direction.
core.presentation.models.settings uses core.domain.entities.common, so a change to core.domain.entities.common can break core.presentation.models.settings, while a change to core.presentation.models.settings can't break core.domain.entities.common.
Position
Below the diagonal: core.presentation.models.settings uses a module listed above it, which is the healthy direction.
core.presentation.models.settings uses core.domain.entities.settings, so a change to core.domain.entities.settings can break core.presentation.models.settings, while a change to core.presentation.models.settings can't break core.domain.entities.settings.
Position
Below the diagonal: core.presentation.models.settings uses a module listed above it, which is the healthy direction.
editor.impl.presentation.ui.root.EditorFeatureComponent uses core.common.architecture.component, so a change to core.common.architecture.component can break editor.impl.presentation.ui.root.EditorFeatureComponent, while a change to editor.impl.presentation.ui.root.EditorFeatureComponent can't break core.common.architecture.component.
Position
Below the diagonal: editor.impl.presentation.ui.root.EditorFeatureComponent uses a module listed above it, which is the healthy direction.
core.domain.entities.organizations uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.organizations, while a change to core.domain.entities.organizations can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.organizations uses a module listed above it, which is the healthy direction.
core.domain.entities.organizations uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.domain.entities.organizations, while a change to core.domain.entities.organizations can't break core.domain.entities.subject.
Position
Below the diagonal: core.domain.entities.organizations uses a module listed above it, which is the healthy direction.
core.domain.entities.organizations uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.domain.entities.organizations, while a change to core.domain.entities.organizations can't break core.domain.entities.employee.
Position
Below the diagonal: core.domain.entities.organizations uses a module listed above it, which is the healthy direction.
core.presentation.models.users uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.presentation.models.users, while a change to core.presentation.models.users can't break core.domain.entities.employee.
Position
Below the diagonal: core.presentation.models.users uses a module listed above it, which is the healthy direction.
22→24 core.presentation.models.users uses core.presentation.models.subjectspart of a loop✕
Connections
1 pair of types, where a type in core.presentation.models.users uses a type in core.presentation.models.subjects.
core.presentation.models.users uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break core.presentation.models.users, while a change to core.presentation.models.users can't break core.presentation.models.subjects.
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.
core.domain.entities.tasks uses core.domain.entities.goals, so a change to core.domain.entities.goals can break core.domain.entities.tasks, while a change to core.domain.entities.tasks can't break core.domain.entities.goals.
Position
Below the diagonal: core.domain.entities.tasks uses a module listed above it, which is the healthy direction.
core.domain.entities.tasks uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.domain.entities.tasks, while a change to core.domain.entities.tasks can't break core.domain.entities.subject.
Position
Below the diagonal: core.domain.entities.tasks uses a module listed above it, which is the healthy direction.
core.domain.entities.tasks uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break core.domain.entities.tasks, while a change to core.domain.entities.tasks can't break core.domain.entities.organizations.
Position
Below the diagonal: core.domain.entities.tasks uses a module listed above it, which is the healthy direction.
core.presentation.models.subjects uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.presentation.models.subjects, while a change to core.presentation.models.subjects can't break core.domain.entities.subject.
Position
Below the diagonal: core.presentation.models.subjects uses a module listed above it, which is the healthy direction.
core.presentation.models.subjects uses core.presentation.models.users, so a change to core.presentation.models.users can break core.presentation.models.subjects, while a change to core.presentation.models.subjects can't break core.presentation.models.users.
Position
Below the diagonal: core.presentation.models.subjects uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.common.functional, so a change to core.common.functional can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.common.functional.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.domain.entities.subject.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.domain.entities.employee.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.domain.entities.organizations.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.domain.entities.classes uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break core.domain.entities.classes, while a change to core.domain.entities.classes can't break core.domain.entities.tasks.
Position
Below the diagonal: core.domain.entities.classes uses a module listed above it, which is the healthy direction.
core.presentation.models.organizations uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break core.presentation.models.organizations, while a change to core.presentation.models.organizations can't break core.domain.entities.organizations.
Position
Below the diagonal: core.presentation.models.organizations uses a module listed above it, which is the healthy direction.
core.presentation.models.organizations uses core.presentation.models.users, so a change to core.presentation.models.users can break core.presentation.models.organizations, while a change to core.presentation.models.organizations can't break core.presentation.models.users.
Position
Below the diagonal: core.presentation.models.organizations uses a module listed above it, which is the healthy direction.
core.presentation.models.organizations uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break core.presentation.models.organizations, while a change to core.presentation.models.organizations can't break core.presentation.models.subjects.
Position
Below the diagonal: core.presentation.models.organizations uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.common.functional, so a change to core.common.functional can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.common.functional.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.settings, so a change to core.domain.entities.settings can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.settings.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.subject, so a change to core.domain.entities.subject can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.subject.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.employee, so a change to core.domain.entities.employee can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.employee.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.organizations.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.tasks.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
analytics.impl.domain.entities uses core.domain.entities.classes, so a change to core.domain.entities.classes can break analytics.impl.domain.entities, while a change to analytics.impl.domain.entities can't break core.domain.entities.classes.
Position
Below the diagonal: analytics.impl.domain.entities uses a module listed above it, which is the healthy direction.
core.domain.entities.schedules.base uses core.common.functional, so a change to core.common.functional can break core.domain.entities.schedules.base, while a change to core.domain.entities.schedules.base can't break core.common.functional.
Position
Below the diagonal: core.domain.entities.schedules.base uses a module listed above it, which is the healthy direction.
core.domain.entities.schedules.base uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.entities.schedules.base, while a change to core.domain.entities.schedules.base can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.entities.schedules.base uses a module listed above it, which is the healthy direction.
core.domain.entities.schedules.base uses core.domain.entities.classes, so a change to core.domain.entities.classes can break core.domain.entities.schedules.base, while a change to core.domain.entities.schedules.base can't break core.domain.entities.classes.
Position
Below the diagonal: core.domain.entities.schedules.base uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.common.functional, so a change to core.common.functional can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.common.functional.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.domain.entities.common, so a change to core.domain.entities.common can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.domain.entities.common.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.domain.entities.subject.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.presentation.models.users, so a change to core.presentation.models.users can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.presentation.models.users.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.presentation.models.subjects.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.schedules uses core.presentation.models.organizations, so a change to core.presentation.models.organizations can break core.presentation.models.schedules, while a change to core.presentation.models.schedules can't break core.presentation.models.organizations.
Position
Below the diagonal: core.presentation.models.schedules uses a module listed above it, which is the healthy direction.
core.presentation.models.tasks uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break core.presentation.models.tasks, while a change to core.presentation.models.tasks can't break core.domain.entities.tasks.
Position
Below the diagonal: core.presentation.models.tasks uses a module listed above it, which is the healthy direction.
core.presentation.models.tasks uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break core.presentation.models.tasks, while a change to core.presentation.models.tasks can't break core.presentation.models.subjects.
Position
Below the diagonal: core.presentation.models.tasks uses a module listed above it, which is the healthy direction.
core.presentation.models.tasks uses core.presentation.models.organizations, so a change to core.presentation.models.organizations can break core.presentation.models.tasks, while a change to core.presentation.models.tasks can't break core.presentation.models.organizations.
Position
Below the diagonal: core.presentation.models.tasks uses a module listed above it, which is the healthy direction.
schedule.impl.presentation.models.classes uses core.common.functional, so a change to core.common.functional can break schedule.impl.presentation.models.classes, while a change to schedule.impl.presentation.models.classes can't break core.common.functional.
Position
Below the diagonal: schedule.impl.presentation.models.classes uses a module listed above it, which is the healthy direction.
schedule.impl.presentation.models.classes uses core.domain.entities.subject, so a change to core.domain.entities.subject can break schedule.impl.presentation.models.classes, while a change to schedule.impl.presentation.models.classes can't break core.domain.entities.subject.
Position
Below the diagonal: schedule.impl.presentation.models.classes uses a module listed above it, which is the healthy direction.
schedule.impl.presentation.models.classes uses core.presentation.models.users, so a change to core.presentation.models.users can break schedule.impl.presentation.models.classes, while a change to schedule.impl.presentation.models.classes can't break core.presentation.models.users.
Position
Below the diagonal: schedule.impl.presentation.models.classes uses a module listed above it, which is the healthy direction.
schedule.impl.presentation.models.classes uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break schedule.impl.presentation.models.classes, while a change to schedule.impl.presentation.models.classes can't break core.presentation.models.subjects.
Position
Below the diagonal: schedule.impl.presentation.models.classes uses a module listed above it, which is the healthy direction.
schedule.impl.presentation.models.classes uses core.presentation.models.organizations, so a change to core.presentation.models.organizations can break schedule.impl.presentation.models.classes, while a change to schedule.impl.presentation.models.classes can't break core.presentation.models.organizations.
Position
Below the diagonal: schedule.impl.presentation.models.classes uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.common.functional, so a change to core.common.functional can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.common.functional.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.domain.entities.goals, so a change to core.domain.entities.goals can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.domain.entities.goals.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.domain.entities.subject, so a change to core.domain.entities.subject can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.domain.entities.subject.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.domain.entities.organizations.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.domain.entities.tasks.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.entities uses core.domain.entities.classes, so a change to core.domain.entities.classes can break tasks.impl.domain.entities, while a change to tasks.impl.domain.entities can't break core.domain.entities.classes.
Position
Below the diagonal: tasks.impl.domain.entities uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.common.functional, so a change to core.common.functional can break core.domain.repositories, while a change to core.domain.repositories can't break core.common.functional.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.common, so a change to core.domain.entities.common can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.common.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.goals, so a change to core.domain.entities.goals can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.goals.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.settings, so a change to core.domain.entities.settings can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.settings.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.subject.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.employee.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.organizations.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.tasks.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.classes, so a change to core.domain.entities.classes can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.classes.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
core.domain.repositories uses core.domain.entities.schedules.base, so a change to core.domain.entities.schedules.base can break core.domain.repositories, while a change to core.domain.repositories can't break core.domain.entities.schedules.base.
Position
Below the diagonal: core.domain.repositories uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.common.functional, so a change to core.common.functional can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.common.functional.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.common, so a change to core.domain.entities.common can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.common.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.settings, so a change to core.domain.entities.settings can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.settings.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.subject, so a change to core.domain.entities.subject can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.subject.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses editor.impl.domain.entities, so a change to editor.impl.domain.entities can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break editor.impl.domain.entities.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.employee, so a change to core.domain.entities.employee can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.employee.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.organizations.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.tasks.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.classes, so a change to core.domain.entities.classes can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.classes.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
editor.impl.domain.interactors uses core.domain.entities.schedules.base, so a change to core.domain.entities.schedules.base can break editor.impl.domain.interactors, while a change to editor.impl.domain.interactors can't break core.domain.entities.schedules.base.
Position
Below the diagonal: editor.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.common.functional, so a change to core.common.functional can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.common.functional.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.domain.entities.subject, so a change to core.domain.entities.subject can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.domain.entities.subject.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.domain.entities.employee, so a change to core.domain.entities.employee can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.domain.entities.employee.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.domain.entities.organizations.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.domain.entities.classes, so a change to core.domain.entities.classes can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.domain.entities.classes.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
schedule.impl.domain.entities uses core.domain.entities.schedules.base, so a change to core.domain.entities.schedules.base can break schedule.impl.domain.entities, while a change to schedule.impl.domain.entities can't break core.domain.entities.schedules.base.
Position
Below the diagonal: schedule.impl.domain.entities uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses core.common.functional, so a change to core.common.functional can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break core.common.functional.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses core.domain.entities.goals, so a change to core.domain.entities.goals can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break core.domain.entities.goals.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses core.domain.entities.subject, so a change to core.domain.entities.subject can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break core.domain.entities.subject.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break core.domain.entities.organizations.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break core.domain.entities.tasks.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.domain.interactors uses tasks.impl.domain.entities, so a change to tasks.impl.domain.entities can break tasks.impl.domain.interactors, while a change to tasks.impl.domain.interactors can't break tasks.impl.domain.entities.
Position
Below the diagonal: tasks.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.tasks uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break tasks.impl.presentation.models.tasks, while a change to tasks.impl.presentation.models.tasks can't break core.domain.entities.tasks.
Position
Below the diagonal: tasks.impl.presentation.models.tasks uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.tasks uses core.presentation.models.subjects, so a change to core.presentation.models.subjects can break tasks.impl.presentation.models.tasks, while a change to tasks.impl.presentation.models.tasks can't break core.presentation.models.subjects.
Position
Below the diagonal: tasks.impl.presentation.models.tasks uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.tasks uses core.presentation.models.organizations, so a change to core.presentation.models.organizations can break tasks.impl.presentation.models.tasks, while a change to tasks.impl.presentation.models.tasks can't break core.presentation.models.organizations.
Position
Below the diagonal: tasks.impl.presentation.models.tasks uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.tasks uses core.presentation.models.tasks, so a change to core.presentation.models.tasks can break tasks.impl.presentation.models.tasks, while a change to tasks.impl.presentation.models.tasks can't break core.presentation.models.tasks.
Position
Below the diagonal: tasks.impl.presentation.models.tasks uses a module listed above it, which is the healthy direction.
37→40 tasks.impl.presentation.models.tasks uses tasks.impl.presentation.models.goalspart of a loop✕
Connections
3 pairs of types, where a type in tasks.impl.presentation.models.tasks uses a type in tasks.impl.presentation.models.goals.
tasks.impl.presentation.models.tasks uses tasks.impl.presentation.models.goals, so a change to tasks.impl.presentation.models.goals can break tasks.impl.presentation.models.tasks, while a change to tasks.impl.presentation.models.tasks can't break tasks.impl.presentation.models.goals.
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.
core.data.repositories uses core.common.functional, so a change to core.common.functional can break core.data.repositories, while a change to core.data.repositories can't break core.common.functional.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.common, so a change to core.domain.entities.common can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.common.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.common.managers, so a change to core.common.managers can break core.data.repositories, while a change to core.data.repositories can't break core.common.managers.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.goals, so a change to core.domain.entities.goals can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.goals.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.settings, so a change to core.domain.entities.settings can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.settings.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.subject, so a change to core.domain.entities.subject can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.subject.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.employee, so a change to core.domain.entities.employee can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.employee.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.organizations.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.tasks.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.classes, so a change to core.domain.entities.classes can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.classes.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.entities.schedules.base, so a change to core.domain.entities.schedules.base can break core.data.repositories, while a change to core.data.repositories can't break core.domain.entities.schedules.base.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
core.data.repositories uses core.domain.repositories, so a change to core.domain.repositories can break core.data.repositories, while a change to core.data.repositories can't break core.domain.repositories.
Position
Below the diagonal: core.data.repositories uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.common.functional, so a change to core.common.functional can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.common.functional.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.domain.entities.subject, so a change to core.domain.entities.subject can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.domain.entities.subject.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.domain.entities.employee, so a change to core.domain.entities.employee can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.domain.entities.employee.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.domain.entities.organizations, so a change to core.domain.entities.organizations can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.domain.entities.organizations.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.domain.entities.tasks, so a change to core.domain.entities.tasks can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.domain.entities.tasks.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses core.domain.entities.schedules.base, so a change to core.domain.entities.schedules.base can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break core.domain.entities.schedules.base.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
schedule.impl.domain.interactors uses schedule.impl.domain.entities, so a change to schedule.impl.domain.entities can break schedule.impl.domain.interactors, while a change to schedule.impl.domain.interactors can't break schedule.impl.domain.entities.
Position
Below the diagonal: schedule.impl.domain.interactors uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.goals uses core.domain.entities.goals, so a change to core.domain.entities.goals can break tasks.impl.presentation.models.goals, while a change to tasks.impl.presentation.models.goals can't break core.domain.entities.goals.
Position
Below the diagonal: tasks.impl.presentation.models.goals uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.goals uses core.presentation.models.tasks, so a change to core.presentation.models.tasks can break tasks.impl.presentation.models.goals, while a change to tasks.impl.presentation.models.goals can't break core.presentation.models.tasks.
Position
Below the diagonal: tasks.impl.presentation.models.goals uses a module listed above it, which is the healthy direction.
tasks.impl.presentation.models.goals uses tasks.impl.presentation.models.tasks, so a change to tasks.impl.presentation.models.tasks can break tasks.impl.presentation.models.goals, while a change to tasks.impl.presentation.models.goals can't break tasks.impl.presentation.models.tasks.
Position
Below the diagonal: tasks.impl.presentation.models.goals uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
9
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
A05:2025 — Injection
1
High / Critical
A02:2025 — Security Misconfiguration
1
Medium
A01:2025 — Broken Access Control
1
Medium
Roadmap
First, integrate automated security scanning into the CI pipeline to block regressions before they land. Second, maintain a changelog for every release and restrict public API exposure to ensure internal changes do not break consumers. Finally, extend structured logging across all runnable modules to improve production diagnosability and address the single gap in architectural decision records.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Code Duplication: Members sharing a duplicated core (9 members, 50+ identical tokens)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 8
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 — 494
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 40
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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
Watchdog 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. 66 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 70 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, 517 of 542 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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.
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 (2 contributor(s) across 212 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% 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.
D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. `androidApp/src/main/java/ru/aleshin/studyassistant/application/StudyAssistantApp.kt`, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/security/ShareCode.kt`, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt`, `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/OutputConsumer.kt`, `shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/ktor/NetworkConnectionChecker.kt`, … (+3 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.
D34 Knowledge Freshness — git history too condensed for a reliable signal — The history looks squashed or freshly imported, so per-file ownership reflects those commits rather than real maintenance. This dimension is reported as a low-confidence advisory and is not scored.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Kodein, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (androidApp). the Android app did not build — `./gradlew :androidApp:assembleDebug` exited 1: a45c7f4c64abc77460e1c00f541e9f960e3c7ed2538f1ede19eacd873ae'
at org.gradle.wrapper.Install.verifyDownloadChecksum(Install.java:165)
at org.gradle.wrapper.Install.access$800(Install.java:27)
at org…; runtime evidence skipped (launch chosen because androidApp/build.gradle.kts applies the Android application plugin and gradlew builds it).
C2 Access Controls — not measured this run — Watchdog 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.
DM9 Scattered domain decisions — not measured this run — Watchdog 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 measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
ED5 Idempotency — not measured this run — Watchdog 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift 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.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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 REDACTED (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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
21 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ImportComposeStore.handleEvent at 49. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Base.execute at 28 — they are counted neither in the figure above nor in this dimension's score. 4 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: shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AiToolConfirmationCard.kt (AiToolConfirmationCardKt.argumentLabel at 25), shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/Placeholders.kt (PlaceholdersKt.highlightColorFor at 19), shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/mappers/BackendShareErrorMapper.kt (BackendShareErrorMapperKt.mapBackendShareError at 16), shared/features/settings/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/settings/impl/presentation/ui/root/SettingsContentProvider.kt (SettingsContentProvider.RootContent at 16). 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.
+ 16 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with ImportComposeStore.handleEvent (cyclomatic 49). — Refactoring it lifts Cyclomatic Complexity from 7.1 to about 7.6/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with OverviewTopSheetKt.OverviewTopSheetAnalysis (cognitive 42), ImportComposeStore.handleEvent (cognitive 39). — 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 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 107 MethodTooLong finding(s) in God Classes — start with AiAssistantInteractor.kt (11), GoalsInteractor.kt (7), HomeworksInteractor.kt (7). — One of this dimension's main actionable groups (107 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with REDACTED, TextFields.kt, ImportStatusLayouts.kt. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with REDACTED, ScheduleImportHandler.kt, AnalyticsReportCalculator.kt. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
266 duplicated block group(s) detected. A further 18 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 100 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), DeepSeekScheduleExtractionMapper.kt, StartClassesReminderWorker.kt. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 14 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ImportClassEditorSheet.kt (2), HomeworkSharingRepositoryImpl.kt, AiCompletionHandler.kt. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with StoredHomeworkShare.kt (2), StudyAssistantApp.kt, ComponentExt.kt. — One of this dimension's main actionable groups (13 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.2 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
32 production modules (Gradle), 0 dependency cycle(s), 9 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; 3 module(s) off the main sequence.
Off the main sequence: StudyAssistant:shared:core:presentation · ×3
What to do
Resolve the 9 Unstable project StudyAssistant finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
Low cohesion: Base (LCOM4 11)shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:96
What to do
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ScheduleImportHandler.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
1 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 1 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
Outdated: YandexMobileAds
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt (8×49=392); shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt (6×23=138); shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.kt (3×23=69) Repeated repair below the complexity floor: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt (5 of 9 changes were fixes); shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiConversationHandler.kt (4 of 6 changes were fixes); shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportCompactLayout.kt (4 of 5 changes were fixes)
Resolve the 13 Hotspot finding(s) in Churn × Complexity Hotspots — start with ImportComposeStore.kt, AssistantComposeStore.kt, ShareComposeStore.kt. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 7 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ImportLayout.kt, AiConversationHandler.kt, ImportCompactLayout.kt. — One of this dimension's main actionable groups (7 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 141749 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: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's single README is a polished marketing page with branding badges and links to GitHub stats (forks, stars, releases), but it contains no overview of what the project does or what it is for, no installation/build/usage instructions, no contribution guidance, and no licence statement. The document is an advertisement rather than documentation — it lacks the four standard README sections that a repository root README must provide.
Documentation: no project overview · ×3README.md
What to do
Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStronggated by 1 serious finding◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
1 API inconsistencies across a 400-member sample of 1776 exposed types.
Inconsistent naming for the same domain concept (entity identifier) across feature APIs. One uses 'employeeId' and the other uses 'homeworkId', while both are nullable String identifiers for navigation targets.
What to do
Resolve the 1 Inconsistent naming for the same domain concept (entity identifier)… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion3.9 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
10 of 32 build units (Gradle, Xcode) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: 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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. semgrep hit a parse error in 3 file(s) — `backend/ktor/gradlew` (line 74, line 178), `gradlew` (line 177), `widget/src/androidMain/kotlin/ru/aleshin/studyassistant/widget/presentation/theme/WidgetTheme.kt` (line 135, line 138) — 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
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 8 file(s) — `androidApp/src/main/java/ru/aleshin/studyassistant/application/StudyAssistantApp.kt`, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/security/ShareCode.kt`, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt`, `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/OutputConsumer.kt`, `shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/ktor/NetworkConnectionChecker.kt`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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 31 platform declaration(s) and 117 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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No in-app HTTPS enforcement, but the server reads the forwarded scheme (X-Forwarded-Proto, Ktor's XForwardedHeaders, Spring's ForwardedHeaderFilter) — a TLS-terminating reverse proxy sits in front of it, where serving TLS in the app would be wrong. Verify the reverse proxy enforces TLS. — backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/plugins/HttpSecurity.kt:25
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (SQLCipher, a Realm encryptionKey, field-level AEAD) — partial coverage still leaves gaps.
Do you agree with this assessment?
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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 clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 31 of 31 project(s) that lack one — worth up to 2 pts.
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 README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
1776/2394 types (74%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability6.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `iosApp`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) so requests are traceable across the system, not just health-probable.
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 7028 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.
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.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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 database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 25 use(s) across 152,591 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
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 the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. 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 · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. 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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. 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 a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether suspend functions that make a cancellable request accept or pass on the coroutine's cancellation (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
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 method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. 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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. 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. (×5) — backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/api/validation/ScheduleImageGuard.kt:59, backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/ScheduleImageNormalizer.kt:94, shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/extensions/Json.kt:175, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — shared/core/ui/src/androidMain/kotlin/ru/aleshin/studyassistant/core/ui/views/VoiceInputButton.android.kt:67
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 log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
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 — 3 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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 21 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :androidApp:assembleDebug` exited 1: a45c7f4c64abc77460e1c00f541e9f960e3c7ed2538f1ede19eacd873ae'
at org.gradle.wrapper.Install.verifyDownloadChecksum(Install.java:165)
at org.gradle.wrapper.Install.access$800(Install.java:27)
at org…; runtime evidence skipped (launch chosen because androidApp/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
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.
D10 Test Quality — ~9073 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
D14 License Compliance — Not scored — this repository's 117 declared JVM dependency coordinate(s) were read from its 34 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 109 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/org/jetbrains/kotlin/kotlin-test/2.4.10/kotlin-test-2.4.10.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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.
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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D34 Knowledge Freshness — history too condensed to judge knowledge freshness
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
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)
DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — Not assessed, and this one is on us: 26 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift source, so there is no service whose uptime a failing dependency could take down
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
MethodTooLong: AiToolCallProcessor.activeCalls REDACTED:76— MethodTooLong — activeCalls runs 838 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 738 over it, 8.38× 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: AiToolCallProcessor.pendingMutations REDACTED:77— MethodTooLong — pendingMutations runs 837 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 737 over it, 8.37× 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: AiToolCallProcessor.isMutation REDACTED:78— MethodTooLong — isMutation runs 836 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 736 over it, 8.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: AiToolCallProcessor.confirmationPreview REDACTED:79— MethodTooLong — confirmationPreview runs 835 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 735 over it, 8.35× 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: AiToolCallProcessor.execute REDACTED:80— MethodTooLong — execute runs 834 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 734 over it, 8.34× 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: ScheduleImportHandler.updateStartOfDay shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:64— MethodTooLong — updateStartOfDay runs 492 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 392 over it, 4.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScheduleImportHandler.updateClassesDuration shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:70— MethodTooLong — updateClassesDuration runs 486 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 386 over it, 4.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AnalyticsReportCalculator.calculate shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/domain/calculators/AnalyticsReportCalculator.kt:62— MethodTooLong — calculate runs 481 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 381 over it, 4.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: ScheduleImportHandler.updateBreaksDuration shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:77— MethodTooLong — updateBreaksDuration runs 479 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 379 over it, 4.79× 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: ScheduleImportHandler.swapDays shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:84— MethodTooLong — swapDays runs 472 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 372 over it, 4.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: ScheduleImportHandler.mergeOrganizationPlaces shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:90— MethodTooLong — mergeOrganizationPlaces runs 466 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 366 over it, 4.66× 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: ShareSchedulesInteractor.linkOrganization shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:81— MethodTooLong — linkOrganization runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.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: ShareSchedulesInteractor.updateLinkedSubjects shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:88— MethodTooLong — updateLinkedSubjects runs 374 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 274 over it, 3.74× 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: ShareSchedulesInteractor.updateLinkedEmployees shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:95— MethodTooLong — updateLinkedEmployees runs 368 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 268 over it, 3.68× 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: ShareSchedulesInteractor.importShare shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:102— MethodTooLong — importShare runs 362 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 262 over it, 3.62× 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: WidgetInteractor.fetchSchedule widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:67— MethodTooLong — fetchSchedule runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.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: WidgetInteractor.fetchHomeworks widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:68— MethodTooLong — fetchHomeworks runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× 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: WidgetInteractor.fetchTodos widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:69— MethodTooLong — fetchTodos runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.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: WidgetInteractor.fetchGoals widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:70— MethodTooLong — fetchGoals runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× 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: WidgetInteractor.fetchDisplaySettings widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:71— MethodTooLong — fetchDisplaySettings runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WidgetInteractor.setTodoDone widget/src/commonMain/kotlin/ru/aleshin/studyassistant/widget/domain/interactors/WidgetInteractor.kt:72— MethodTooLong — setTodoDone runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× 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: ImportClassEditorSheetKt.ImportClassEditorSheet shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:111— MethodTooLong — ImportClassEditorSheet runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GoalsInteractor.addGoal shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:52— MethodTooLong — addGoal runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GoalsInteractor.fetchGoalsByDate shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:53— MethodTooLong — fetchGoalsByDate runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GoalsInteractor.fetchGoalsProgressByTimeRange shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:54— MethodTooLong — fetchGoalsProgressByTimeRange runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× 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.
Duplicated block (7 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.kt:145— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.kt:145-151 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/validation/ScheduleImportValidator.kt:96-102 — 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: `LocalTime` names `java.time.LocalTime` in one and `kotlinx.datetime.LocalTime` 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 (7 lines × 2) shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:67— shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:67-73 | shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/StartClassesReminderManagerImpl.ios.kt:62-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.
Duplicated block (7 lines × 2) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/goals/GoalDataMapper.kt:74— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/goals/GoalDataMapper.kt:74-80 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/goals/GoalShortDataMapper.kt:33-39 — 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 `shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/goals/GoalDataMapper.kt:74` 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:493— REDACTED:493-499 | REDACTED:581-587 — 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) REDACTED:1131— REDACTED:1131-1137 | REDACTED:1141-1147 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:159— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:159-170 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:215-221 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:159` 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, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:157` calls `padding` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:213` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:409— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:409-415 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:416-422 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/models/importing/ImportFastEditDurationMath.kt:84— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/models/importing/ImportFastEditDurationMath.kt:84-90 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:471-477 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/models/importing/ImportFastEditDurationMath.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. 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) shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:233— shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:233-239 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:314-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 `shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:233` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/mappers/BaseScheduleUiMapper.kt:27— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/mappers/BaseScheduleUiMapper.kt:27-33 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/mappers/CustomScheduleUiMapper.kt:27-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt:42— shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt:42-48 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/models/InputFileUi.kt:46-52 — before extracting anything, compare `shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/models/InputFileUi.kt` as WHOLE FILES: 87% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseScheduleInteractor.kt:49— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseScheduleInteractor.kt:49-55 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/CustomScheduleInteractor.kt:87-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.
Duplicated block (7 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:490— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:490-496 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeSubjectView.kt:118-124 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:490` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.kt:143— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.kt:143-149 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedSubjectsView.kt:150-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.kt:143` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedOrganizationView.kt:263— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedOrganizationView.kt:263-269 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeContactInfoView.kt:99-105 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedOrganizationView.kt: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 (7 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekConfig.kt:76— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekConfig.kt:76-82 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterConfig.kt:83-89 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekConfig.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterConfig.kt` as WHOLE FILES: 86% 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.
Duplicated block (11 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:101— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:101-111 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:96-106 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:101` 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) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiCompletionHandler.kt:56— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiCompletionHandler.kt:56-66 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/ScheduleImportRepositoryImpl.kt:56-66 — 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 `shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiCompletionHandler.kt:56` 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) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:51— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:51-61 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsInsightsSection.kt:81-91 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:51` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:338— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:338-348 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:347-357 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:338` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:90— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:90-100 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:172-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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:171` calls `painterResource` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:89` 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 × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:66— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:66-76 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:76-86 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:66` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:78— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:78-88 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationNameInfoField.kt:75-85 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:78` 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, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:91` calls `MutableInteractionSource` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationNameInfoField.kt:89` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/CityInfoField.kt:75— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/CityInfoField.kt:75-85 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/UsernameInfoField.kt:74-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/CityInfoField.kt:75` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:285— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:285-295 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:396-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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:285` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/ClassDetailsUiMapper.kt:29— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/ClassDetailsUiMapper.kt:29-39 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/ClassUiMapper.kt:32-42 — 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:204— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:204-214 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:147-157 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:204` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:232— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:232-242 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:157-167 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:232` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:286— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:286-296 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/HomeworksInteractor.kt:278-289 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:286` 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) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/HomeworkShareRepositoryImpl.kt:49— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/HomeworkShareRepositoryImpl.kt:49-59 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/ScheduleShareRepositoryImpl.kt:52-62 — 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 `shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/HomeworkShareRepositoryImpl.kt:49` 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.
Hotspot: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:69— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in ImportComposeStore.handleEvent at line 69. 5 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.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: shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt:52— shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AssistantComposeStore.handleEvent at line 52. 2 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.kt:54— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in ShareComposeStore.handleEvent at line 54. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.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: shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.kt shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.kt:235— shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SetupContentKt.SetupPageInfoSection at line 235. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.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: shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.kt shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.kt:42— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in YandexRewardedAdHostKt.YandexRewardedAdHost at line 42. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.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: backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:54— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AiQuotaRepositoryImpl.reserve at line 54. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:314— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in OverviewTopSheetKt.OverviewTopSheetAnalysis at line 314. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.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: backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:57— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ScheduleExtractionService.extract at line 57. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.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: shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt:61— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in HomeworksComposeStore.handleEvent at line 61. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.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: shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/store/SetupComposeStore.kt shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/store/SetupComposeStore.kt:55— shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/store/SetupComposeStore.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SetupComposeStore.handleEvent at line 55. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/store/SetupComposeStore.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: shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:507— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DailyHomeworksDetailsViewKt.ShortHomeworkViewContent at line 507. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.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: shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/mappers/BackendShareErrorMapper.kt shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/mappers/BackendShareErrorMapper.kt:28— shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/mappers/BackendShareErrorMapper.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in BackendShareErrorMapperKt.mapBackendShareError at line 28. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/core/remote/src/commonMain/kotlin/ru/aleshin/studyassistant/core/remote/mappers/BackendShareErrorMapper.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: backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.kt backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.kt:58— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in AiCompletionService.complete at line 58. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.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.
Duplicated block (8 lines × 2) androidApp/src/main/java/ru/aleshin/studyassistant/application/StudyAssistantApp.kt:122— androidApp/src/main/java/ru/aleshin/studyassistant/application/StudyAssistantApp.kt:122-129 | shared/core/common/src/androidMain/kotlin/ru/aleshin/studyassistant/core/common/notifications/NotificationCreator.kt:183-190 — 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 (8 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:54— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:54-61 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt:60-67 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt` as WHOLE FILES: 94% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt:68` calls `contentHashCode`, `hashCode` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:62` 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) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:42— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:42-49 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:83-90 — 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 `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:42` 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) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:56— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:56-63 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:121-128 — 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 `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `Any` in one and `Any?` 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 (8 lines × 2) shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/WorkloadWarningWorker.kt:109— shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/WorkloadWarningWorker.kt:109-117 | shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/WorkloadWarningManagerImpl.ios.kt:99-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 `shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/WorkloadWarningWorker.kt:109` 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 lines × 2) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/OrganizationDataMapper.kt:58— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/OrganizationDataMapper.kt:58-65 | shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/organizations/OrganizationUiMapper.kt:59-66 — 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 `shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/OrganizationDataMapper.kt:58` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ScheduleImportInteractor.kt:237— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ScheduleImportInteractor.kt:237-244 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:316-323 — 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:337— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:337-344 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:231-238 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:337` 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) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/GeneralSettingsRepositoryImpl.kt:34— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/GeneralSettingsRepositoryImpl.kt:34-41 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/NotificationSettingsRepositoryImpl.kt:34-42 — 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) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:347— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:347-354 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:361-368 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:347` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/store/EmployeeComposeStore.kt:183— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/store/EmployeeComposeStore.kt:183-190 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/store/EmployeeComposeStore.kt:139-146 — 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. Note first that the copies are not typed on the same thing: `EmployeeAction` names `ru.aleshin.studyassistant.editor.impl.presentation.ui.employee.contract.EmployeeAction` in one and `ru.aleshin.studyassistant.info.impl.presentation.ui.employee.contract.EmployeeAction` 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 (8 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/store/TodoComposeStore.kt:134— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/store/TodoComposeStore.kt:134-141 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/store/TodoComposeStore.kt:103-110 — 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. Note first that the copies are not typed on the same thing: `TodoAction` names `ru.aleshin.studyassistant.editor.impl.presentation.ui.todo.contract.TodoAction` in one and `ru.aleshin.studyassistant.tasks.impl.presentation.ui.todos.contract.TodoAction` 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 (8 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:41— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:41-48 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt:44-51 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt` as WHOLE FILES: 94% 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredScheduleShare.kt:52` calls `contentEquals` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/domain/model/StoredHomeworkShare.kt:50` 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 × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:81— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:81-96 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsWorkloadSection.kt:195-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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsMetricView.kt:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsTopAppBar.kt:57— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsTopAppBar.kt:57-72 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsTopAppBar.kt:87-102 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/AnalyticsTopAppBar.kt:57` 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) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/layouts/AnalyticsExpandedLayout.kt:58— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/layouts/AnalyticsExpandedLayout.kt:58-73 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/layouts/AnalyticsExpandedLayout.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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/layouts/AnalyticsExpandedLayout.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 (16 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:167— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:167-182 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt:216-231 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:167` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:191— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:191-206 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt:240-255 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:191` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:189— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:189-204 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:324-339 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/OrganizationInfoField.kt:115— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/OrganizationInfoField.kt:115-130 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/common/OrganizationsPicker.kt:125-140 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/OrganizationInfoField.kt:115` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:307— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:307-322 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:312-327 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:137— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:137-152 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:241-256 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.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 after the matched lines, `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:258` calls `Spacer`, `weight` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:153` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedSubjectsView.kt:188— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedSubjectsView.kt:188-203 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/views/LinkDataSelectorDialogs.kt:80-95 — 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:342— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:342-357 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/HomeworksOverview.kt:242-257 — 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 (16 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/HomeworkSharingRoutes.kt:56— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/HomeworkSharingRoutes.kt:56-71 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/ScheduleSharingRoutes.kt:58-73 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/HomeworkSharingRoutes.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/ScheduleSharingRoutes.kt` as WHOLE FILES: 84% 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. 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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/api/HomeworkSharingRoutes.kt:56` 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) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:112— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:112-126 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt:135-149 — before extracting anything, compare `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt:133` calls `item` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:111` 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 (15 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsOrganizationsSection.kt:263— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsOrganizationsSection.kt:263-277 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsRegularitySection.kt:273-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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsOrganizationsSection.kt: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 (15 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:185— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:185-199 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleView.kt:219-233 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:185` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:344— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:344-358 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:350-364 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:344` 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 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:113— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:113-127 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:168-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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:113` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:167— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:167-181 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:236-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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.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.
Duplicated block (15 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:233— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:233-247 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:279-293 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:233` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:66— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:66-80 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:415-429 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:66` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.kt:124— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.kt:124-138 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedSubjectsView.kt:131-145 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedEmployeesView.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 (15 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:211— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:211-225 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/OverviewContent.kt:251-265 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:211` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:116— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:116-130 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:238-252 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:116` 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) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:94— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:94-105 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:161-172 — 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 `element` to `JsonElement): Any = when (element` in one and `JsonElement): Any? = when (element` 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 (12 lines × 2) shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt:29— shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt:29-40 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/models/InputFileUi.kt:33-44 — before extracting anything, compare `shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/models/InputFileUi.kt` as WHOLE FILES: 87% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204-215 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsOrganizationsSection.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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/common/EmployeeSubjectView.kt:48— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/common/EmployeeSubjectView.kt:48-59 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/common/EmployeeSubjectView.kt:80-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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/common/EmployeeSubjectView.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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:60— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:60-71 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt:60-71 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:123— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:123-134 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:177-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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:123` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:137— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:137-148 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:191-202 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:137` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:187— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:187-198 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:223-234 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:187` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/root/ScheduleContentProvider.kt:43— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/root/ScheduleContentProvider.kt:43-54 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/root/TasksContentProvider.kt:43-54 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/root/ScheduleContentProvider.kt:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Child` names `ru.aleshin.studyassistant.schedule.impl.presentation.ui.root.ScheduleFeatureComponent.Child` in one and `ru.aleshin.studyassistant.tasks.impl.presentation.ui.root.TasksFeatureComponent.Child` 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 (12 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:83— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:83-94 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:147-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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:83` 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) androidApp/src/github/java/ru/aleshin/studyassistant/application/BaseFlavorApplication.kt:34— androidApp/src/github/java/ru/aleshin/studyassistant/application/BaseFlavorApplication.kt:34-45 | androidApp/src/huawei/java/ru/aleshin/studyassistant/application/BaseFlavorApplication.kt:34-45 — before extracting anything, compare `androidApp/src/github/java/ru/aleshin/studyassistant/application/BaseFlavorApplication.kt` and `androidApp/src/huawei/java/ru/aleshin/studyassistant/application/BaseFlavorApplication.kt` as WHOLE FILES: 91% 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.
Duplicated block (10 lines × 2) shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:37— shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:37-46 | shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.kt:33-42 — before extracting anything, compare `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt` and `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.kt` as WHOLE FILES: 94% 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 `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:37` 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, `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:36` calls `mapToUi` and `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.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 (10 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204-213 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsSubjectsSection.kt:227-236 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:204` 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) shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:634— shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:634-643 | shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:644-653 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseScheduleInteractor.kt:83— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseScheduleInteractor.kt:83-92 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/CustomScheduleInteractor.kt:221-230 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/models/classes/FastEditDurationMath.kt:48— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/models/classes/FastEditDurationMath.kt:48-57 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/models/importing/ImportFastEditDurationMath.kt:51-60 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/models/classes/FastEditDurationMath.kt:48` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:266— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:266-275 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:344-353 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:266` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:288— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:288-297 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:292-301 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:288` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:179— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:179-188 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeSubjectView.kt:68-77 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:179` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:206— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:206-215 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:219-228 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:206` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/AllHomeworksExecutionAnalysisView.kt:109— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/AllHomeworksExecutionAnalysisView.kt:109-118 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/AllHomeworksExecutionAnalysisView.kt:163-172 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/AllHomeworksExecutionAnalysisView.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 (10 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:203— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:203-212 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:380-389 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:203` 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) shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:74— shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:74-86 | shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.kt:51-63 — before extracting anything, compare `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt` and `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.kt` as WHOLE FILES: 94% 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 `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:74` 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, `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:73` calls `mapToDomain` and `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.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 (13 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:343— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:343-355 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:425-437 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:343` 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) REDACTED:379— REDACTED:379-391 | REDACTED:537-549 — 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:379` 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) shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantWorkProcessor.kt:168— shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantWorkProcessor.kt:168-180 | shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantWorkProcessor.kt:184-196 — 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 `shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantWorkProcessor.kt:168` 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 × 2) shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:342— shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:342-354 | shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:539-551 — 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 `shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantChatBody.kt:342` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:147— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:147-159 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:131-143 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:147` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:187— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:187-200 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:168-180 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:187` 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 (13 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:243— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:243-255 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/views/ShortEmployeeView.kt:86-98 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:243` 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 × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:93— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:93-105 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:122-134 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.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 (13 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:521— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:521-533 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:464-476 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:521` 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: AiToolCallProcessor (74-1194). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: views/TextFields.kt shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 138 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: views/ImportStatusLayouts.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportStatusLayouts.kt— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 66 over it, 1.13× 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: overview/OverviewContent.kt shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/OverviewContent.kt— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 66 over it, 1.13× 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: common/ScheduleImportHandler.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ScheduleImportHandler (40-689). The bar is 500 significant lines; this is 33 over it, 1.07× 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: calculators/AnalyticsReportCalculator.kt shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/domain/calculators/AnalyticsReportCalculator.kt— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: AnalyticsReportCalculator (60-672). The bar is 500 significant lines; this is 23 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: views/DailyGoalsView.kt shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyGoalsView.kt— FileTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 21 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: views/DailyHomeworksDetailsView.kt shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt— FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 15 over it, 1.03× 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.
Duplicated block (18 lines × 2) shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:129— shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:129-146 | shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/StartClassesReminderManagerImpl.ios.kt:122-139 — 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 `shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:129` 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) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/theme/tokens/StudyAssistantColors.kt:106— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/theme/tokens/StudyAssistantColors.kt:106-123 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/theme/tokens/StudyAssistantColors.kt:142-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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/theme/tokens/StudyAssistantColors.kt:106` 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 (18 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:141— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:141-158 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:203-220 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.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.
Duplicated block (18 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:198— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:198-215 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:106-123 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:198` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:249— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:249-266 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:252-269 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:249` calls `Composable` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:246` 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 (18 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:399— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:399-416 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.kt:432-449 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/WeekScheduleBottomSheet.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 (18 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:68— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:68-85 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/SubjectsSearchTopBar.kt:68-85 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/SubjectsSearchTopBar.kt` as WHOLE FILES: 96% 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. 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:68` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:174— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:174-191 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportTeacherEditorSheet.kt:120-137 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportTeacherEditorSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:174` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:385— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:385-398 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:122-135 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:385` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:192— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:192-205 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:198-211 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:192` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:177— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:177-190 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsLayout.kt:153-166 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeLayout.kt:177` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:302— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:302-315 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:413-426 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:302` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:189— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:189-202 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:132-145 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:189` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:123— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:123-136 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/ShareLayout.kt:150-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:123` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: `Res` names `ru.aleshin.studyassistant.schedule.impl.resources.Res` in one and `ru.aleshin.studyassistant.tasks.impl.resources.Res` 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 (14 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:321— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:321-334 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/ShareLayout.kt:295-308 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareStatusLayouts.kt:321` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:248— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:248-261 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:364-377 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:245` calls `mutableStateOf` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:363` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64-72 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:129-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. Read the line range as the matched WINDOW rather than a finished unit: at `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64` 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 `value` to `Any` in one and `Any?` 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 (9 lines × 2) shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/EndClassesReminderManagerImpl.ios.kt:101— shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/EndClassesReminderManagerImpl.ios.kt:101-109 | shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/StartClassesReminderManagerImpl.ios.kt:152-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. 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) REDACTED:271— REDACTED:271-279 | REDACTED:394-402 — 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:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:437— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:437-445 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:460-468 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:437` 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/store/SubjectsWorkProcessor.kt:86— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/store/SubjectsWorkProcessor.kt:86-99 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/store/SubjectsWorkProcessor.kt:112-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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/store/SubjectsWorkProcessor.kt:86` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/store/OverviewComposeStore.kt:125— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/store/OverviewComposeStore.kt:125-133 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/store/OverviewComposeStore.kt:197-205 — 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: `OverviewEvent` names `ru.aleshin.studyassistant.schedule.impl.presentation.ui.overview.contract.OverviewEvent` in one and `ru.aleshin.studyassistant.tasks.impl.presentation.ui.overview.contract.OverviewEvent` 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 (9 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:290— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:290-298 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/HomeworksOverview.kt:182-190 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalBottomSheet.kt:303— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalBottomSheet.kt:303-311 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:310-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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalBottomSheet.kt:303` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) shared/features/profile/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/profile/impl/presentation/ui/views/ProfileExpandedHeader.kt:68— shared/features/profile/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/profile/impl/presentation/ui/views/ProfileExpandedHeader.kt:68-73 | shared/features/profile/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/profile/impl/presentation/ui/views/ProfileInfoSection.kt:66-70 — 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 `shared/features/profile/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/profile/impl/presentation/ui/views/ProfileExpandedHeader.kt:68` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/BaseScheduleRepositoryImpl.kt:40— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/BaseScheduleRepositoryImpl.kt:40-44 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/CustomScheduleRepositoryImpl.kt:39-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:88— shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:88-92 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:79-83 — before extracting anything, compare `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt` and `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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 `item` to `BaseScheduleEntity` in one and `CustomScheduleEntity` 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 (5 lines × 2) shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:147— shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:147-151 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:111-115 — before extracting anything, compare `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt` and `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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 `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:147` 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, `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:117` calls `deleteSchedulesByIds`, `deleteSchedulesById` and `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:153` 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) shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/models/users/EmployeeDetailsUi.kt:50— shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/models/users/EmployeeDetailsUi.kt:50-54 | shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/models/users/EmployeeUi.kt:48-52 — before extracting anything, compare `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/models/users/EmployeeDetailsUi.kt` and `shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/models/users/EmployeeUi.kt` as WHOLE FILES: 93% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/HomeworkInteractor.kt:39— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/HomeworkInteractor.kt:39-43 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/HomeworksInteractor.kt:203-207 — 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) REDACTED:937— REDACTED:937-941 | REDACTED:968-972 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:942` calls `fetchAllSubjectsByOrganization`, `first` and `REDACTED:973` 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) shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:190— shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:190-194 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:215-219 — 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 before the matched lines, `shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:189` calls `weight`, `fillMaxHeight`, `verticalScroll` and `shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/EmployeeProfileContent.kt:214` 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.
Repeated repair: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt:31— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.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 3 (its worst body is ImportLayoutKt.ImportLayout at line 31), 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(backend): cap extraction reasoning at 4096 tokens and raise request timeout to 180s”; “fix: schedule import weekdays, per-day fast-edit and swap days”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: schedule import screen”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.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: shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiConversationHandler.kt shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiConversationHandler.kt:51— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiConversationHandler.kt changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Base.retryLastMessage at line 51), 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: date time bug & chat logic”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: bugs in ui, business logic and backend”; “fix: minor bugs”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/AiConversationHandler.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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportCompactLayout.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportCompactLayout.kt:38— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportCompactLayout.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is ImportCompactLayoutKt.ImportCompactLayout at line 38), 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(backend): cap extraction reasoning at 4096 tokens and raise request timeout to 180s”; “fix: schedule import weekdays, per-day fast-edit and swap days”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: minor bugs”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportCompactLayout.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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportExpandedLayout.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportExpandedLayout.kt:39— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportExpandedLayout.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is ImportExpandedLayoutKt.ImportExpandedLayout at line 39), 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(backend): cap extraction reasoning at 4096 tokens and raise request timeout to 180s”; “fix: schedule import weekdays, per-day fast-edit and swap days”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: minor bugs”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/layouts/ImportExpandedLayout.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: shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportDayColumn.kt shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportDayColumn.kt:54— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportDayColumn.kt changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is ImportDayColumnKt.ImportDayColumn at line 54), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: schedule import weekdays, per-day fast-edit and swap days”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: minor bugs”; “fix: schedule import screen”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportDayColumn.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: shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/ai/AiAssistantMessage.kt shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/ai/AiAssistantMessage.kt:210— shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/ai/AiAssistantMessage.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is AiAssistantMessageKt.lastConfirmedTurnEndIndex at line 210), 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: date time bug & chat logic”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: bugs in ui, business logic and backend”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/ai/AiAssistantMessage.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: backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.kt backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.kt:103— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.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 DeepSeekScheduleExtractionMapper.parseClocks at line 103), 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(backend): mapping schedule”; “fix: AI chat recovery, schedule import, editor and banner bugs”; “fix: bugs in ui, business logic and backend”. 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-06-08..2026-09-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-08 01:52:50 +03:00' --until='2026-09-06 01:52:50 +03:00' --full-history --no-merges -- backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/deepseek/mappers/DeepSeekScheduleExtractionMapper.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.
Duplicated block (17 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:70— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:70-86 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.kt:77-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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:70` 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) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:94— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:94-110 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/services/AiCompletionService.kt:105-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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/services/ScheduleExtractionService.kt:94` 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) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:308— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:308-324 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:432-448 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:107— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:107-123 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsOrganizationsSection.kt:97-113 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:107` 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) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:180— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:180-196 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsTargetSection.kt:160-176 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:180` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:289— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:289-305 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:298-314 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:289` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:144— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:144-160 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt:149-165 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:55— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:55-72 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:81-92 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:116-137 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:148-159 — 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) shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/goals/DailyGoalsLocalDataSource.kt:134— shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/goals/DailyGoalsLocalDataSource.kt:134-201 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:161-212 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:129-176 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/tasks/HomeworksLocalDataSource.kt:129-172 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt:48— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt:48-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeTopBar.kt:48-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationTopBar.kt:48-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/views/SubjectTopBar.kt:48-77 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:176— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:176-298 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:310-427 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:91-169 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:88-153 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:61— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:61-103 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoBottomActions.kt:61-103 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportBottomActionBar.kt:60-127 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareBottomActionBar.kt:60-124 — 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:115— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:115-135 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleView.kt:91-131 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/views/CommonScheduleView.kt:116-156 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedScheduleView.kt:81-121 — 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.
Duplicated block (21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:261— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:261-281 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationsInfoFields.kt:138-158 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:261` 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 (21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:218— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:218-238 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:126-146 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.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.
Duplicated block (21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:282— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:282-302 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:383-403 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:282` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:295— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:295-315 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:387-407 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:295` 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, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:385` calls `HorizontalDivider` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:294` 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 (21 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/views/CommonScheduleView.kt:119— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/views/CommonScheduleView.kt:119-139 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedScheduleView.kt:84-104 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/views/CommonScheduleView.kt:119` 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 (21 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt:56— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt:56-76 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt:78-98 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportLayout.kt:56` 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 (27 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:251— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:251-277 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:375-401 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 (27 lines × 2) shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:186— shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:186-212 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:150-176 — before extracting anything, compare `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt` and `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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 `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:186` 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 (27 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/Dialog.kt:63— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/Dialog.kt:63-89 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/Dialog.kt:148-174 — 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 (27 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:75— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:75-101 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt:77-103 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.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.
Duplicated block (27 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:275— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:275-301 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:368-394 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.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 (20 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:136— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:136-155 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt:185-204 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:136` 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 (20 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:174— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:174-193 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.kt:143-162 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.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 (20 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:636— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:636-655 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:547-566 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalBottomSheet.kt:275— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalBottomSheet.kt:275-294 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:290-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. 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 (20 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:286— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:286-305 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:458-477 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
Swallowed exception (caught, then discarded) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/api/validation/ScheduleImageGuard.kt:59— `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) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/ScheduleImageNormalizer.kt:94— `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) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/extensions/Json.kt:175— `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) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/FunctionArgumentsHandler.kt:35— `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) shared/core/ui/src/androidMain/kotlin/ru/aleshin/studyassistant/core/ui/views/ShareQrCode.android.kt:192— `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.
Duplicated block (17–18 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekAiCompletionGateway.kt:213— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekAiCompletionGateway.kt:213-230 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterScheduleExtractionGateway.kt:313-329 — 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 (17–18 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:125— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:125-142 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:200-216 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:125` 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 (17–18 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:267— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:267-284 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt:159-175 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:267` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:240— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:240-256 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:267-284 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.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.
Duplicated block (15–16 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/BottomNavBar.kt:98— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/BottomNavBar.kt:98-112 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/SideNavRail.kt:117-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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/BottomNavBar.kt:98` 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, `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/SideNavRail.kt:133` calls `fillMaxWidth` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/uikit/navigation/BottomNavBar.kt:113` 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–16 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/TodoContent.kt:197— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/TodoContent.kt:197-211 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/TodoContent.kt:238-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/TodoContent.kt:238` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/ShareContent.kt:138— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/ShareContent.kt:138-153 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/ShareContent.kt:99-113 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/ShareContent.kt:138` 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 first that the copies are not typed on the same thing: `Res` names `ru.aleshin.studyassistant.schedule.impl.resources.Res` in one and `ru.aleshin.studyassistant.tasks.impl.resources.Res` 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 (15–16 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:67— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:67-81 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.kt:130-145 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/store/ShareWorkProcessor.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 × 3) shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.kt:108— shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.kt:108-118 | shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:161-171 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/ScheduleInteractor.kt:57-67 — 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 `shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.kt:108` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:127— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:127-137 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:202-212 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:351-361 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:126— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:126-136 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/LinkedSubjectsView.kt:191-201 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/views/LinkDataSelectorDialogs.kt:83-93 — 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 (11 lines × 3) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:80— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:80-90 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:202-212 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:321-331 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:80` 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.
ClassTooLong: AiToolCallProcessor REDACTED:74— ClassTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 439 over it, 2.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: ScheduleImportHandler shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:40— ClassTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 115 over it, 1.29× 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: AnalyticsReportCalculator shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/domain/calculators/AnalyticsReportCalculator.kt:60— ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 82 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:116— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:116-163 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:191-238 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:266-313 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:342-395 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:424-477 — 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) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BirthdayDatePicker.kt:52— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BirthdayDatePicker.kt:52-93 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/LinkedClassInfoField.kt:355-397 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoDeadlineInfoFields.kt:149-197 | shared/features/settings/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/settings/impl/presentation/ui/calendar/views/HolidaysView.kt:490-530 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyGoalsView.kt:664-699 — 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) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:58— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:58-144 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt:58-143 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:105-253 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/OverviewContent.kt:123-288 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/TodoContent.kt:72-136 — 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.
Duplicated block (26 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:160— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:160-185 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:222-247 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:160` 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 (26 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:102— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:102-127 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:452-477 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material.Icon` in one and `androidx.compose.material3.Icon` 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 (26 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt:204— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt:204-229 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/store/OverviewComposeStore.kt:213-238 — 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) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:283— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:283-305 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:407-429 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 (23 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:210— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:210-232 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt:259-281 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 75 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:210` 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:184— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:184-206 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/HomeworkTasksChart.kt:135-157 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:184` 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 (22 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:212— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:212-233 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:287-308 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:212` 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 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:365— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:365-386 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:470-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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.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 (22 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsLayout.kt:121— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsLayout.kt:121-142 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsLayout.kt:197-218 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsLayout.kt:121` 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 × 3) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:143— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:143-162 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:218-237 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:293-312 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:143` 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 (20 lines × 3) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:383— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:383-402 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt:176-195 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:390-409 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material.Icon` in one and `androidx.compose.material3.Icon` 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 (20 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:139— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:139-158 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:97-116 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportTeacherEditorSheet.kt:75-94 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/EndClassesReminderManagerImpl.ios.kt:53— shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/EndClassesReminderManagerImpl.ios.kt:53-71 | shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/StartClassesReminderManagerImpl.ios.kt:69-87 — 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 `shared/core/data/src/iosMain/kotlin/ru/aleshin/studyassistant/core/data/managers/reminders/EndClassesReminderManagerImpl.ios.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.
Duplicated block (19 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:366— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:366-384 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:370-388 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:366` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:296— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:296-314 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt:189-207 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:296` 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) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:81— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:81-86 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:148-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 `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:81` 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 (6 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/FailuresMapper.kt:52— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/FailuresMapper.kt:52-57 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/mappers/FailuresMapper.kt:38-43 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/mappers/FailuresMapper.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. Note first that the copies are not typed on the same thing: `Res` names `ru.aleshin.studyassistant.schedule.impl.resources.Res` in one and `ru.aleshin.studyassistant.tasks.impl.resources.Res` 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 (6 lines × 2) REDACTED:239— REDACTED:239-244 | REDACTED:269-274 — 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.
TooManyMethods: Base REDACTED:82— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Base shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:96— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (44 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:132— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:132-175 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:127-170 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (44 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:177— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:177-220 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:226-269 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.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 (34 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:361— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:361-394 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:443-476 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:361` 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 (34 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:191— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:191-224 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt:160-193 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (32 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:150— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:150-181 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt:119-150 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `Res` names `ru.aleshin.studyassistant.schedule.impl.resources.Res` in one and `ru.aleshin.studyassistant.tasks.impl.resources.Res` 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 (32 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:94— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:94-125 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/store/OrganizationWorkProcessor.kt:80-111 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:94` 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 (29 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/menu/AvatarView.kt:99— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/menu/AvatarView.kt:99-127 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/menu/AvatarView.kt:157-185 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/menu/AvatarView.kt:99` 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 × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:243— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:243-271 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/OrganizationContent.kt:342-370 — 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 (24 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:210— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:210-233 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:345-368 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:210` 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 (24 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:239— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt:239-262 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:411-434 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/ShareHomeworksBottomSheet.kt: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.
Duplicated block (21 lines × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt:57— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt:57-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeTopBar.kt:57-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationTopBar.kt:57-77 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/views/SubjectTopBar.kt:57-77 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeTopBar.kt` as WHOLE FILES: 92% 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/ClassTopBar.kt:57` 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 × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:62— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:62-82 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoBottomActions.kt:62-82 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportBottomActionBar.kt:61-81 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareBottomActionBar.kt:61-81 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoBottomActions.kt` as WHOLE FILES: 97% 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. 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.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 (18–19 lines × 2) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:312— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:312-330 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsSubjectsSection.kt:313-330 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/sections/AnalyticsEmployeesSection.kt:312` 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 (18–19 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/views/ShortSubjectView.kt:134— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/views/ShortSubjectView.kt:134-151 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:285-303 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/views/ShortSubjectView.kt:134` 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 (18 lines × 3) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:117— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:117-134 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt:116-133 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/TodoContent.kt:109-126 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.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.
Duplicated block (18 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:289— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:289-306 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:382-399 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt:182-199 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:289` 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 × 3) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:359— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:359-373 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt:117-131 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:366-380 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:359` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:263— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:263-277 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:175-189 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportTeacherEditorSheet.kt:121-135 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt: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 (14–15 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:106— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:106-120 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.kt:91-104 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:106` 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) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:582— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:582-595 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:523-537 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:523` 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) androidApp/src/github/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt:38— androidApp/src/github/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt:38-49 | androidApp/src/huawei/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt:38-49 | androidApp/src/rustore/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt:38-49 — before extracting anything, compare `androidApp/src/github/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt` and `androidApp/src/huawei/java/ru/aleshin/studyassistant/data/AnalyticsServiceImpl.kt` as WHOLE FILES: 100% 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. 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 × 3) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:487— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:487-499 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:329-340 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:453-464 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:487` 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–12 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:130— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:130-141 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:185-195 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:130` 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–12 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:327— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:327-338 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:353-363 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:327` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/EmailInfoFields.kt:60— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/EmailInfoFields.kt:60-69 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationsInfoFields.kt:58-67 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/PhoneInfoFields.kt:56-65 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/WebInfoFields.kt:60-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/EmailInfoFields.kt:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:224— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:224-233 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:359-368 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:150-159 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:134-143 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationInfoField.kt:224` 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) shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/MediatedOrganizationDataMapper.kt:55— shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/MediatedOrganizationDataMapper.kt:55-59 | shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/mappers/organizations/OrganizationDataMapper.kt:58-62 | shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/organizations/OrganizationUiMapper.kt:59-63 — 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 (5 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:654— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:654-658 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportTimeNormalizer.kt:282-286 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditBar.kt:203-207 — 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. 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.
ImportComposeStore.handleEvent (cyclomatic 49) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:69— ImportComposeStore.handleEvent has cyclomatic complexity 49 (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.
OverviewComposeStore.handleEvent (cyclomatic 29) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/store/OverviewComposeStore.kt:59— OverviewComposeStore.handleEvent has cyclomatic complexity 29 (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.
OverviewTopSheetKt.OverviewTopSheetAnalysis (cyclomatic 24) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:314— OverviewTopSheetKt.OverviewTopSheetAnalysis 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.
ShareComposeStore.handleEvent (cyclomatic 23) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareComposeStore.kt:54— ShareComposeStore.handleEvent 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.
AssistantComposeStore.handleEvent (cyclomatic 23) shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt:52— AssistantComposeStore.handleEvent has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Base.updateClass (cyclomatic 22) REDACTED:526— Base.updateClass 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. This is NOT this file's highest cyclomatic complexity: Base.execute (cyclomatic 28) 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.
HomeworksComposeStore.handleEvent (cyclomatic 21) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt:61— HomeworksComposeStore.handleEvent has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OpenRouterScheduleExtractionGateway.extractWithinDeadline (cyclomatic 21) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterScheduleExtractionGateway.kt:95— OpenRouterScheduleExtractionGateway.extractWithinDeadline 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.
SetupComposeStore.handleEvent (cyclomatic 20) shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/store/SetupComposeStore.kt:55— SetupComposeStore.handleEvent 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.
YandexRewardedAdHostKt.YandexRewardedAdHost (cyclomatic 20) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.kt:42— YandexRewardedAdHostKt.YandexRewardedAdHost 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.
ClassComposeStore.handleEvent (cyclomatic 19) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/store/ClassComposeStore.kt:52— ClassComposeStore.handleEvent 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.
Base.createNotify (cyclomatic 19) shared/core/common/src/androidMain/kotlin/ru/aleshin/studyassistant/core/common/notifications/NotificationCreator.kt:94— Base.createNotify 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.
DeepSeekAiCompletionGateway.completeWithinDeadline (cyclomatic 18) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekAiCompletionGateway.kt:81— DeepSeekAiCompletionGateway.completeWithinDeadline 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.
DeepSeekMapper.mapResponse (cyclomatic 18) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/mappers/DeepSeekMapper.kt:99— DeepSeekMapper.mapResponse 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.
DailyHomeworksDetailsViewKt.ShortHomeworkViewContent (cyclomatic 17) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:507— DailyHomeworksDetailsViewKt.ShortHomeworkViewContent 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.
OverviewComposeStore.handleEvent (cyclomatic 17) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/store/OverviewComposeStore.kt:59— OverviewComposeStore.handleEvent 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.
SetupContentKt.SetupPageInfoSection (cyclomatic 17) shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.kt:235— SetupContentKt.SetupPageInfoSection 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.
AiCompletionRequestValidator.validate (cyclomatic 17) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/api/validation/AiCompletionRequestValidator.kt:39— AiCompletionRequestValidator.validate 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.
DetailsComposeStore.handleEvent (cyclomatic 16) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/store/DetailsComposeStore.kt:60— DetailsComposeStore.handleEvent 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.
Base.isOverlay (cyclomatic 16) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/managers/TimeOverlayManager.kt:30— Base.isOverlay 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.
AiQuotaRepositoryImpl.reserve (cyclomatic 16) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:54— AiQuotaRepositoryImpl.reserve 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.
OverviewTopSheetKt.OverviewTopSheetAnalysis (cognitive 42) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:314— OverviewTopSheetKt.OverviewTopSheetAnalysis has cognitive complexity 42 (threshold 15). Drivers by points: if/else 34 (37 pts), match/switch 2 (4 pts), boolean chains 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.
ImportComposeStore.handleEvent (cognitive 39) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/store/ImportComposeStore.kt:69— ImportComposeStore.handleEvent has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 6, match/switch 2 (3 pts) (nesting depth added 16). 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.
Base.fetchGoalsByDate (cognitive 27) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/GoalsInteractor.kt:87— Base.fetchGoalsByDate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
YandexRewardedAdHostKt.YandexRewardedAdHost (cognitive 26) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/ads/YandexRewardedAdHost.kt:42— YandexRewardedAdHostKt.YandexRewardedAdHost has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20 (23 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.
SetupContentKt.SetupPageInfoSection (cognitive 25) shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/SetupContent.kt:235— SetupContentKt.SetupPageInfoSection has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 3 (10 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OverviewClassesSectionKt.OverviewClassesSection (cognitive 23) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewClassesSection.kt:74— OverviewClassesSectionKt.OverviewClassesSection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 2 (nesting depth added 12). 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.
Base.createNotify (cognitive 23) shared/core/common/src/androidMain/kotlin/ru/aleshin/studyassistant/core/common/notifications/NotificationCreator.kt:94— Base.createNotify has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (20 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.
AiQuotaRepositoryImpl.reserve (cognitive 23) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:54— AiQuotaRepositoryImpl.reserve has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 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.
TodoViewItemKt.TodoViewFooter (cognitive 22) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/TodoViewItem.kt:207— TodoViewItemKt.TodoViewFooter has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 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.
Base.updateClass (cognitive 22) REDACTED:526— Base.updateClass has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, boolean chains 9. 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.
TextFieldsKt.ClickableInfoTextField (cognitive 22) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:480— TextFieldsKt.ClickableInfoTextField has cognitive complexity 22 (threshold 15). Drivers by points: if/else 19 (21 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.
OpenRouterScheduleExtractionGateway.extractWithinDeadline (cognitive 22) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterScheduleExtractionGateway.kt:95— OpenRouterScheduleExtractionGateway.extractWithinDeadline has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), error handling 3, boolean chains 2, 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.
DailyHomeworksDetailsViewKt.ShortHomeworkViewContent (cognitive 20) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:507— DailyHomeworksDetailsViewKt.ShortHomeworkViewContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrganizationPageInfoKt.OrganizationPageInfo (cognitive 20) shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/setup/views/OrganizationPageInfo.kt:77— OrganizationPageInfoKt.OrganizationPageInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (20 pts) (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.
TextFieldsKt.ClickableTextField (cognitive 20) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:603— TextFieldsKt.ClickableTextField has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17 (19 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.
MainActivityKt.createAdsConfiguration (cognitive 20) androidApp/src/main/java/ru/aleshin/studyassistant/presentation/ui/MainActivity.kt:113— MainActivityKt.createAdsConfiguration has cognitive complexity 20 (threshold 15). Drivers by points: if/else 20. 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.
DailyHomeworksDetailsViewKt.DailyHomeworksDetailsView (cognitive 18) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:116— DailyHomeworksDetailsViewKt.DailyHomeworksDetailsView has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 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.
Base.isOverlay (cognitive 18) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/managers/TimeOverlayManager.kt:30— Base.isOverlay has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeepSeekAiCompletionGateway.completeWithinDeadline (cognitive 18) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekAiCompletionGateway.kt:81— DeepSeekAiCompletionGateway.completeWithinDeadline has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 3, 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.
AssistantComposeStore.handleEvent (cognitive 17) shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/store/AssistantComposeStore.kt:52— AssistantComposeStore.handleEvent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 7). 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.
AnalyticsContentKt.AnalyticsContent (cognitive 17) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/AnalyticsContent.kt:91— AnalyticsContentKt.AnalyticsContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 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.
AiAssistantMessageKt.lastConfirmedTurnEndIndex (cognitive 17) shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/ai/AiAssistantMessage.kt:210— AiAssistantMessageKt.lastConfirmedTurnEndIndex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DailyHomeworksViewKt.DailyHomeworksView (cognitive 16) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:104— DailyHomeworksViewKt.DailyHomeworksView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (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.
ImportContentKt.ImportContent (cognitive 16) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/ImportContent.kt:74— ImportContentKt.ImportContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, 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.
AnalyticsGridKt.analyticsDetailsItems (cognitive 16) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/views/layouts/AnalyticsGrid.kt:144— AnalyticsGridKt.analyticsDetailsItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 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.
TabIndicatorOffsetKt.pagerTabIndicatorOffset (cognitive 16) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TabIndicatorOffset.kt:39— TabIndicatorOffsetKt.pagerTabIndicatorOffset has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 2 (4 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.
D22 · Internal API Consistency· Inconsistent naming for the same domain concept (entity identifier) across feature APIs. One uses 'employeeId' and the other uses 'homeworkId', while both are nullable String identifiers for navigation targets. · ×1
Inconsistent naming for the same domain concept (entity identifier) across feature APIs. One uses 'employeeId' and the other uses 'homeworkId', while both are nullable String identifiers for navigation targets. — Standardize on a generic 'targetId' or 'id' property name in a shared navigation contract interface, or ensure consistent domain-specific naming if the types are strictly separated. (signatures: ru.aleshin.studyassistant.users.api.UsersOutput.NavigateToEmployeeEditor.employeeId: String? | ru.aleshin.studyassistant.tasks.api.TasksOutput.NavigateToEditor.Homework.homeworkId: String?)
D4 · Code Duplication· Near-duplicate member family (3 members, 45 shared lines) · ×1
Near-duplicate member family (3 members, 45 shared lines) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:79— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:79-188 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:201-310 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:320-402 — These 3 members are variants of one another: a block of 45 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
Near-duplicate member pair (91 shared lines) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:123— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:123-394 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:92-245 — These two members are variants of one another: 91 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 (85 shared lines) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:97— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:97-185 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:160-247 — These two members are variants of one another: 85 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 (75 shared lines) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:90— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/SubjectSelectorBottomSheet.kt:90-232 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/TeacherInfoField.kt:131-281 — These two members are variants of one another: 75 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 (47 shared lines) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:284— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:284-386 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:395-491 — These two members are variants of one another: 47 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· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:390— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:390-457 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:339-403 — 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· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:68— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:68-161 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/EmailInfoFields.kt:59-177 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationsInfoFields.kt:57-175 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/PhoneInfoFields.kt:55-173 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:68-150 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/WebInfoFields.kt:59-177 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:70-188 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/WorkTimeInfoField.kt:64-135 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/LinkedClassInfoField.kt:104-155 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationNameInfoField.kt:68-154 — These 10 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 10 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 10 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:65— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:65-100 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:109-155 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:164-212 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopBar.kt:138-203 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:85-151 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:75-110 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:119-164 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:173-220 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSwapDaysDialog.kt:71-112 — These 9 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 9 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 9 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) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:55— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:55-65 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:70-80 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:86-96 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:102-112 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:118-128 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:134-144 — 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.
Duplicated block (55 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:525— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:525-579 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:633-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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:525` 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 (51 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:391— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:391-441 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:340-390 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:391` 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 (46 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:535— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:535-580 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:477-522 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:535` 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 (43 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:87— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:87-129 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/SubjectsSearchTopBar.kt:87-129 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/SubjectsSearchTopBar.kt` as WHOLE FILES: 96% 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. 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/EmployeeSearchTopBar.kt:87` 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 (42 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:141— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:141-182 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt:164-205 — before extracting anything, compare `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:141` 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 (41–42 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:98— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:98-139 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:161-201 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 153 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/NumberedDurationView.kt:98` 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 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:228— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:228-265 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/EmployeeContent.kt:329-366 — 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 (36 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareCompactLayout.kt:94— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareCompactLayout.kt:94-129 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareExpandedLayout.kt:123-158 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareCompactLayout.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareExpandedLayout.kt` as WHOLE FILES: 89% 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. 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/layouts/ShareCompactLayout.kt:94` 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 (33–34 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:173— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:173-205 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt:176-209 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.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. 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 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:71— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:71-103 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoBottomActions.kt:71-103 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoBottomActions.kt` as WHOLE FILES: 97% 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. 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/HomeworkBottomActions.kt:71` 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 (31 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:81— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:81-111 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt:101-131 — before extracting anything, compare `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt` and `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseSelectorDialog.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 88 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BaseCheckedDialog.kt:81` 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 (30 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:358— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:358-387 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:410-439 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalView.kt:358` 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 (27–28 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:238— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:238-264 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/HomeworkTaskView.kt:183-210 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt:207-234 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:238` 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 (28 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:228— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:228-255 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/ClassContent.kt:316-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.
Duplicated block (17–27 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:127— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:127-153 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:226-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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/DailyScheduleContent.kt:127` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/HomeworkContent.kt:224— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/HomeworkContent.kt:224-248 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/HomeworkContent.kt:303-327 — 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 (21–22 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:100— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:100-121 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt:94-114 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/views/DetailsSubjectView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/views/DetailsEmployeeView.kt:100` 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 (21 lines × 3) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:168— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:168-188 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:290-310 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:382-402 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:168` 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–21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:208— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:208-226 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt:120-140 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/CommonShortClassView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 99 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.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.
Duplicated block (20–21 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:175— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:175-195 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt:527-546 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportNumberedDurations.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/TimeDurationMenu.kt:175` 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 first that the copies are not typed on the same thing: `Icon` names `androidx.compose.material.Icon` in one and `androidx.compose.material3.Icon` 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 (17–21 lines × 2) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:131— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:131-147 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:116-136 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.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.
Duplicated block (19–20 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:225— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:225-244 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:289-307 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:225` 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–19 lines × 4) shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/goals/DailyGoalsLocalDataSource.kt:154— shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/goals/DailyGoalsLocalDataSource.kt:154-170 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt:172-190 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt:140-154 | shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/tasks/HomeworksLocalDataSource.kt:138-154 — before extracting anything, compare `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/BaseScheduleLocalDataSource.kt` and `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/schedules/CustomScheduleLocalDataSource.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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 `shared/core/database/src/commonMain/kotlin/ru/aleshin/studyassistant/core/database/datasource/goals/DailyGoalsLocalDataSource.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 (19 lines × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:117— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.kt:117-135 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleView.kt:109-127 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/views/CommonScheduleView.kt:134-152 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/SharedScheduleView.kt:99-117 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/CommonShortClassView.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 (19 lines × 3) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/TodoViewItem.kt:398— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/TodoViewItem.kt:398-416 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeContactInfoView.kt:111-129 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeSubjectView.kt:130-148 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/TodoViewItem.kt:398` 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–18 lines × 3) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseClassInteractor.kt:103— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseClassInteractor.kt:103-119 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseClassInteractor.kt:161-176 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseClassInteractor.kt:196-213 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/BaseClassInteractor.kt:103` 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 (17 lines × 5) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BirthdayDatePicker.kt:68— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BirthdayDatePicker.kt:68-84 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/LinkedClassInfoField.kt:372-388 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/todo/views/TodoDeadlineInfoFields.kt:172-188 | shared/features/settings/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/settings/impl/presentation/ui/calendar/views/HolidaysView.kt:505-521 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyGoalsView.kt:680-696 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/BirthdayDatePicker.kt:68` 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–17 lines × 4) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:114— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:114-130 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:188-203 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/OverviewContent.kt:159-175 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/TodoContent.kt:106-122 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/TodoContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:114` 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 × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareTopBar.kt:49— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareTopBar.kt:49-65 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/views/ShareTopBar.kt:49-65 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/views/TodoTopBar.kt:49-65 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareTopBar.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/share/views/ShareTopBar.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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/views/ShareTopBar.kt:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–17 lines × 2) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:185— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:185-201 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:154-168 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:185` 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–17 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:200— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:200-216 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:272-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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:271` calls `Column`, `spacedBy`, `EventTypeInfoField` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/subject/SubjectContent.kt:200` 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–17 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:261— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:261-272 | shared/features/users/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/users/impl/presentation/ui/employee/views/EmployeeProfileTopSheet.kt:152-168 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.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 (16 lines × 5) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:148— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:148-163 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:223-238 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:298-313 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:380-395 | shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:462-477 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/TextFields.kt:148` 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 × 5) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:117— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt:117-132 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt:116-131 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/HomeworksContent.kt:190-205 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/OverviewContent.kt:162-176 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/todos/TodoContent.kt:109-124 — before extracting anything, compare `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.kt` and `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/subjects/SubjectsContent.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/EmployeeContent.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. 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) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:194— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:194-209 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/common/HomeworkTaskView.kt:159-174 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt:163-178 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 110 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:194` 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) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:308— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt:308-321 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt:103-116 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/DetailsClassView.kt:313-326 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/DetailsClassView.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetClassView.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13–14 lines × 2) shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.kt:101— shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.kt:101-113 | shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/StartClassesReminderWorker.kt:153-166 — 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 `shared/core/data/src/androidMain/kotlin/ru/aleshin/studyassistant/core/data/workers/EndClassesReminderWorker.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 (12–14 lines × 2) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.kt:125— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.kt:125-138 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.kt:182-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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/WeekScheduleContent.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 (12–13 lines × 4) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:236— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:236-248 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:263-275 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:328-339 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:350-361 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/TaskErrorsBottomSheet.kt:236` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 3) backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:470— backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/AiQuotaRepositoryImpl.kt:470-482 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt:215-227 | backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt:343-354 — before extracting anything, compare `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/HomeworkSharingRepositoryImpl.kt` and `backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/sharing/infrastructure/ScheduleSharingRepositoryImpl.kt` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 129 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 (13 lines × 3) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:110— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:110-122 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:232-244 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:351-363 — 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:123` calls `mutableStateOf` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/OverviewTodosSections.kt:364` 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–13 lines × 2) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:317— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:317-328 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt:209-221 — before extracting anything, compare `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSubjectEditorSheet.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 92 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportClassEditorSheet.kt:317` 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–12 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:180— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:180-190 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:205-216 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:226-237 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/share/store/ShareWorkProcessor.kt:180` 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 × 4) shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:161— shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:161-171 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:156-166 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:176-186 | shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt:196-206 — before extracting anything, compare `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt` and `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.kt` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 177 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 `shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.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 (10–11 lines × 2) shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/WarningAlertDialog.kt:57— shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/WarningAlertDialog.kt:57-66 | shared/features/settings/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/settings/impl/presentation/ui/general/views/DeleteScheduleDialog.kt:85-95 — 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 `shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/views/dialog/WarningAlertDialog.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 (8–11 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:237— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:237-247 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsExpandedLayout.kt:244-251 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/organizations/layouts/OrganizationsCompactLayout.kt:237` 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 (10 lines × 3) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopSheet.kt:54— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopSheet.kt:54-63 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopSheet.kt:97-106 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/overview/views/OverviewTopSheet.kt:107-116 — 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopSheet.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.
Duplicated block (8–10 lines × 2) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:62— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:62-69 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.kt:104-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 `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/architecture/component/ComponentExt.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.
Duplicated block (9 lines × 9) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:68— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:68-76 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:119-127 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:174-182 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/profile/views/ProfileTopBar.kt:142-152 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/schedule/views/ScheduleIntervalsDialog.kt:88-96 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:78-86 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:126-134 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt:180-188 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportSwapDaysDialog.kt:75-83 — before extracting anything, compare `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt` and `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/importer/views/ImportFastEditDialogs.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/daily/views/FastEditDialogs.kt:68` 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 (9 lines × 6) shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:57— shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:57-65 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:72-80 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:88-96 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:104-112 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:120-128 | shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:136-144 — 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 `shared/features/analytics/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/analytics/impl/presentation/ui/analytics/store/AnalyticsWorkProcessor.kt:57` 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–9 lines × 2) shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:77— shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:77-84 | shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:91-99 — 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 `shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/employee/store/EmployeeWorkProcessor.kt:77` 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 lines × 10) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:72— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:72-78 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/EmailInfoFields.kt:63-69 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/LocationsInfoFields.kt:61-67 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/PhoneInfoFields.kt:59-65 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/SubjectAndEventTypeInfoField.kt:72-78 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/common/WebInfoFields.kt:63-69 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/EmployeeNameInfoField.kt:76-82 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/employee/views/WorkTimeInfoField.kt:68-74 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/LinkedClassInfoField.kt:106-112 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/organization/views/OrganizationNameInfoField.kt:73-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:72` 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, `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/classes/views/TImeInfoField.kt:69` calls `mutableStateOf` and `shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/homework/views/LinkedClassInfoField.kt:104` 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 (6 lines × 4) shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64— shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64-69 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:87-92 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:129-134 | shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:154-159 — 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 `shared/core/common/src/commonMain/kotlin/ru/aleshin/studyassistant/core/common/functional/AnySerializer.kt:64` 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 `value` to `Any` in one and `Any?): JsonElement = when (value` 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 (4–5 lines × 3) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:355— shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:355-358 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:388-392 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:435-439 — 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 `shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:355` 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 × 4) shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/CustomClassInteractor.kt:147— shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/CustomClassInteractor.kt:147-153 | shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/domain/interactors/CustomScheduleInteractor.kt:212-218 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ScheduleImportInteractor.kt:248-254 | shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/interactors/ShareSchedulesInteractor.kt:327-333 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Low cohesion: Base (LCOM4 11) shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:96— Base's methods fall into 11 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 11 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.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `backend-container.yml` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Swallowed exception (empty catch) shared/core/ui/src/androidMain/kotlin/ru/aleshin/studyassistant/core/ui/views/VoiceInputButton.android.kt:67— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated predicate shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantBottomBar.kt:129— `!isLoadingChat && responseStatus != ResponseStatus.LOADING && !isQuotaExpired && isInputEnabled && textFieldState.text.isNotBlank()` appears character-identically in 2 files — shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantBottomBar.kt, shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/views/AssistantInputIsland.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:221— `(completedHomeworks.isNotEmpty() || runningHomeworks.isNotEmpty()) && errorHomeworks.isNotEmpty()` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt:206— `activeSchedule != null && activeSchedule.classes.isNotEmpty()` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/store/HomeworksComposeStore.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/store/OverviewComposeStore.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 backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekConfig.kt:44— `baseUrl.startsWith(HTTPS_PREFIX) && !baseUrl.contains('?') && !baseUrl.contains('#')` appears character-identically in 2 files — backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/infrastructure/deepseek/DeepSeekConfig.kt, backend/ktor/src/main/kotlin/ru/aleshin/studyassistant/backend/ai/schedule/infrastructure/openrouter/OpenRouterConfig.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 shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt:672— `char == '-' || char == '—' || char == '–' || char == '.'` appears character-identically in 2 files — shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/common/ScheduleImportHandler.kt, shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/domain/validation/ScheduleImportValidator.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:172— `completedHomeworks.isNotEmpty() && runningHomeworks.isNotEmpty()` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:399— `dismissValue == EndToStart && status != HomeworkStatus.COMPLETE` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:398— `dismissValue == EndToStart && status == HomeworkStatus.COMPLETE` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:401— `dismissValue == StartToEnd && status != HomeworkStatus.SKIPPED` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt:400— `dismissValue == StartToEnd && status == HomeworkStatus.SKIPPED` appears character-identically in 2 files — shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/homeworks/views/DailyHomeworksDetailsView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/DailyHomeworksView.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 shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/models/classes/FastEditDurationMath.kt:49— `durations.size > 1 && grouped.size == 1 && mode >= MEGA_DURATION_MS` appears character-identically in 2 files — shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/models/classes/FastEditDurationMath.kt, shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/models/importing/ImportFastEditDurationMath.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 shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/AssistantLayoutMode.kt:42— `isCompactWidth || isCompactHeight || isTabletopPosture` appears character-identically in 9 files — shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/AssistantLayoutMode.kt, shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/EditorLayoutMode.kt, shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/InfoLayoutMode.kt, shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/PreviewLayoutMode.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 shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/interactors/TodoCompletionInteractor.kt:55— `linkedGoal != null && !linkedGoal.isDone` appears character-identically in 3 files — shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/interactors/TodoCompletionInteractor.kt, REDACTED, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/domain/interactors/HomeworksInteractor.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 shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/interactors/TodoCompletionInteractor.kt:65— `linkedGoal != null && linkedGoal.targetDate >= currentTime.startThisDay()` appears character-identically in 2 files — shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/interactors/TodoCompletionInteractor.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 shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/EmployeeRepositoryImpl.kt:55— `oldAvatarUrl != null && oldAvatarUrl != avatar` appears character-identically in 2 files — shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/EmployeeRepositoryImpl.kt, shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/repositories/OrganizationsRepositoryImpl.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 shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt:298— `openClassBottomSheet && classModel != null` appears character-identically in 2 files — shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/DetailsContent.kt, shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/details/layouts/DetailsExpandedWeekSection.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 shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt:30— `other == null || this::class != other::class` appears character-identically in 3 files — shared/core/domain/src/commonMain/kotlin/ru/aleshin/studyassistant/core/domain/entities/files/InputFile.kt, shared/core/ui/src/commonMain/kotlin/ru/aleshin/studyassistant/core/ui/models/InputFileUi.kt, shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/platform/ImageCompressor.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 shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt:210— `priority == TaskPriority.MEDIUM || priority == TaskPriority.HIGH` appears character-identically in 2 files — shared/features/schedule/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/schedule/impl/presentation/ui/common/SheetHomeworkView.kt, shared/features/tasks/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/tasks/impl/presentation/ui/overview/views/GoalHomeworkView.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 widget/src/androidMain/kotlin/ru/aleshin/studyassistant/widget/presentation/ui/goals/GoalWidgetRow.kt:62— `sizeClass.width == WidgetSizeClass.Width.COMPACT || sizeClass.height == WidgetSizeClass.Height.COMPACT` appears character-identically in 3 files — widget/src/androidMain/kotlin/ru/aleshin/studyassistant/widget/presentation/ui/goals/GoalWidgetRow.kt, widget/src/androidMain/kotlin/ru/aleshin/studyassistant/widget/presentation/ui/homeworks/HomeworkWidgetRow.kt, widget/src/androidMain/kotlin/ru/aleshin/studyassistant/widget/presentation/ui/todos/TodoWidgetRow.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 shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/AssistantLayoutMode.kt:43— `useNavigationRail || useExpandedLayout || isBookPosture` appears character-identically in 9 files — shared/features/chat/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/chat/impl/presentation/ui/assistant/AssistantLayoutMode.kt, shared/features/editor/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/editor/impl/presentation/ui/EditorLayoutMode.kt, shared/features/info/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/info/impl/presentation/ui/InfoLayoutMode.kt, shared/features/preview/impl/src/commonMain/kotlin/ru/aleshin/studyassistant/preview/impl/presentation/ui/PreviewLayoutMode.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 shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt:76— `workTimeStart != null && workTimeEnd != null` appears character-identically in 2 files — shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeDetailsUiMapper.kt, shared/core/presentation/src/commonMain/kotlin/ru/aleshin/studyassistant/core/presentation/mappers/users/EmployeeUiMapper.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.
Documentation: no project overview README.md— The opening displays branding badges but contains no description of what StudyAssistant is or what it does. State the project's purpose and core features in one sentence under the title, so a reader can tell what this app does without reading further.
Documentation: no installation or build instructions README.md— There are no installation/build/usage instructions anywhere in the document. Add an 'Installation' section covering how to add the library, build it (Kotlin configuration), and run the app on Android/iOS.
Documentation: no usage examples README.md— There are no usage examples or commands shown in any shell block. Add a 'Usage' section with code blocks for each major feature (e.g. scheduling, importing from photos) so readers can run the app immediately.
Silent fallback default in catch shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/FunctionArgumentsHandler.kt:35— `encode` 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 shared/core/data/src/commonMain/kotlin/ru/aleshin/studyassistant/core/data/handlers/FunctionArgumentsHandler.kt:48— `decode` swallows every exception into `emptyMap()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
No ADRs found — 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 10 of 32 project(s) overshoot their size bounds, lowering Project Cohesion to 3.9/10. The most over is `backend/ktor` (11648 LoC, 296 module-visible types across 63 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
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.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1776/2394 types (74%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `iosApp`.
No SAST — 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 7028 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 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.)
Off the main sequence: StudyAssistant:shared:core:presentation — StudyAssistant:shared:core:presentation: abstractness 0.02, instability 0.13, distance 0.85 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: StudyAssistant:shared:core:domain — StudyAssistant:shared:core:domain: abstractness 0.14, instability 0.04, distance 0.82 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: StudyAssistant:shared:core:common — StudyAssistant:shared:core:common: abstractness 0.29, instability 0.00, distance 0.71 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Outdated: YandexMobileAds — `YandexMobileAds` is locked at 8.1.0 in iosApp/Podfile.lock, but 8.6.0 is the newest release the CocoaPods trunk lists within the same major. A `~>` requirement admits every release below the next major — so `pod update YandexMobileAds` reaches this one with no change to the Podfile.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1636d-c58d-79db-89d3-04a761f9a1f5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 8 · Warnings: 494 · Recommendations: 36 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 11:45 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.