Public report of DemchaAV/GraphCompose, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 21:03 UTC · Survey ID cd_c24355afda0e4b3bae52c68dfc9b30bc
DemchaAV/GraphCompose
Measured 16 November 2026, 21:02 UTC, at code version a18e4ac
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 198,730 lines of product code in 20 projects, tests not counted · Estimated rebuild effort: about 2.8 person-years · Weakest lens: Code Health, 30.7
Findings by how serious they are
59 critical1266 serious57 minor
12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 21:02 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
72of 72 dimensions measured by tools.
1371of 1382 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
72dimensions across 7 lenses, read from 198,730 lines of product code in 20 projects.
DemchaAV/GraphCompose falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 48.8 out of 100 and is rated Weak, and 55 of its 59 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Code Health, at 30.7, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 5.3 points. Making the controls keyboard-usable comes next, worth about 4.6 points. Raising Code Health to 70 would lift the score to about 61.8.
Fifty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and two packages carry licence risk. Pinning each tool to an exact version, setting a waiting period for automatic updates and replacing or clearing the banned-licence packages would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. The button or link with no name needs a name, even when it only shows an icon.
The product code is 198,730 lines, about €400,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 30.7 to 70, the lowest score rated Strong, the score would rise from 48.8 to about 61.8.
Code composition: what the lines of code are
Product code 55%Tests 45%
Rebuild cost: about €400,000 · Estimate
Cost to rebuild
€130,000 to €670,000, for 2,224 to 7,055 hours of work, about 2.8 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 49. 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: 198,730 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 5.3 points · Medium effort · Type Safety
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 4.6 points · Medium effort · Keyboard semantics
3
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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 €400,000 to build again, about 2.8 person-years of work. Its weakest lens is Code Health, at 30.7 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. Of all the actions in this report, it raises the score most for the work it takes: about 5.3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 504,237 lines over the last 90 days, which is about 2,044,961 lines a year. At that pace, the extra work comes to an estimated 109.1 to 681.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
97 modules, with 304 dependencies between them. 6 loops run through 16 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 57 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.
engine.components.content.shape uses engine.components.style, so a change to engine.components.style can break engine.components.content.shape, while a change to engine.components.content.shape can't break engine.components.style.
Position
Below the diagonal: engine.components.content.shape uses a module listed above it, which is the healthy direction.
7→13 engine.font uses engine.components.content.textpart of a loop✕
Connections
2 pairs of types, where a type in engine.font uses a type in engine.components.content.text.
engine.font uses engine.components.content.text, so a change to engine.components.content.text can break engine.font, while a change to engine.font can't break engine.components.content.text.
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.
document.table uses document.style, so a change to document.style can break document.table, while a change to document.table can't break document.style.
Position
Below the diagonal: document.table uses a module listed above it, which is the healthy direction.
9→12 document.table uses document.nodepart of a loop✕
Connections
3 pairs of types, where a type in document.table uses a type in document.node.
document.templates.core.theme uses font, so a change to font can break document.templates.core.theme, while a change to document.templates.core.theme can't break font.
Position
Below the diagonal: document.templates.core.theme uses a module listed above it, which is the healthy direction.
document.templates.core.theme uses document.style, so a change to document.style can break document.templates.core.theme, while a change to document.templates.core.theme can't break document.style.
Position
Below the diagonal: document.templates.core.theme uses a module listed above it, which is the healthy direction.
engine.measurement uses engine.font, so a change to engine.font can break engine.measurement, while a change to engine.measurement can't break engine.font.
Position
Below the diagonal: engine.measurement uses a module listed above it, which is the healthy direction.
11→13 engine.measurement uses engine.components.content.textpart of a loop✕
Connections
3 pairs of types, where a type in engine.measurement uses a type in engine.components.content.text.
engine.measurement uses engine.components.content.text, so a change to engine.components.content.text can break engine.measurement, while a change to engine.measurement can't break engine.components.content.text.
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.
88 pairs of types, where a type in document.node uses a type in document.style. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
engine.components.content.text uses font, so a change to font can break engine.components.content.text, while a change to engine.components.content.text can't break font.
Position
Below the diagonal: engine.components.content.text uses a module listed above it, which is the healthy direction.
engine.components.content.text uses engine.font, so a change to engine.font can break engine.components.content.text, while a change to engine.components.content.text can't break engine.font.
Position
Below the diagonal: engine.components.content.text uses a module listed above it, which is the healthy direction.
engine.components.content.text uses engine.measurement, so a change to engine.measurement can break engine.components.content.text, while a change to engine.components.content.text can't break engine.measurement.
Position
Below the diagonal: engine.components.content.text uses a module listed above it, which is the healthy direction.
document.chart uses document.style, so a change to document.style can break document.chart, while a change to document.chart can't break document.style.
Position
Below the diagonal: document.chart uses a module listed above it, which is the healthy direction.
document.output uses document.style, so a change to document.style can break document.output, while a change to document.output can't break document.style.
Position
Below the diagonal: document.output uses a module listed above it, which is the healthy direction.
document.output uses document.node, so a change to document.node can break document.output, while a change to document.output can't break document.node.
Position
Below the diagonal: document.output uses a module listed above it, which is the healthy direction.
engine.components.content.table uses engine.components.style, so a change to engine.components.style can break engine.components.content.table, while a change to engine.components.content.table can't break engine.components.style.
Position
Below the diagonal: engine.components.content.table uses a module listed above it, which is the healthy direction.
engine.components.content.table uses engine.components.content.shape, so a change to engine.components.content.shape can break engine.components.content.table, while a change to engine.components.content.table can't break engine.components.content.shape.
Position
Below the diagonal: engine.components.content.table uses a module listed above it, which is the healthy direction.
engine.components.content.table uses engine.components.content.text, so a change to engine.components.content.text can break engine.components.content.table, while a change to engine.components.content.table can't break engine.components.content.text.
Position
Below the diagonal: engine.components.content.table uses a module listed above it, which is the healthy direction.
engine.render.pdf uses engine.font, so a change to engine.font can break engine.render.pdf, while a change to engine.render.pdf can't break engine.font.
Position
Below the diagonal: engine.render.pdf uses a module listed above it, which is the healthy direction.
engine.render.pdf uses engine.components.content.text, so a change to engine.components.content.text can break engine.render.pdf, while a change to engine.render.pdf can't break engine.components.content.text.
Position
Below the diagonal: engine.render.pdf uses a module listed above it, which is the healthy direction.
document.layout.payloads uses document.image, so a change to document.image can break document.layout.payloads, while a change to document.layout.payloads can't break document.image.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.components.content, so a change to engine.components.content can break document.layout.payloads, while a change to document.layout.payloads can't break engine.components.content.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.components.style, so a change to engine.components.style can break document.layout.payloads, while a change to document.layout.payloads can't break engine.components.style.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses document.style, so a change to document.style can break document.layout.payloads, while a change to document.layout.payloads can't break document.style.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.components.content.shape, so a change to engine.components.content.shape can break document.layout.payloads, while a change to document.layout.payloads can't break engine.components.content.shape.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.measurement, so a change to engine.measurement can break document.layout.payloads, while a change to document.layout.payloads can't break engine.measurement.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
36 pairs of types, where a type in document.layout.payloads uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.layout.payloads uses document.node, so a change to document.node can break document.layout.payloads, while a change to document.layout.payloads can't break document.node.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.components.content.text, so a change to engine.components.content.text can break document.layout.payloads, while a change to document.layout.payloads can't break engine.components.content.text.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
document.layout.payloads uses engine.components.content.table, so a change to engine.components.content.table can break document.layout.payloads, while a change to document.layout.payloads can't break engine.components.content.table.
Position
Below the diagonal: document.layout.payloads uses a module listed above it, which is the healthy direction.
18→19 document.layout.payloads uses document.layoutpart of a loop✕
Connections
4 pairs of types, where a type in document.layout.payloads uses a type in document.layout.
document.layout.payloads uses document.layout, so a change to document.layout can break document.layout.payloads, while a change to document.layout.payloads can't break document.layout.
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.
document.layout uses document.image, so a change to document.image can break document.layout, while a change to document.layout can't break document.image.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.components.content, so a change to engine.components.content can break document.layout, while a change to document.layout can't break engine.components.content.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.components.style, so a change to engine.components.style can break document.layout, while a change to document.layout can't break engine.components.style.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses document.style, so a change to document.style can break document.layout, while a change to document.layout can't break document.style.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.components.content.shape, so a change to engine.components.content.shape can break document.layout, while a change to document.layout can't break engine.components.content.shape.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses document.table, so a change to document.table can break document.layout, while a change to document.layout can't break document.table.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.measurement, so a change to engine.measurement can break document.layout, while a change to document.layout can't break engine.measurement.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
51 pairs of types, where a type in document.layout uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.layout uses document.node, so a change to document.node can break document.layout, while a change to document.layout can't break document.node.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.components.content.text, so a change to engine.components.content.text can break document.layout, while a change to document.layout can't break engine.components.content.text.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses document.chart, so a change to document.chart can break document.layout, while a change to document.layout can't break document.chart.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses engine.components.content.table, so a change to engine.components.content.table can break document.layout, while a change to document.layout can't break engine.components.content.table.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
document.layout uses document.layout.payloads, so a change to document.layout.payloads can break document.layout, while a change to document.layout can't break document.layout.payloads.
Position
Below the diagonal: document.layout uses a module listed above it, which is the healthy direction.
19→20 document.layout uses document.backend.fixedpart of a loop✕
Connections
1 pair of types, where a type in document.layout uses a type in document.backend.fixed.
document.layout uses document.backend.fixed, so a change to document.backend.fixed can break document.layout, while a change to document.layout can't break document.backend.fixed.
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.
document.backend.fixed uses engine.measurement, so a change to engine.measurement can break document.backend.fixed, while a change to document.backend.fixed can't break engine.measurement.
Position
Below the diagonal: document.backend.fixed uses a module listed above it, which is the healthy direction.
document.backend.fixed uses document.output, so a change to document.output can break document.backend.fixed, while a change to document.backend.fixed can't break document.output.
Position
Below the diagonal: document.backend.fixed uses a module listed above it, which is the healthy direction.
document.backend.fixed uses document.layout, so a change to document.layout can break document.backend.fixed, while a change to document.backend.fixed can't break document.layout.
Position
Below the diagonal: document.backend.fixed uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses document.image, so a change to document.image can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.image.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses engine.components.content, so a change to engine.components.content can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break engine.components.content.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses font, so a change to font can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break font.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses document.style, so a change to document.style can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.style.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses engine.components.content.shape, so a change to engine.components.content.shape can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break engine.components.content.shape.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses document.node, so a change to document.node can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.node.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses engine.components.content.text, so a change to engine.components.content.text can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break engine.components.content.text.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses engine.components.content.table, so a change to engine.components.content.table can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break engine.components.content.table.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses engine.render.pdf, so a change to engine.render.pdf can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break engine.render.pdf.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses document.layout.payloads, so a change to document.layout.payloads can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.layout.payloads.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf.handlers uses document.layout, so a change to document.layout can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.layout.
Position
Below the diagonal: document.backend.fixed.pdf.handlers uses a module listed above it, which is the healthy direction.
21→26 document.backend.fixed.pdf.handlers uses document.backend.fixed.pdfpart of a loop✕
Connections
35 pairs of types, where a type in document.backend.fixed.pdf.handlers uses a type in document.backend.fixed.pdf. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.backend.fixed.pdf.handlers uses document.backend.fixed.pdf, so a change to document.backend.fixed.pdf can break document.backend.fixed.pdf.handlers, while a change to document.backend.fixed.pdf.handlers can't break document.backend.fixed.pdf.
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.
document.backend.semantic uses font, so a change to font can break document.backend.semantic, while a change to document.backend.semantic can't break font.
Position
Below the diagonal: document.backend.semantic uses a module listed above it, which is the healthy direction.
document.backend.semantic uses document.output, so a change to document.output can break document.backend.semantic, while a change to document.backend.semantic can't break document.output.
Position
Below the diagonal: document.backend.semantic uses a module listed above it, which is the healthy direction.
document.backend.semantic uses document.layout, so a change to document.layout can break document.backend.semantic, while a change to document.backend.semantic can't break document.layout.
Position
Below the diagonal: document.backend.semantic uses a module listed above it, which is the healthy direction.
document.debug.snapshot uses engine.components.style, so a change to engine.components.style can break document.debug.snapshot, while a change to document.debug.snapshot can't break engine.components.style.
Position
Below the diagonal: document.debug.snapshot uses a module listed above it, which is the healthy direction.
document.debug.snapshot uses engine.components.content.text, so a change to engine.components.content.text can break document.debug.snapshot, while a change to document.debug.snapshot can't break engine.components.content.text.
Position
Below the diagonal: document.debug.snapshot uses a module listed above it, which is the healthy direction.
document.debug.snapshot uses document.layout.payloads, so a change to document.layout.payloads can break document.debug.snapshot, while a change to document.debug.snapshot can't break document.layout.payloads.
Position
Below the diagonal: document.debug.snapshot uses a module listed above it, which is the healthy direction.
document.debug.snapshot uses document.layout, so a change to document.layout can break document.debug.snapshot, while a change to document.debug.snapshot can't break document.layout.
Position
Below the diagonal: document.debug.snapshot uses a module listed above it, which is the healthy direction.
109 pairs of types, where a type in document.dsl uses a type in document.style. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
81 pairs of types, where a type in document.dsl uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
39 pairs of types, where a type in document.api uses a type in document.layout. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.api uses document.backend.fixed, so a change to document.backend.fixed can break document.api, while a change to document.api can't break document.backend.fixed.
Position
Below the diagonal: document.api uses a module listed above it, which is the healthy direction.
document.api uses document.backend.semantic, so a change to document.backend.semantic can break document.api, while a change to document.api can't break document.backend.semantic.
Position
Below the diagonal: document.api uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses engine.components.content, so a change to engine.components.content can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break engine.components.content.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses engine.components.style, so a change to engine.components.style can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break engine.components.style.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses font, so a change to font can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break font.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.style, so a change to document.style can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.style.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses engine.measurement, so a change to engine.measurement can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break engine.measurement.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.node, so a change to document.node can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.node.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.output, so a change to document.output can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.output.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.layout.payloads, so a change to document.layout.payloads can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.layout.payloads.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.layout, so a change to document.layout can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.layout.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.backend.fixed, so a change to document.backend.fixed can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.backend.fixed.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pdf uses document.backend.fixed.pdf.handlers, so a change to document.backend.fixed.pdf.handlers can break document.backend.fixed.pdf, while a change to document.backend.fixed.pdf can't break document.backend.fixed.pdf.handlers.
Position
Below the diagonal: document.backend.fixed.pdf uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses engine.components.content, so a change to engine.components.content can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break engine.components.content.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses font, so a change to font can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break font.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.style, so a change to document.style can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.style.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses engine.components.content.shape, so a change to engine.components.content.shape can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break engine.components.content.shape.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.node, so a change to document.node can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.node.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses engine.components.content.text, so a change to engine.components.content.text can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break engine.components.content.text.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.output, so a change to document.output can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.output.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses engine.components.content.table, so a change to engine.components.content.table can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break engine.components.content.table.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses engine.render.pdf, so a change to engine.render.pdf can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break engine.render.pdf.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.layout.payloads, so a change to document.layout.payloads can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.layout.payloads.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.layout, so a change to document.layout can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.layout.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx.handlers uses document.backend.fixed.pdf.handlers, so a change to document.backend.fixed.pdf.handlers can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.backend.fixed.pdf.handlers.
Position
Below the diagonal: document.backend.fixed.pptx.handlers uses a module listed above it, which is the healthy direction.
27→31 document.backend.fixed.pptx.handlers uses document.backend.fixed.pptxpart of a loop✕
Connections
32 pairs of types, where a type in document.backend.fixed.pptx.handlers uses a type in document.backend.fixed.pptx. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.backend.fixed.pptx.handlers uses document.backend.fixed.pptx, so a change to document.backend.fixed.pptx can break document.backend.fixed.pptx.handlers, while a change to document.backend.fixed.pptx.handlers can't break document.backend.fixed.pptx.
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.
document.backend.semantic.docx uses document.image, so a change to document.image can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.image.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.components.content, so a change to engine.components.content can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.components.content.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.components.style, so a change to engine.components.style can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.components.style.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses font, so a change to font can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break font.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
49 pairs of types, where a type in document.backend.semantic.docx uses a type in document.style. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.backend.semantic.docx uses document.style, so a change to document.style can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.style.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.components.content.shape, so a change to engine.components.content.shape can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.components.content.shape.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.svg, so a change to document.svg can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.svg.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.table, so a change to document.table can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.table.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.measurement, so a change to engine.measurement can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.measurement.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
85 pairs of types, where a type in document.backend.semantic.docx uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.backend.semantic.docx uses document.node, so a change to document.node can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.node.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.components.content.text, so a change to engine.components.content.text can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.components.content.text.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.chart, so a change to document.chart can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.chart.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.output, so a change to document.output can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.output.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses engine.components.content.table, so a change to engine.components.content.table can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break engine.components.content.table.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.layout.payloads, so a change to document.layout.payloads can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.layout.payloads.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in document.backend.semantic.docx uses a type in document.layout. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.backend.semantic.docx uses document.layout, so a change to document.layout can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.layout.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.backend.semantic.docx uses document.backend.semantic, so a change to document.backend.semantic can break document.backend.semantic.docx, while a change to document.backend.semantic.docx can't break document.backend.semantic.
Position
Below the diagonal: document.backend.semantic.docx uses a module listed above it, which is the healthy direction.
document.templates.core.identity uses document.style, so a change to document.style can break document.templates.core.identity, while a change to document.templates.core.identity can't break document.style.
Position
Below the diagonal: document.templates.core.identity uses a module listed above it, which is the healthy direction.
document.templates.core.identity uses document.svg, so a change to document.svg can break document.templates.core.identity, while a change to document.templates.core.identity can't break document.svg.
Position
Below the diagonal: document.templates.core.identity uses a module listed above it, which is the healthy direction.
document.templates.core.identity uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.core.identity, while a change to document.templates.core.identity can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.core.identity uses a module listed above it, which is the healthy direction.
document.templates.core.identity uses document.node, so a change to document.node can break document.templates.core.identity, while a change to document.templates.core.identity can't break document.node.
Position
Below the diagonal: document.templates.core.identity uses a module listed above it, which is the healthy direction.
document.templates.core.identity uses document.dsl, so a change to document.dsl can break document.templates.core.identity, while a change to document.templates.core.identity can't break document.dsl.
Position
Below the diagonal: document.templates.core.identity uses a module listed above it, which is the healthy direction.
document.templates.core.widgets uses document.style, so a change to document.style can break document.templates.core.widgets, while a change to document.templates.core.widgets can't break document.style.
Position
Below the diagonal: document.templates.core.widgets uses a module listed above it, which is the healthy direction.
document.templates.core.widgets uses document.table, so a change to document.table can break document.templates.core.widgets, while a change to document.templates.core.widgets can't break document.table.
Position
Below the diagonal: document.templates.core.widgets uses a module listed above it, which is the healthy direction.
document.templates.core.widgets uses document.node, so a change to document.node can break document.templates.core.widgets, while a change to document.templates.core.widgets can't break document.node.
Position
Below the diagonal: document.templates.core.widgets uses a module listed above it, which is the healthy direction.
document.templates.core.widgets uses document.dsl, so a change to document.dsl can break document.templates.core.widgets, while a change to document.templates.core.widgets can't break document.dsl.
Position
Below the diagonal: document.templates.core.widgets uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses engine.components.content, so a change to engine.components.content can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break engine.components.content.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses font, so a change to font can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break font.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.style, so a change to document.style can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.style.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses engine.components.content.shape, so a change to engine.components.content.shape can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break engine.components.content.shape.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.node, so a change to document.node can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.node.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses engine.components.content.text, so a change to engine.components.content.text can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break engine.components.content.text.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.output, so a change to document.output can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.output.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses engine.render.pdf, so a change to engine.render.pdf can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break engine.render.pdf.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.layout.payloads, so a change to document.layout.payloads can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.layout.payloads.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.layout, so a change to document.layout can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.layout.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.backend.fixed, so a change to document.backend.fixed can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.backend.fixed.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.backend.fixed.pdf, so a change to document.backend.fixed.pdf can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.backend.fixed.pdf.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.backend.fixed.pptx uses document.backend.fixed.pptx.handlers, so a change to document.backend.fixed.pptx.handlers can break document.backend.fixed.pptx, while a change to document.backend.fixed.pptx can't break document.backend.fixed.pptx.handlers.
Position
Below the diagonal: document.backend.fixed.pptx uses a module listed above it, which is the healthy direction.
document.templates.api uses document.api, so a change to document.api can break document.templates.api, while a change to document.templates.api can't break document.api.
Position
Below the diagonal: document.templates.api uses a module listed above it, which is the healthy direction.
document.templates.cv.data uses document.image, so a change to document.image can break document.templates.cv.data, while a change to document.templates.cv.data can't break document.image.
Position
Below the diagonal: document.templates.cv.data uses a module listed above it, which is the healthy direction.
document.templates.cv.data uses document.templates.core.identity, so a change to document.templates.core.identity can break document.templates.cv.data, while a change to document.templates.cv.data can't break document.templates.core.identity.
Position
Below the diagonal: document.templates.cv.data uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses font, so a change to font can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break font.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses document.style, so a change to document.style can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break document.style.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses document.node, so a change to document.node can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break document.node.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses document.api, so a change to document.api can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break document.api.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.coverletter.presets uses document.templates.api, so a change to document.templates.api can break document.templates.coverletter.presets, while a change to document.templates.coverletter.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.coverletter.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.image, so a change to document.image can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.image.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses font, so a change to font can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break font.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
34 pairs of types, where a type in document.templates.cv.presets uses a type in document.style. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.cv.presets uses document.style, so a change to document.style can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.style.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.svg, so a change to document.svg can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.svg.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.table, so a change to document.table can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.table.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in document.templates.cv.presets uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.cv.presets uses document.node, so a change to document.node can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.node.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
75 pairs of types, where a type in document.templates.cv.presets uses a type in document.dsl. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.cv.presets uses document.dsl, so a change to document.dsl can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.dsl.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.api, so a change to document.api can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.api.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.presets uses document.templates.core.identity, so a change to document.templates.core.identity can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.templates.core.identity.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in document.templates.cv.presets uses a type in document.templates.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.cv.presets uses document.templates.api, so a change to document.templates.api can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
133 pairs of types, where a type in document.templates.cv.presets uses a type in document.templates.cv.data. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.cv.presets uses document.templates.cv.data, so a change to document.templates.cv.data can break document.templates.cv.presets, while a change to document.templates.cv.presets can't break document.templates.cv.data.
Position
Below the diagonal: document.templates.cv.presets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.image, so a change to document.image can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.image.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.style, so a change to document.style can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.style.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.node, so a change to document.node can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.node.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.dsl, so a change to document.dsl can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.dsl.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.templates.core.identity, so a change to document.templates.core.identity can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.templates.core.identity.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.cv.widgets uses document.templates.cv.data, so a change to document.templates.cv.data can break document.templates.cv.widgets, while a change to document.templates.cv.widgets can't break document.templates.cv.data.
Position
Below the diagonal: document.templates.cv.widgets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.image, so a change to document.image can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.image.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.style, so a change to document.style can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.style.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.svg, so a change to document.svg can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.svg.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.table, so a change to document.table can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.table.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
46 pairs of types, where a type in document.templates.invoice.presets uses a type in document.node. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.invoice.presets uses document.node, so a change to document.node can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.node.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
101 pairs of types, where a type in document.templates.invoice.presets uses a type in document.dsl. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.invoice.presets uses document.dsl, so a change to document.dsl can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.dsl.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.api, so a change to document.api can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.api.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.invoice.presets uses document.templates.api, so a change to document.templates.api can break document.templates.invoice.presets, while a change to document.templates.invoice.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.invoice.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.image, so a change to document.image can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.image.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.style, so a change to document.style can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.style.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.svg, so a change to document.svg can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.svg.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.table, so a change to document.table can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.table.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.node, so a change to document.node can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.node.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in document.templates.proposal.presets uses a type in document.dsl. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
document.templates.proposal.presets uses document.dsl, so a change to document.dsl can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.dsl.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.api, so a change to document.api can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.api.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.proposal.presets uses document.templates.api, so a change to document.templates.api can break document.templates.proposal.presets, while a change to document.templates.proposal.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.proposal.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.style, so a change to document.style can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.style.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.templates.core.theme, so a change to document.templates.core.theme can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.templates.core.theme.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.dsl, so a change to document.dsl can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.dsl.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.api, so a change to document.api can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.api.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.templates.core.identity, so a change to document.templates.core.identity can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.templates.core.identity.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.receipt.presets uses document.templates.api, so a change to document.templates.api can break document.templates.receipt.presets, while a change to document.templates.receipt.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.receipt.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.style, so a change to document.style can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.style.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.svg, so a change to document.svg can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.svg.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.table, so a change to document.table can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.table.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.node, so a change to document.node can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.node.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.dsl, so a change to document.dsl can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.dsl.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.api, so a change to document.api can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.api.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
document.templates.rota.presets uses document.templates.api, so a change to document.templates.api can break document.templates.rota.presets, while a change to document.templates.rota.presets can't break document.templates.api.
Position
Below the diagonal: document.templates.rota.presets uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 30.7 · Weak · gated by R1, R2, R3, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
60
High / Critical
A03:2025 — Software Supply Chain Failures
9
Medium
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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 — 59
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 — 1266
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 — 57
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 72 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, 1371 of 1382 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java, .mjs) 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.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 58 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 883 test source file(s) (.java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .mjs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Maven build resolved 39 artifact(s) (6 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 1970 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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (wrapper/pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 127 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention 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 retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights 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 data-subject rights controls.
ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 111 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with DocxSemanticBackend.writePanelPiece (cyclomatic 72). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.5/10.
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.
+ 180 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 60 down to 60 or less in Cognitive Complexity — start with extract-api.buildSurface (cognitive 100), DocxSemanticBackend.reportZoneLine (cognitive 91), DocxSemanticBackend.writePanelPiece (cognitive 89). — 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 7 together lifts Cognitive Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Stronggated by 62 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 18 ClassTooLong finding(s) in God Classes — start with DocxLayoutMetrics.java, LayoutCompiler.java, ParagraphWrapping.java. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 16 TooManyMethods finding(s) in God Classes — start with DocxSemanticBackend.java, DocxLayoutMetrics.java, AbstractFlowBuilder.java. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 15 FileTooLong finding(s) in God Classes — start with DocxSemanticBackend.java, DocxLayoutMetrics.java, LayoutCompiler.java. — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
425 duplicated block group(s) detected. 9.1 % of the production lines (18,026 of 198,730) are in a reported copy. A further 347 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 150 of the 772 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 218 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 36 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with LayoutGraphSnapshotExtractor.java (3), InlineLayoutToken.java (2), LayoutCompiler.java (2). — One of this dimension's main actionable groups (36 warning-level).
Resolve the 36 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with MintEditorial.java (2), MerchantSettlement.java (2), EditorialPageOne.java (2). — One of this dimension's main actionable groups (36 warning-level).
Resolve the 36 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with LayerStackBuilder.java (3), CompactMonoLetter.java (3), EngineeringResumeLetter.java (3). — One of this dimension's main actionable groups (36 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 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.
20 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 8 of the 20 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: graph-compose-emoji · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with DocxFidelityGateTest.java, PageMarginTest.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 58 tests. Measured on the JavaScript/TypeScript suite only — at least 883 test source file(s) (.java) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
2 of 36 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 24 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 34 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 7 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. 2 name a copyleft licence without stating its version (e.g. "GNU Lesser General Public Licence"), which this policy bans only at specific versions; they are reported here and not charged, because guessing the version would either accuse an LGPL-2.1 artifact or clear an LGPL-3.0 one.
Banned license: org.openjdk.jmh:jmh-core · ×2
What to do
Resolve the 2 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java (270×72=19440); render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java (62×19=1178); render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java (18×17=306) Repeated repair below the complexity floor: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java (14 of 15 changes were fixes); render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java (8 of 8 changes were fixes); render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java (7 of 7 changes were fixes)
Resolve the 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with DocxSemanticBackend.java, DocxLayoutMetrics.java, DocxDrawingAnchors.java. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 11 Repeated repair finding(s) in Churn × Complexity Hotspots — start with DocxDrawings.java, DocxExportReport.java, DocxFontTable.java. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 198730 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 9 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
3 of 9 build units (Maven) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3templates/pom.xml:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
40 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
60 finding(s): 0 critical, 55 high, 4 medium, 1 low. 53 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `mvnw` (line 86, line 124, line 134, …), `scripts/ab-bench.sh` (lines 76–78, lines 80–84, line 134, …), `scripts/release-smoke/run.sh` (line 135, line 149, line 201) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 53 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (53 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 671 of the 1019 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with RowBuilder.java, DocxDrawings.java. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with Palette.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 22 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels8.0 / 10Strong✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — web/examples.js:542
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure8.0 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. (×2) — web-src/pages/index.html:372, web/index.html:696
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×6) — web-src/pages/index.html:377, web-src/pages/index.html:378, web-src/pages/index.html:379, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.example-card[data-id] .example-preview-fallback` sets color: #52606d on background-color: #0b1220 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — web/styles.css:1286
`.example-action` sets color: #fff on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — web/styles.css:1391
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary✓ 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's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
2 public types in `com.demcha.compose.document.dsl.internal` are marked as implementation by their own namespace, folder or name: `BuilderSupport` (core/src/main/java/com/demcha/compose/document/dsl/internal/BuilderSupport.java:9, `internal`), `SemanticNameNormalizer` (core/src/main/java/com/demcha/compose/document/dsl/internal/SemanticNameNormalizer.java:6, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — core/src/main/java/com/demcha/compose/document/dsl/internal/BuilderSupport.java:9
What to do
Hide `com.demcha.compose.document.dsl.internal` (`BuilderSupport`, `SemanticNameNormalizer`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
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.
What to do
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.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 31 plain JS — the untyped files are knowledge/tools/api-query/api-query.mjs, knowledge/tools/api-surface/check-stability-doc.mjs, knowledge/tools/api-surface/extract-api.mjs, knowledge/tools/api-surface/lib/annotations.mjs, knowledge/tools/api-surface/lib/javap.mjs, knowledge/tools/api-surface/lib/provenance.mjs (+25 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
10 duplicated blocks under knowledge/tools/ have copies in at least two of the sibling directories api-query, api-surface, bundle, changeset, claims, routing — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — knowledge/tools/api-query/api-query.mjs:215
knowledge/tools/api-query/api-query.mjs:215 · knowledge/tools/routing/lib/pack-version.mjs:30 — the two spans are one implementation copied and then locally edited — 170 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — knowledge/tools/api-query/api-query.mjs:215
knowledge/tools/bundle/build-bundle.mjs:44 · knowledge/tools/routing/check-routes.mjs:69 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — knowledge/tools/bundle/build-bundle.mjs:44
knowledge/tools/api-query/api-query.mjs:342 · knowledge/tools/claims/check-claims.mjs:58 — the two spans are one implementation copied and then locally edited — 78 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — knowledge/tools/api-query/api-query.mjs:342
knowledge/tools/api-surface/lib/provenance.mjs:46 · knowledge/tools/api-surface/lib/tree.mjs:34 — the two spans are one implementation copied and then locally edited — 103 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — knowledge/tools/api-surface/lib/provenance.mjs:46
knowledge/tools/api-query/api-query.mjs:94 · knowledge/tools/api-surface/extract-api.mjs:135 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — knowledge/tools/api-query/api-query.mjs:94
knowledge/tools/api-surface/lib/javap.mjs:89 · knowledge/tools/api-surface/lib/source-names.mjs:27 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — knowledge/tools/api-surface/lib/javap.mjs:89
knowledge/tools/api-query/api-query.mjs:349 · knowledge/tools/routing/check-routes.mjs:107 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — knowledge/tools/api-query/api-query.mjs:349
knowledge/tools/claims/check-claims.mjs:73 · knowledge/tools/routing/check-routes.mjs:117 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — knowledge/tools/claims/check-claims.mjs:73
web/examples.js:587 · web/examples.js:700 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — web/examples.js:587
knowledge/tools/api-query/api-query.mjs:463 · knowledge/tools/api-query/api-query.mjs:470 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — knowledge/tools/api-query/api-query.mjs:463
knowledge/tools/api-query/api-query.mjs:361 · knowledge/tools/api-surface/lib/render-markdown.mjs:30 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — knowledge/tools/api-query/api-query.mjs:361
knowledge/tools/api-query/api-query.mjs:95 · knowledge/tools/api-surface/extract-api.mjs:136 · knowledge/tools/changeset/changeset.mjs:62 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — knowledge/tools/api-query/api-query.mjs:95
knowledge/tools/claims/lib/claims.mjs:286 · knowledge/tools/claims/lib/claims.mjs:318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — knowledge/tools/claims/lib/claims.mjs:286
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
panelModel has cyclomatic complexity 45 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:81
query has cyclomatic complexity 37 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-query/api-query.mjs:414
buildSurface has cyclomatic complexity 35 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-surface/extract-api.mjs:351
loadSurfaces has cyclomatic complexity 23 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-query/api-query.mjs:318
render has cyclomatic complexity 23 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/examples.js:406
parseMember has cyclomatic complexity 22 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-surface/lib/javap.mjs:158
render has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:391
renderCard has cyclomatic complexity 20 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/examples.js:679
render has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-query/api-query.mjs:559
injectFullItemListJsonLd has cyclomatic complexity 16 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/examples.js:118
renderTask has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-query/api-query.mjs:233
(anonymous) has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:778
parseArgs has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — knowledge/tools/api-query/api-query.mjs:90, knowledge/tools/api-surface/extract-api.mjs:132
stripCommentsAndLiterals has cyclomatic complexity 14 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/claims/lib/claims.mjs:198
membersOf has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/changeset/changeset.mjs:90
renderHighlight has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/examples.js:581
originatingBetas has cyclomatic complexity 13 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-surface/lib/stability-doc.mjs:27
findJavap has cyclomatic complexity 13 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-surface/lib/javap.mjs:48
(anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/claims/lib/claims.mjs:86
resolve has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:254
indexParameterNames has cyclomatic complexity 11 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/api-surface/lib/source-names.mjs:80
readDeclaration has cyclomatic complexity 11 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — knowledge/tools/claims/lib/claims.mjs:309
renderThumbnails has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:532
onViewerClosed has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/examples.js:308
renderPanel has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:435
Do you agree with this assessment?
R3 · Large Files2.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
knowledge/tools/api-surface/extract-api.mjs has 787 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — knowledge/tools/api-surface/extract-api.mjs:1
web/examples.js has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/examples.js:1
knowledge/tools/api-query/api-query.mjs has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — knowledge/tools/api-query/api-query.mjs:1
knowledge/tools/claims/check-claims.mjs has 463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — knowledge/tools/claims/check-claims.mjs:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage4.6 / 10Weak✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×13) — knowledge/tools/api-surface/extract-api.mjs:1, REDACTED:1, web/examples.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. 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.
`https://cdn.jsdelivr.net/npm/prismjs@1.29.0/components/prism-core.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 10 such include(s) across the repository's markup. — web-src/pages/index.html:390
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Do you agree with this assessment?
X13 · Undrained process stream5.0 / 10Adequate✓ Tool-verified
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.
The JDK merges `stderr` into `stdout` here (`redirectErrorStream(true)`), and that one stream is still a pipe — and the parent waits on `p.waitFor(…)` while nothing in this scope ever reads stdout. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the bounded wait then times out on a command that was only waiting to be read, and the output is lost. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — dev-tools/PdfRebuildOpenInAdobe.java:146
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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 (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — 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)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. 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 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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped7.7 / 10Strong✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`escAttr(SOURCE_TREE+encodeURIComponent(ref)+SOURCE_PATH)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — web/examples.js:109
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
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.
`.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — web/home.js:52
`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. — render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/GlyphFallbackLogger.java:255
`catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×8) — render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2844, render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4883, render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10738, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — knowledge/tools/claims/check-claims.mjs:98, knowledge/tools/api-surface/lib/tree.mjs:40
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. (×2) — knowledge/tools/api-query/api-query.mjs:190, dev-tools/PdfRebuildOpenInAdobe.java:115
What to do
Swallowed exception (empty catch)
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.
`debug` at line 292 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/PdfFont.java:292
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/78 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java, .mjs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention 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 retention 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.
C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 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.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — Not scored — a Maven build resolved 39 artifact(s) (6 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency does not read html yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — None of 9 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (588 value object(s))
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (32 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 32 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
P12 CI test-gate honesty — 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.
P2 Observability — This repository's JVM, JavaScript/TypeScript source (9 module(s), 982 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 4% of this repository's production lines — java (197,260 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
Banned license: org.openjdk.jmh:jmh-core — `org.openjdk.jmh:jmh-core` 1.37 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
Banned license: com.itextpdf:itext-core — `com.itextpdf:itext-core` 9.8.0 is published on Maven Central under `AGPL-3.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name web/examples.js:542— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
D11 · Test Reliability· Test declared unreliable · ×1
Test declared unreliable: declaresTestMethod knowledge/tools/claims/test/claims.test.mjs:209— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "flaky". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:181— core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:181-188 | core/src/main/java/com/demcha/compose/document/layout/definitions/PathDefinition.java:61-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:181` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:140— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:140-147 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:957-964 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1010— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1010-1017 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:84-93 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:669— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:669-676 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:698-709 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:669` 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) core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:806— core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:806-813 | core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:1025-1032 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:56— core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:56-63 | core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:158-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java: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.
Duplicated block (8 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:627— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:627-634 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxDeckAssembly.java:144-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:32— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:32-39 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:32-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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/BlueBannerLetter.java:85— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/BlueBannerLetter.java:85-92 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MinimalUnderlined.java:100-107 — 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/BlueBannerLetter.java:85` 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 `doc` to `CoverLetterDocument` in one and `CvDocument` 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:261— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:261-268 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:888-895 — 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:131— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:131-138 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:312-319 — 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:131` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionDispatcher.java:37— templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionDispatcher.java:37-44 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BlueBanner.java:150-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 `templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionDispatcher.java:37` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:737— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:737-744 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:798-805 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:737` 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, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:745` calls `lineSpacing` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:806` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:763— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:763-770 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:813-820 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:763` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:205— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:205-212 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:391-398 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:205` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:215— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:215-222 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java:349-356 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:215` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:272— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:272-279 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java:130-137 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:272` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:266— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:266-273 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:275-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:65— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:65-72 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceMasthead.java:107-114 — 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:65` 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) core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:303— core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:303-310 | core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:324-331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:240— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:240-247 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:415-422 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:239` calls `style` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:414` 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 (8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:86— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:86-93 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:77-84 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:86` 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) core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:199— core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:199-206 | core/src/main/java/com/demcha/compose/document/svg/SvgIcon.java:230-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfMetadataOptions.java:30— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfMetadataOptions.java:30-37 | core/src/main/java/com/demcha/compose/document/output/DocumentMetadata.java:32-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/src/main/java/com/demcha/compose/document/debug/snapshot/LayoutGraphSnapshotExtractor.java:298— core/src/main/java/com/demcha/compose/document/debug/snapshot/LayoutGraphSnapshotExtractor.java:298-305 | core/src/main/java/com/demcha/compose/engine/debug/LayoutInsetsSnapshot.java:28-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:942— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:942-948 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:994-1000 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:942` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:973— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:973-979 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1049-1055 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:973` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14960— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14960-14966 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16285-16291 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14960` 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:343— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:343-349 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:226-232 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (7 lines × 2) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:123— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:123-129 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:172-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:120` calls `drawable` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:171` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:51— templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:51-57 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:127-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:51` 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, `templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:50` calls `lineSpacing` and `templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:126` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:44— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:44-50 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:86-92 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:44` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:716— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:716-722 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:848-854 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:716` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:757— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:757-763 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:913-919 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:757` 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, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:912` calls `bodyStyle` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:756` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:120— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:120-127 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:108-114 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:196— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:196-202 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:178-184 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:196` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:152— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:152-158 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:129-135 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:152` 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) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:118— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:118-124 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:155-161 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:324— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:324-330 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:594-600 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 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) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:60— core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:60-66 | core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:46-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:60` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:284— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:284-290 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:316-322 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:284` 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) core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:31— core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:31-37 | core/src/main/java/com/demcha/compose/document/layout/definitions/SectionDefinition.java:31-37 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `node` to `ContainerNode` in one and `SectionNode` 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 (7 lines × 2) core/src/main/java/com/demcha/compose/engine/components/style/Margin.java:48— core/src/main/java/com/demcha/compose/engine/components/style/Margin.java:48-54 | core/src/main/java/com/demcha/compose/engine/components/style/Padding.java:34-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CenteredHeadlineLetter.java:130— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CenteredHeadlineLetter.java:130-136 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CenteredHeadline.java:221-227 — 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CenteredHeadlineLetter.java:130` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:46— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:46-52 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineText.java:48-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:798— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:798-804 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:920-926 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:841— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:841-847 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:963-969 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarIcons.java:54— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarIcons.java:54-60 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarIcons.java:49-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:73— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:73-79 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalParty.java:73-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:87— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:87-93 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalParty.java:87-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. 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) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:54— core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:54-58 | core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:40-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java: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 (5 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16692— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16692-16696 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxZoneParts.java:197-201 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16692` 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:70— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:70-74 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:120-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:744— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:744-748 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:303-307 — 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:744` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:175— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:175-179 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:265-269 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:175` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:283— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:283-288 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java:142-146 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:283` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:164— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:164-168 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:118-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:164` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:144— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:144-148 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianCards.java:107-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) core/src/main/java/com/demcha/compose/document/chart/PointMarker.java:55— core/src/main/java/com/demcha/compose/document/chart/PointMarker.java:55-59 | core/src/main/java/com/demcha/compose/document/style/ShapeOutline.java:492-496 — 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) core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:80— core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:80-84 | core/src/main/java/com/demcha/compose/document/dsl/ShapeContainerBuilder.java:376-380 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/demcha/compose/document/dsl/ShapeContainerBuilder.java:388` calls `layer` and `core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:97` 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) core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:100— core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:100-104 | core/src/main/java/com/demcha/compose/document/dsl/ShapeContainerBuilder.java:405-409 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java: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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:121— core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:121-125 | core/src/main/java/com/demcha/compose/document/dsl/ShapeContainerBuilder.java:426-430 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/dsl/LayerStackBuilder.java:121` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) core/src/main/java/com/demcha/compose/document/node/LineNode.java:238— core/src/main/java/com/demcha/compose/document/node/LineNode.java:238-242 | core/src/main/java/com/demcha/compose/document/node/ParagraphNode.java:153-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/node/LineNode.java:238` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) core/src/main/java/com/demcha/compose/document/node/LineNode.java:310— core/src/main/java/com/demcha/compose/document/node/LineNode.java:310-314 | core/src/main/java/com/demcha/compose/document/style/DocumentCornerRadius.java:156-160 — 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) core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:419— core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:419-423 | core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:113-117 — 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) core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:181— core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:181-188 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextControls.java:99-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:158— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:158-162 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:322-327 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:164— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:164-168 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:329-334 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:170— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:170-174 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:336-341 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:196— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:196-200 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:557-562 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:202— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:202-206 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:564-569 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:233— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:233-237 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:257-261 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:233` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:226— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:226-230 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:584-589 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:240— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:240-244 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:464-469 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:240` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:927— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:927-931 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1043-1047 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:927` 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 (6 lines × 2) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:182— core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:182-187 | core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:89-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:327— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:327-332 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:393-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:484— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:484-489 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:522-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/src/main/java/com/demcha/compose/document/layout/definitions/AlignDefinition.java:41— core/src/main/java/com/demcha/compose/document/layout/definitions/AlignDefinition.java:41-46 | core/src/main/java/com/demcha/compose/document/layout/definitions/HorizontalBandContentDefinition.java:52-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/definitions/AlignDefinition.java:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `node` to `AlignNode` in one and `HorizontalBandContentNode` 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 (6 lines × 2) core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:342— core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:342-347 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java:204-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:342` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:118— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:118-123 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:139-144 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:131— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:131-136 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:144-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java: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. 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 (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:354— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:354-359 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:329-334 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:354` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:140— templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:140-145 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:208-213 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:86— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:86-91 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:74-79 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java: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.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:188— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:188-193 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:163-168 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:188` 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 (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:106— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:106-111 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:93-98 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:99` calls `addSection`, `spacing` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:112` 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 × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsParties.java:97— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsParties.java:97-102 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceMasthead.java:252-257 — 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsParties.java:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:152— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:152-157 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineProposal.java:151-159 — 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:152` 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) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:577— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:577-582 | core/src/main/java/com/demcha/compose/engine/text/markdown/MarkDownParser.java:161-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 `core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:577` 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) core/src/main/java/com/demcha/compose/document/layout/DocumentNodeAdapters.java:46— core/src/main/java/com/demcha/compose/document/layout/DocumentNodeAdapters.java:46-51 | core/src/main/java/com/demcha/compose/document/layout/LayoutInsets.java:24-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDeterminism.java:44— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDeterminism.java:44-49 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxDeterminismWriter.java:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java:172— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java:172-177 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeStyle.java:50-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:219— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:219-224 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:245-250 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java` as WHOLE FILES: this scan already matched 6 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:391— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:391-396 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1145-1150 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:399— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:399-404 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1152-1157 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/SidebarPortraitLetter.java:147— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/SidebarPortraitLetter.java:147-152 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:905-911 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:181— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:181-186 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:169-174 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalGlance.java:52— templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalGlance.java:52-57 | templates/src/main/java/com/demcha/compose/document/templates/data/schedule/ScheduleDay.java:29-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalGoals.java:24— templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalGoals.java:24-29 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalScope.java:27-32 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `List<Goal>` in one and `List<Item>` 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) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:81— core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:81-89 | core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:283-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java: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 (9 lines × 2) core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:70— core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:70-78 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22707-22715 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:70` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:803— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:803-811 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:836-844 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:803` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:238— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:238-246 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWrittenTree.java:38-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java: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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/core/widgets/CardWidget.java:39— templates/src/main/java/com/demcha/compose/document/templates/core/widgets/CardWidget.java:39-47 | templates/src/main/java/com/demcha/compose/document/templates/core/widgets/CardWidget.java:66-74 — both copies are in the same file, so extract the 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 (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:150— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:150-158 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:176-184 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java` as WHOLE FILES: this scan already matched 6 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:150` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:112— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:112-120 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:221-229 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:556— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:556-564 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:605-613 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:556` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:398— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:398-406 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:434-442 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java: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 (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155-163 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:383-391 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:177— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:177-185 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:177-185 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java: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 (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsWidgets.java:113— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsWidgets.java:113-121 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceWidgets.java:140-148 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:106— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:106-114 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:143-151 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:381— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:381-389 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:680-688 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:122— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:122-130 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:458-466 — 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:122` 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:63— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:63-71 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfPolygonFragmentRenderHandler.java:35-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. Read the line range as the matched WINDOW rather than a finished unit: at `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:63` 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 `payload` to `EllipseFragmentPayload` in one and `PolygonFragmentPayload` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:158— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:158-166 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:267-275 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:158` 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) render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/helpers/PdfWatermarkRenderer.java:190— render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/helpers/PdfWatermarkRenderer.java:190-198 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:300-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 `render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/helpers/PdfWatermarkRenderer.java:190` 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 `position` to `WatermarkPosition` in one and `DocumentWatermarkPosition` 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:363— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:363-371 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:266-274 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:250— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:250-258 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:877-885 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:470— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:470-478 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:514-522 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:470` 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) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:195— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:195-203 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:253-261 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:195` 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) examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:95— examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:95-103 | examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:89-97 — 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 `examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:95` 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) examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:177— examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:177-185 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:355-363 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java: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 (9 lines × 2) examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99— examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99-107 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:145-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 `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:154` calls `accentBottom`, `spacing` and `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:108` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:818— core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:818-827 | core/src/main/java/com/demcha/compose/document/layout/definitions/ChartDefinition.java:121-130 — 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 (10 lines × 2) core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:340— core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:340-349 | core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:1052-1061 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:41— core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:41-50 | core/src/main/java/com/demcha/compose/document/node/InlineSvgRun.java:46-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:41` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) core/src/main/java/com/demcha/compose/document/table/DocumentTableCell.java:206— core/src/main/java/com/demcha/compose/document/table/DocumentTableCell.java:206-215 | core/src/main/java/com/demcha/compose/engine/components/content/table/TableCellContent.java:104-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. 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:141— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:141-150 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:155-164 — 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:141` 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:181— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:181-190 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:659-668 — 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 (10 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:74— templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:74-83 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:194-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1220— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1220-1229 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:834-843 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:696— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:696-705 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:758-767 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:696` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:713— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:713-722 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:775-784 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:713` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:151— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:151-160 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:305-314 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:151` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:476— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:476-485 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:523-532 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:476` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:114— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:114-123 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:92-101 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java` as WHOLE FILES: this scan already matched 5 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. 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:114` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:283— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:283-292 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:330-339 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:283` 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:175— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:175-184 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:152-161 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:175` 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 × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:227— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:227-236 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:190-199 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:204— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:204-213 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:196-205 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:91— core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:91-100 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22725-22734 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:91` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:263— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:263-272 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:745-754 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:300— core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:300-309 | core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:345-354 — both copies are in the same file, so extract the 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) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:282— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:282-291 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:271-280 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:282` 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) examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:401— examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:401-410 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:430-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 `examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:401` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) examples/src/main/java/com/demcha/examples/support/ReadmeBannerRenderer.java:43— examples/src/main/java/com/demcha/examples/support/ReadmeBannerRenderer.java:43-52 | examples/src/main/java/com/demcha/examples/support/ReadmeHeroRenderer.java:37-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:119— examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:119-128 | examples/src/main/java/com/demcha/examples/templates/cv/CvTemplateGalleryFileExample.java:116-125 — 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 `examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:119` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `doc` to `CoverLetterDocument` in one and `CvDocument` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) examples/src/main/java/com/demcha/examples/templates/cv/v2/CvMintEditorialCustomExample.java:47— examples/src/main/java/com/demcha/examples/templates/cv/v2/CvMintEditorialCustomExample.java:47-56 | examples/src/main/java/com/demcha/examples/templates/cv/v2/CvMintEditorialExample.java:72-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/templates/cv/v2/CvMintEditorialCustomExample.java:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
+ 2 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×20
Edited copy of a member (8 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:545— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:545-552 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:1266-1273 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:290— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:290-297 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:280-287 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1093— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1093-1100 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1176-1184 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianLines.java:116— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianLines.java:116-125 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianLines.java:182-189 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:128— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:128-135 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:135-142 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeWidgets.java:100— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeWidgets.java:100-108 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridWidgets.java:106-113 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLineStartHyphens.java:182— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLineStartHyphens.java:182-189 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:98-107 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:75— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:75-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:49-56 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:847— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:847-855 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:795-802 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/HorizontalBandContentNode.java:41— core/src/main/java/com/demcha/compose/document/layout/HorizontalBandContentNode.java:41-48 | core/src/main/java/com/demcha/compose/document/layout/HorizontalBandsNode.java:45-54 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/data/EntriesSection.java:27— templates/src/main/java/com/demcha/compose/document/templates/cv/data/EntriesSection.java:27-34 | templates/src/main/java/com/demcha/compose/document/templates/cv/data/RowsSection.java:36-44 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialWidgets.java:182— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialWidgets.java:182-189 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineWidgets.java:168-177 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/src/main/java/com/demcha/compose/document/style/DocumentFlowWidth.java:41— core/src/main/java/com/demcha/compose/document/style/DocumentFlowWidth.java:41-49 | templates/src/main/java/com/demcha/compose/document/templates/core/widgets/CardWidget.java:109-116 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CenteredHeadline.java:205— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CenteredHeadline.java:205-212 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:341-348 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:168— core/src/main/java/com/demcha/compose/document/layout/RowSlots.java:168-175 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22754-22761 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:288— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:288-295 | render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/GlyphFallbackLogger.java:241-249 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeStyles.java:305— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeStyles.java:305-312 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailStyles.java:160-167 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianWidgets.java:67— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianWidgets.java:67-74 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoWidgets.java:36-43 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:688— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:688-696 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:755-762 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:949— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:949-956 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:406-413 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×19
Edited copy of a member (14 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShadingSupport.java:117— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShadingSupport.java:117-130 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShadingSupport.java:133-150 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:46— core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:46-59 | core/src/main/java/com/demcha/compose/document/node/SectionNode.java:58-72 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) core/src/main/java/com/demcha/compose/document/node/LayerStackNode.java:47— core/src/main/java/com/demcha/compose/document/node/LayerStackNode.java:47-60 | core/src/main/java/com/demcha/compose/document/node/ShapeContainerNode.java:89-112 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:52— core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:52-65 | core/src/main/java/com/demcha/compose/document/layout/definitions/SectionDefinition.java:52-65 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) examples/src/main/java/com/demcha/examples/support/ShowcaseSync.java:617— examples/src/main/java/com/demcha/examples/support/ShowcaseSync.java:617-635 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:1054-1067 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:141— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:141-154 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:173-188 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:88— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:88-103 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:110-123 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/core/text/MarkdownInline.java:66— templates/src/main/java/com/demcha/compose/document/templates/core/text/MarkdownInline.java:66-82 | templates/src/main/java/com/demcha/compose/document/templates/core/text/MarkdownInline.java:115-128 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:159— templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:159-172 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:198-213 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/data/SkillGroup.java:34— templates/src/main/java/com/demcha/compose/document/templates/cv/data/SkillGroup.java:34-48 | templates/src/main/java/com/demcha/compose/document/templates/cv/data/SkillsSection.java:27-40 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:233— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:233-246 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWrittenTree.java:33-46 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/components/LabelValueRenderer.java:35— templates/src/main/java/com/demcha/compose/document/templates/cv/components/LabelValueRenderer.java:35-48 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:83-101 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfHeaderFooterOptions.java:58— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfHeaderFooterOptions.java:58-71 | core/src/main/java/com/demcha/compose/document/output/DocumentHeaderFooter.java:90-104 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxFontMapping.java:58— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxFontMapping.java:58-71 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxFontMapping.java:80-93 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1216— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1216-1229 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:830-843 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:651— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:651-664 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:393-412 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:114— examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:114-128 | examples/src/main/java/com/demcha/examples/templates/cv/CvTemplateGalleryFileExample.java:112-125 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:304— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:304-318 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:410-423 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:198— examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:198-211 | examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:236-249 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
ClassTooLong: DocxLayoutMetrics render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:53— ClassTooLong — 1008 significant lines (blank, comment-only and punctuation-only lines excluded), 110 methods. The bar is 400 significant lines; this is 608 over it, 2.52× 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: LayoutCompiler core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:27— ClassTooLong — 924 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 524 over it, 2.31× 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: ParagraphWrapping core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:30— ClassTooLong — 788 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 388 over it, 1.97× 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: TextFlowSupport core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:35— ClassTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 296 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DocxNativeCharts render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:71— ClassTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 263 over it, 1.66× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MintEditorial templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:131— ClassTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 234 over it, 1.59× 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: SidebarPortrait templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:79— ClassTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 209 over it, 1.52× 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: MonogramSidebar templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:71— ClassTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 155 over it, 1.39× 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: PdfFixedLayoutBackend render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:55— ClassTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 148 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TableLayoutSupport core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:31— ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 113 over it, 1.28× 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: DocumentSession core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:70— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 400 significant lines; this is 103 over it, 1.26× 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: DocxDrawingAnchors render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:81— ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 58 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EngineeringResume templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:48— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DocxTimelineRails render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:70— ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TimelineMinimal templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:68— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NodeDefinitionSupport core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:29— ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 38 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PptxFixedLayoutBackend render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:98— ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 5 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SvgIconReader core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:37— ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 1 over it, 1.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×17
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:216— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:216-230 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:234-253 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:114— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:114-128 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:135-149 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:904— core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:904-919 | core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:935-949 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsClosing.java:146— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsClosing.java:146-160 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsSettlement.java:81-98 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:170— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:170-184 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:260-275 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:695— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:695-709 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:757-771 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:46— templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:46-63 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/ProjectRenderer.java:123-137 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:207— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:207-221 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:185-199 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:624— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:624-638 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:641-655 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:555— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:555-569 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:604-618 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:168— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:168-182 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:276-290 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:2312— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:2312-2326 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:2357-2371 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:972— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:972-986 | core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:994-1008 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/core/widgets/AccentStrip.java:116— templates/src/main/java/com/demcha/compose/document/templates/core/widgets/AccentStrip.java:116-130 | templates/src/main/java/com/demcha/compose/document/templates/core/widgets/Divider.java:138-157 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) examples/src/main/java/com/demcha/examples/features/text/HebrewInvoiceExample.java:169— examples/src/main/java/com/demcha/examples/features/text/HebrewInvoiceExample.java:169-183 | examples/src/main/java/com/demcha/examples/features/text/HebrewInvoiceExample.java:186-202 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:177— examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:177-191 | examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:482-497 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) examples/src/main/java/com/demcha/examples/templates/cv/v2/CharcoalGoldExample.java:34— examples/src/main/java/com/demcha/examples/templates/cv/v2/CharcoalGoldExample.java:34-48 | examples/src/main/java/com/demcha/examples/templates/cv/v2/TerracottaRailExample.java:34-48 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
TooManyMethods: DocxSemanticBackend render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:202— TooManyMethods — 782 methods. The bar is 30 methods; this is 752 over it, 26.07× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (REDACTED) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: DocxLayoutMetrics render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:53— TooManyMethods — 110 methods. The bar is 30 methods; this is 80 over it, 3.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractFlowBuilder core/src/main/java/com/demcha/compose/document/dsl/AbstractFlowBuilder.java:28— TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: DocumentSession core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:70— TooManyMethods — 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ParagraphBuilder core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:44— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: RichText core/src/main/java/com/demcha/compose/document/dsl/RichText.java:43— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ShapeContainerBuilder core/src/main/java/com/demcha/compose/document/dsl/ShapeContainerBuilder.java:29— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: RowBuilder core/src/main/java/com/demcha/compose/document/dsl/RowBuilder.java:32— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: TextFlowSupport core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:35— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: TableLayoutSupport core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:31— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Template templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:351— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TableBuilder core/src/main/java/com/demcha/compose/document/dsl/TableBuilder.java:24— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ParagraphWrapping core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:30— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LineBuilder core/src/main/java/com/demcha/compose/document/dsl/LineBuilder.java:17— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: DocxTimelineRails render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:70— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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: ListBuilder core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java:19— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/pom.xml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×16
Edited copy of a member (11 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12374— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12374-12387 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19236-19246 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:73— templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:73-83 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:112-125 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:244— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:244-254 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:279-289 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:273— core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:273-283 | core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:286-298 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:277— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:277-287 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:267-277 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoClosing.java:114— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoClosing.java:114-124 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoClosing.java:128-138 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:1183— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:1183-1193 | core/src/main/java/com/demcha/compose/document/node/InlineRun.java:40-53 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5182— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5182-5193 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5271-5281 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:909— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:909-919 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:1067-1077 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfWatermarkOptions.java:45— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfWatermarkOptions.java:45-55 | core/src/main/java/com/demcha/compose/document/output/DocumentWatermark.java:47-57 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/src/main/java/com/demcha/compose/document/showcase/FontShowcase.java:39— core/src/main/java/com/demcha/compose/document/showcase/FontShowcase.java:39-49 | core/src/main/java/com/demcha/compose/document/showcase/FontShowcase.java:57-67 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:239— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:239-249 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:251-261 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14338— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14338-14348 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxZoneParts.java:132-142 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:755— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:755-766 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:544-554 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:256— examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:256-266 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:268-279 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:146— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:146-156 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckPptxExample.java:31-41 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×16
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:68— core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:68-75 | core/src/main/java/com/demcha/compose/document/layout/InlineLayoutToken.java:84-90 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/svg/SvgStyles.java:127— core/src/main/java/com/demcha/compose/document/svg/SvgStyles.java:127-133 | core/src/main/java/com/demcha/compose/document/svg/SvgStyles.java:145-157 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianCards.java:57— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianCards.java:57-66 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianSettlement.java:58-64 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredSettlement.java:115— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredSettlement.java:115-121 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredWidgets.java:75-85 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/payloads/ResolvedSvgLayer.java:53— core/src/main/java/com/demcha/compose/document/layout/payloads/ResolvedSvgLayer.java:53-60 | core/src/main/java/com/demcha/compose/document/layout/payloads/PathFragmentPayload.java:57-63 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:401— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:401-412 | core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:426-432 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:244— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:244-250 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:152-159 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/node/ListMarker.java:198— core/src/main/java/com/demcha/compose/document/node/ListMarker.java:198-205 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:549-555 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:83— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:83-89 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:93-99 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:208— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:208-214 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:263-273 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:231— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:231-237 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:136-143 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/chart/ChartData.java:111— core/src/main/java/com/demcha/compose/document/chart/ChartData.java:111-117 | core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:799-805 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/LayerStackGeometry.java:66— core/src/main/java/com/demcha/compose/document/layout/LayerStackGeometry.java:66-72 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceWidgets.java:151-157 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:269— examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:269-275 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseIcons.java:75-81 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:447— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:447-453 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:666-672 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:92— examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:92-98 | examples/src/main/java/com/demcha/examples/features/navigation/ContainerBookmarkExample.java:82-88 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
FileTooLong: docx/DocxSemanticBackend.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java— FileTooLong — 11252 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10752 over it, 22.50× 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: docx/DocxLayoutMetrics.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java— FileTooLong — 1036 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: DocxLayoutMetrics (53-2399). The bar is 500 significant lines; this is 536 over it, 2.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: layout/LayoutCompiler.java core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java— FileTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: LayoutCompiler (27-1476). The bar is 500 significant lines; this is 443 over it, 1.89× 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: layout/ParagraphWrapping.java core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java— FileTooLong — 804 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: ParagraphWrapping (30-1219). The bar is 500 significant lines; this is 304 over it, 1.61× 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: layout/TextFlowSupport.java core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TextFlowSupport (35-1152). The bar is 500 significant lines; this is 216 over it, 1.43× 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: docx/DocxNativeCharts.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java— FileTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: DocxNativeCharts (71-1068). The bar is 500 significant lines; this is 212 over it, 1.42× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: presets/MintEditorial.java templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java— FileTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: MintEditorial (131-1365). The bar is 500 significant lines; this is 172 over it, 1.34× 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: presets/SidebarPortrait.java templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java— FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: SidebarPortrait (79-1149). The bar is 500 significant lines; this is 140 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pdf/PdfFixedLayoutBackend.java render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java— FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: PdfFixedLayoutBackend (55-1037). The bar is 500 significant lines; this is 84 over it, 1.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: presets/MonogramSidebar.java templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: MonogramSidebar (71-963). The bar is 500 significant lines; this is 76 over it, 1.15× 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: api/DocumentSession.java core/src/main/java/com/demcha/compose/document/api/DocumentSession.java— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: DocumentSession (70-1541). The bar is 500 significant lines; this is 42 over it, 1.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 39 over it, 1.08× 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: layout/TableLayoutSupport.java core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TableLayoutSupport (31-905). The bar is 500 significant lines; this is 31 over it, 1.06× 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: web/examples.js web/examples.js— FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 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.
FileTooLong: api-surface/extract-api.mjs knowledge/tools/api-surface/extract-api.mjs— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Hotspot: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:9294— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java changed 270 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in DocxSemanticBackend.writePanelPiece at line 9294. 239 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:940— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java changed 62 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in DocxLayoutMetrics.lineHeight at line 940. 54 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:446— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DocxDrawingAnchors.endSection at line 446. 18 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:392— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in DocxLayerColumns.flow at line 392. 10 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java`: 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: core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:235— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in LayoutCompiler.compileComposite at line 235. 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-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java`: 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: render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:326— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in PdfParagraphFragmentRenderHandler.renderLine at line 326. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java`: 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: render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:186— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in PdfTableRowFragmentRenderHandler.renderCellText at line 186. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java`: 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: scripts/docx-visual/edit-protocol-libreoffice.py scripts/docx-visual/edit-protocol-libreoffice.py:1417— scripts/docx-visual/edit-protocol-libreoffice.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in edit-protocol-libreoffice.main at line 1417. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- scripts/docx-visual/edit-protocol-libreoffice.py`: 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: knowledge/tools/api-surface/extract-api.mjs knowledge/tools/api-surface/extract-api.mjs:351— knowledge/tools/api-surface/extract-api.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in extract-api.buildSurface at line 351. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- knowledge/tools/api-surface/extract-api.mjs`: 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: knowledge/tools/api-query/api-query.mjs knowledge/tools/api-query/api-query.mjs:233— knowledge/tools/api-query/api-query.mjs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in api-query.renderTask at line 233. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- knowledge/tools/api-query/api-query.mjs`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:188— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in DocxPageMarginSections.plan at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:137— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in DocxGrownLines.reachOf at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:140— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Found.look at line 140. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java`: 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: web/examples.js web/examples.js:679— web/examples.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in examples.renderCard at line 679. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- web/examples.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×14
Edited copy of a member (10 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/definitions/PageFieldDefinition.java:51— core/src/main/java/com/demcha/compose/document/layout/definitions/PageFieldDefinition.java:51-60 | core/src/main/java/com/demcha/compose/document/layout/definitions/PageReferenceDefinition.java:39-50 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:62— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:62-73 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:103-112 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java:185— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java:185-197 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java:211-220 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:107— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:107-116 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionSettlement.java:66-75 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/src/main/java/com/demcha/compose/document/node/PageFieldNode.java:46— core/src/main/java/com/demcha/compose/document/node/PageFieldNode.java:46-55 | core/src/main/java/com/demcha/compose/document/node/PageReferenceNode.java:43-54 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:377— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:377-386 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseBody.java:212-221 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:43— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:43-52 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldWidgets.java:85-94 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1111— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1111-1120 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1122-1131 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:227— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:227-236 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:291-300 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) examples/src/main/java/com/demcha/examples/templates/proposal/CinematicProposalFileExample.java:198— examples/src/main/java/com/demcha/examples/templates/proposal/CinematicProposalFileExample.java:198-207 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltStyles.java:473-482 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:531— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:531-541 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:485-494 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:483— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:483-493 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:438-447 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:694— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:694-704 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:748-757 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:95— examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:95-104 | examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:192-203 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×14
Edited copy of a member (12 corresponding lines) render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/helpers/PdfWatermarkRenderer.java:186— render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/helpers/PdfWatermarkRenderer.java:186-198 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:297-308 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:62— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:62-73 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfPolygonFragmentRenderHandler.java:34-45 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseMasthead.java:202— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseMasthead.java:202-213 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java:153-165 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:103— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:103-114 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:140-151 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsMain.java:122— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsMain.java:122-134 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:109-120 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:1076— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:1076-1093 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:1145-1156 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:273— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:273-284 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailProjects.java:47-59 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:119— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:119-132 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:171-182 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:326— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:326-340 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:358-369 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/PdfFont.java:86— render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/PdfFont.java:86-97 | render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/PdfFont.java:288-299 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseClosing.java:138— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseClosing.java:138-151 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioWidgets.java:108-119 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:190— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:190-201 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:216-227 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:183— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:183-195 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:215-226 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:893— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:893-904 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:913-924 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
R4 · Test Coverage· No test reaches this file · ×13
No test reaches this file knowledge/tools/api-surface/extract-api.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/examples.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/routing/check-routes.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/changeset/changeset.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/bundle/build-bundle.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/api-surface/lib/source-names.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/bundle/lib/zip-write.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/api-surface/lib/provenance.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/api-surface/lib/render-markdown.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/api-surface/lib/zip.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file knowledge/tools/api-surface/check-stability-doc.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file web/home.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Duplicated block (11 lines × 2) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfProtectionOptions.java:46— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfProtectionOptions.java:46-56 | core/src/main/java/com/demcha/compose/document/output/DocumentProtection.java:48-58 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfProtectionOptions.java` and `core/src/main/java/com/demcha/compose/document/output/DocumentProtection.java` 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. 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 (11 lines × 2) core/src/main/java/com/demcha/compose/document/node/PathNode.java:75— core/src/main/java/com/demcha/compose/document/node/PathNode.java:75-85 | core/src/main/java/com/demcha/compose/document/style/ShapeOutline.java:174-184 — 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 (11 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPng.java:30— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPng.java:30-40 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java:180-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 (11 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:137— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:137-147 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:475-485 — 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 (11 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:138— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:138-148 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:187-197 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java:341— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java:341-351 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:175-185 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:172` calls `spacing`, `accentLeft`, `padding` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java:340` 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) templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:81— templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:81-91 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:126-136 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java: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 (11 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:159— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:159-169 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:145-155 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:159` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:319— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:319-329 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:204-214 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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.
Duplicated block (11 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:256— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:256-266 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:292-302 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 (11 lines × 2) examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:108— examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:108-118 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:765-775 — 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 (11 lines × 2) examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:315— examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:315-325 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:417-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:428` calls `valueLabels` and `examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:326` 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.
Repeated repair: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java:458— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java changed 15 times in last 90 days and 14 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 DocxDrawings.drawing at line 458), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): draw a dashed line or path dashed (#1028)”; “fix(docx): draw a timeline's rail as a bar LibreOffice draws upright, held by the entry it starts in (#1002)”; “fix(docx): stand a badge and its initials where the page draws them (#941)”; “fix(docx): stack drawings in Word as the page paints them (#922)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java:211— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Builder.addTo at line 211), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): write the shaded spaces closing a paragraph as no-break spaces, so Word fills them (#1032)”; “fix(docx): mark the Word export's 2.5 API @Beta where it was unmarked (#1018)”; “fix(docx): name every page a page-margin note is about (#954)”; “fix(docx): name what a table's cell is composed of by its cell in the report (#953)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxExportReport.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java:491— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is DocxFontTable.collectFonts at line 491), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): write the document when a registered family's classpath face cannot be read (#1049)”; “fix(docx): ask for embedded fonts in the settings so LibreOffice keeps the shipped faces on save (#1007)”; “fix(docx): grow a Word list's item where its face holds its marker (#958)”; “fix(docx): grow lines with their text where they are as tall as their faces' own (#955)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java`: 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: core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:417— core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java changed 7 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 13 (its worst body is NodeDefinitionSupport.measureRow at line 417), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(layout): keep the size of a picture or shape composed in a table cell (#928)”; “fix(layout): honour a margin on composed table-cell content in both passes”; “fix(engine): cap a fixed-width flow at the column of the page it lands on”; “fix(layout): read the anchor when placing a composed cell's child”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java`: 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: core/src/main/java/com/demcha/compose/document/api/DocumentPageZones.java core/src/main/java/com/demcha/compose/document/api/DocumentPageZones.java:100— core/src/main/java/com/demcha/compose/document/api/DocumentPageZones.java 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 7 (its worst body is DocumentPageZones.placeZone at line 100), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): write top and bottom margins that change from page to page as Word sections (#951)”; “fix(api): resolve body anchors inside a page zone”; “fix(api): refuse zone content that splits past the band”; “fix(api): give the page field a layout definition of its own”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- core/src/main/java/com/demcha/compose/document/api/DocumentPageZones.java`: 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: render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java:67— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java 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 12 (its worst body is PptxParagraphFragmentRenderHandler.renderLine at line 67), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): seat text off its baseline as the page does and hang text below its band (#787)”; “fix(pptx): let a chip read the same on a slide as it does on the page (#559)”; “fix(pdf): resolve a chip against its own base, not against having one (#553)”; “fix(render): let a reordered line's frames say which way they read — and a chip keep its meaning (#548)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextBands.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextBands.java:70— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextBands.java changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is DocxTextBands.segments at line 70), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): name what a text header or footer shows otherwise in Word (#921)”; “fix(docx): raise a line Word sets low into the space above it, where both editors keep it (#875)”; “fix(docx): stand a page zone's text on the page's baseline in Word (#867)”; “fix(docx): stand text on the page's baseline in Word's exact lines (#789)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextBands.java`: 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: templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:95— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is TerracottaRailAside.blocks at line 95), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(templates): preserve semantic text when applying letter spacing (#682)”; “fix(templates): dial the number the sheet printed, not one like it”; “fix(templates): put the Terracotta Rail contact rows on one axis (#625)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java`: 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: knowledge/tools/routing/check-routes.mjs knowledge/tools/routing/check-routes.mjs:140— knowledge/tools/routing/check-routes.mjs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is check-routes.checkAnchorRef at line 140), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(knowledge): stop the gate and the CLI failing open on their edges”; “fix(knowledge): resolve a citation against a real path, inside the repository”; “fix(knowledge): close three ways the surface could lie without failing”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- knowledge/tools/routing/check-routes.mjs`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTableSplit.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTableSplit.java:73— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTableSplit.java changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is DocxTableSplit.rowStarting at line 73), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): bookmark a block of drawings alone where its first drawing is anchored (#968)”; “fix(docx): end a page-margin section at a panel's cut (#963)”; “fix(docx): cut a panel whose table runs over pages into a table a page (#962)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTableSplit.java`: 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: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java:220— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java 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 9 (its worst body is DocxShapePictures.unitSegments at line 220), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(docx): name inline picture losses and write a %N marker as text (#937)”; “fix(docx): name in the report what the export draws as a picture or draws without (#900)”; “fix(docx): set a shape container's stacked lines in from its outline, hold an empty row cell to a hairline, and stand inline shapes where the page puts them (#816)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 10:53:30 +00:00' --until='2026-11-11 10:53:30 +00:00' --full-history --no-merges -- render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×11
Members sharing a duplicated core (4 members, 50+ identical tokens) core/src/main/java/com/demcha/compose/document/layout/BoxConstraints.java:23— core/src/main/java/com/demcha/compose/document/layout/BoxConstraints.java:23-30 | core/src/main/java/com/demcha/compose/document/layout/MeasureResult.java:13-20 | core/src/main/java/com/demcha/compose/document/node/ListNode.java:83-105 | core/src/main/java/com/demcha/compose/document/node/SpacerNode.java:29-42 — 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:160— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:160-196 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:162-198 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:186-222 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:279-315 — 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:246— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:246-261 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1298-1314 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1319-1335 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:728-743 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGold.java:248— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGold.java:248-260 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebar.java:226-238 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebar.java:255-267 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadline.java:248-260 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:26— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:26-35 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:325-334 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:318-327 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineText.java:25-34 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:232— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:232-244 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulse.java:206-218 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRail.java:262-274 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGrid.java:215-227 — 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:220— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:220-243 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:95-120 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:159-185 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionClosing.java:267-289 — 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:246— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:246-254 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:123-131 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:188-196 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionClosing.java:292-300 — 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) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:72— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:72-102 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:62-89 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:73-103 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceMasthead.java:103-132 — 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) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:49— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:49-162 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:54-264 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:40-177 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:98-384 — 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) examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:46— examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:46-311 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:91-105 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:107-121 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:764-778 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×11
Edited copy of a member (16 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java:303— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxShapePictures.java:303-320 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShapeGeometry.java:148-163 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:73— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:73-88 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformLines.java:73-94 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:9729— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:9729-9744 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10477-10493 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:98— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:98-113 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:84-101 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:147— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:147-162 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:164-179 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:137— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:137-152 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:186-203 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:117— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:117-138 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:154-169 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:41— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:41-56 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:68-83 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:712— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:712-727 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:774-789 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingInvoice.java:158— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingInvoice.java:158-173 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioInvoice.java:184-200 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) examples/src/main/java/com/demcha/examples/features/text/LetterSpacingExample.java:125— examples/src/main/java/com/demcha/examples/features/text/LetterSpacingExample.java:125-141 | examples/src/main/java/com/demcha/examples/features/text/LetterSpacingExample.java:143-158 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×11
Edited copy of a member (9 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19866— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19866-19874 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19877-19885 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:166— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:166-174 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:364-373 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:260— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:260-268 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:887-895 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:322— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:322-330 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:590-600 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22662— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22662-22670 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:23069-23078 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/LineBuilder.java:449— core/src/main/java/com/demcha/compose/document/dsl/LineBuilder.java:449-457 | core/src/main/java/com/demcha/compose/document/dsl/LineBuilder.java:459-467 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:142— core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:142-150 | core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:183-191 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) core/src/main/java/com/demcha/compose/document/node/CanvasChild.java:27— core/src/main/java/com/demcha/compose/document/node/CanvasChild.java:27-35 | core/src/main/java/com/demcha/compose/document/node/InlineShapeRun.java:50-60 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingMasthead.java:189— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingMasthead.java:189-197 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltHeader.java:200-209 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:507— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:507-515 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:584-594 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:138— examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:138-146 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:148-158 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:54— core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:54-65 | core/src/main/java/com/demcha/compose/document/layout/definitions/SectionDefinition.java:54-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/definitions/ContainerDefinition.java:54` 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 (12 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:63— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:63-74 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:96-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:279— templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:279-290 | templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:315-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:279` 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) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:172— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:172-183 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:221-232 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:143— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:143-154 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:334-345 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java: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 (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:169— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:169-180 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:183-194 — both copies are in the same file, so extract the 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 (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java:202— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java:202-213 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOps.java:252-263 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:947— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:947-958 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1090-1101 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:167— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:167-178 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:204-215 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:167` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:225— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:225-236 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:263-274 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:225` 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) examples/src/main/java/com/demcha/examples/support/OrangeOpsSampleData.java:44— examples/src/main/java/com/demcha/examples/support/OrangeOpsSampleData.java:44-55 | examples/src/main/java/com/demcha/examples/support/TerracottaRailSampleData.java:46-57 — 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.
Swallowed exception (caught, then discarded) render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/GlyphFallbackLogger.java:255— `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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2844— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4883— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10738— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12708— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13332— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14628— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20057— `catch (RuntimeException)` 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20118— `catch (RuntimeException)` 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) knowledge/tools/claims/check-claims.mjs:98— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) knowledge/tools/api-surface/lib/tree.mjs:40— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
MethodTooLong: LayoutCompiler.compileNodeInFixedSlot core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:938— MethodTooLong — compileNodeInFixedSlot runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Template.compose templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:124— MethodTooLong — compose runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: LayoutCompiler.compileHorizontalRow core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:479— MethodTooLong — compileHorizontalRow runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LayoutCompiler.compileComposite core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:235— MethodTooLong — compileComposite runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: BarChartLayout.resolveHorizontal core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:164— MethodTooLong — resolveHorizontal runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Template.compose templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:121— MethodTooLong — compose runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SplittableLeafCompiler.compile core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:50— MethodTooLong — compile runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ParagraphWrapping.toInlineParagraphLine core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:731— MethodTooLong — toInlineParagraphLine runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: PdfParagraphFragmentRenderHandler.renderLine render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:326— MethodTooLong — renderLine runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: StackedLayerCompiler.compile core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:49— MethodTooLong — compile runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×10
Edited copy of a member (4 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:229— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:229-234 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java:168-171 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantStyles.java:140— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantStyles.java:140-143 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformStyles.java:331-334 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/DocumentLayoutPassContext.java:115— core/src/main/java/com/demcha/compose/document/layout/DocumentLayoutPassContext.java:115-118 | core/src/main/java/com/demcha/compose/document/snapshot/PageIndex.java:71-74 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredText.java:38— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredText.java:38-41 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformText.java:44-47 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:87— core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:87-90 | core/src/main/java/com/demcha/compose/document/node/SectionNode.java:106-109 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:554— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:554-557 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2188-2191 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:643— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:643-646 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:700-703 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:361— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:361-365 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:262-265 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:109— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldMain.java:109-112 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:227-231 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:880— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:880-883 | examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:526-529 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×9
Edited copy of a member (13 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceData.java:43— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceData.java:43-55 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalData.java:43-55 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:277— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:277-289 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:152-166 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:213— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:213-226 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:236-248 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxEllipseFragmentRenderHandler.java:35— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxEllipseFragmentRenderHandler.java:35-47 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxPolygonFragmentRenderHandler.java:34-47 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18757— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18757-18769 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22272-22284 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfRenderEnvironment.java:341— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfRenderEnvironment.java:341-353 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxRenderEnvironment.java:575-587 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:27— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:27-39 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:27-39 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/core/identity/Masthead.java:121— templates/src/main/java/com/demcha/compose/document/templates/core/identity/Masthead.java:121-133 | templates/src/main/java/com/demcha/compose/document/templates/core/text/TextOrnaments.java:127-139 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:856— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:856-868 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:845-857 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×9
Edited copy of a member (18 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxInkOutline.java:141— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxInkOutline.java:141-159 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java:100-117 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:467— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:467-485 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:511-528 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/definitions/CanvasLayerDefinition.java:50— core/src/main/java/com/demcha/compose/document/layout/definitions/CanvasLayerDefinition.java:50-76 | core/src/main/java/com/demcha/compose/document/layout/definitions/LayerStackDefinition.java:39-56 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:62— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:62-85 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:111-128 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:235— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:235-255 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:410-427 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:161— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:161-178 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:195-215 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:223— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfDocumentPostProcessor.java:223-243 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxDeckAssembly.java:174-191 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) core/src/main/java/com/demcha/compose/document/backend/fixed/BackendProviders.java:107— core/src/main/java/com/demcha/compose/document/backend/fixed/BackendProviders.java:107-124 | core/src/main/java/com/demcha/compose/document/backend/semantic/SemanticBackendProviders.java:79-96 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionAllocation.java:72— templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionAllocation.java:72-89 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionLookup.java:23-40 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×9
Edited copy of a member (6 corresponding lines) core/src/main/java/com/demcha/compose/engine/components/style/Margin.java:40— core/src/main/java/com/demcha/compose/engine/components/style/Margin.java:40-45 | core/src/main/java/com/demcha/compose/engine/components/style/Padding.java:26-31 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14653— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14653-14661 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:23782-23787 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalFooter.java:28— templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalFooter.java:28-33 | templates/src/main/java/com/demcha/compose/document/templates/data/schedule/ScheduleAssignment.java:33-39 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) core/src/main/java/com/demcha/compose/document/svg/SvgIcon.java:289— core/src/main/java/com/demcha/compose/document/svg/SvgIcon.java:289-294 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/data/CoverLetterDocument.java:46-51 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:345— core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:345-351 | core/src/main/java/com/demcha/compose/document/dsl/RichText.java:246-251 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:681— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:681-686 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:635-640 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:225— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:225-230 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:790-796 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:302— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:302-307 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:612-617 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:634— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:634-639 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:863-868 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (6 lines × 3) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:85— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:85-90 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:121-126 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:457-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxLineFragmentRenderHandler.java:55— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxLineFragmentRenderHandler.java:55-60 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:124-129 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:173-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:194— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:194-199 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:268-273 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMasthead.java:184-189 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:540— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:540-545 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:755-760 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:588-593 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:540` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineAside.java:108— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineAside.java:108-113 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:123-128 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:263-268 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineAside.java:108` 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155-160 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:309-314 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:383-388 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:53— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:53-58 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceServiceLines.java:67-72 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalBrand.java:33-38 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:53` 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, `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceServiceLines.java:64` calls `requireNonNullElse` and `templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalBrand.java:31` 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:620— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:620-625 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:669-674 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:985-990 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:127— examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:127-132 | examples/src/main/java/com/demcha/examples/features/text/HebrewInvoiceExample.java:96-101 | examples/src/main/java/com/demcha/examples/features/text/WorldScriptsExample.java:69-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×8
Edited copy of a member (17 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:771— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:771-787 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:797-817 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltHeader.java:104— templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltHeader.java:104-120 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltHeader.java:177-193 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:79— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:79-97 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:81-97 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:58— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:58-74 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:91-107 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:197— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:197-213 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:397-416 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13997— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13997-14015 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxZoneParts.java:213-229 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:144— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:144-160 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineProposal.java:141-162 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:153— templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:153-169 | templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:202-218 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×8
Edited copy of a member (5 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5957— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5957-5961 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5967-5971 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxBarcodeFragmentRenderHandler.java:86— render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxBarcodeFragmentRenderHandler.java:86-90 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java:113-117 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1190— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1190-1194 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:626-631 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) core/src/main/java/com/demcha/compose/document/chart/ChartSize.java:73— core/src/main/java/com/demcha/compose/document/chart/ChartSize.java:73-77 | examples/src/main/java/com/demcha/examples/support/theme/SpacingScale.java:90-95 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:176— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:176-181 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:375-379 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java:459— core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java:459-465 | core/src/main/java/com/demcha/compose/document/style/DocumentSpacing.java:20-24 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailStyles.java:169— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailStyles.java:169-176 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantStyles.java:171-175 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) examples/src/main/java/com/demcha/examples/support/PaymentsInvoiceSampleData.java:80— examples/src/main/java/com/demcha/examples/support/PaymentsInvoiceSampleData.java:80-85 | examples/src/main/java/com/demcha/examples/support/WorkspaceInvoiceSampleData.java:77-81 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×8
Edited copy of a member (3 corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/SectionBuilder.java:83— core/src/main/java/com/demcha/compose/document/dsl/SectionBuilder.java:83-87 | core/src/main/java/com/demcha/compose/document/dsl/PageFlowBuilder.java:25-27 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxCellDrawings.java:138— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxCellDrawings.java:138-141 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5868-5870 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20621— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20621-20624 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:115-117 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) core/src/main/java/com/demcha/compose/document/node/ListNode.java:133— core/src/main/java/com/demcha/compose/document/node/ListNode.java:133-136 | core/src/main/java/com/demcha/compose/document/node/ParagraphNode.java:252-254 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:205— examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:205-207 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltStyles.java:360-363 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) core/src/main/java/com/demcha/compose/document/node/RowNode.java:201— core/src/main/java/com/demcha/compose/document/node/RowNode.java:201-204 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java:150-152 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:206— examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:206-208 | examples/src/main/java/com/demcha/examples/features/text/TextDirectionExample.java:125-127 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:918— examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:918-920 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:676-682 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:254— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:254-267 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:222-235 — 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:254` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ModernProfessionalLetter.java:118— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ModernProfessionalLetter.java:118-131 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ModernProfessional.java:156-169 — 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: the declarations holding them bind `doc` to `CoverLetterDocument` in one and `CvDocument` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (14 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:248— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:248-261 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:730-743 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:125— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:125-138 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceInvoice.java:123-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:282— core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:282-295 | core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:327-340 — both copies are in the same file, so extract the 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 (14 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDeterminism.java:59— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDeterminism.java:59-72 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxDeterminismWriter.java:56-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:191— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:191-204 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:227-240 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 72 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:191` 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) examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:73— examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:73-86 | examples/src/main/java/com/demcha/examples/features/navigation/ContainerBookmarkExample.java:63-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1020— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1020-1033 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:99-111 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 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 `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1020` 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, `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:114` calls `height`, `bottom` and `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1035` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:405— core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:405-417 | core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:551-563 — 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 (13 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:179— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:179-191 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:244-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.
Duplicated block (13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:102— templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:102-114 | templates/src/main/java/com/demcha/compose/document/templates/cv/components/EntryCompactRenderer.java:135-147 — both copies are in the same file, so extract the 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 (13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:163— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:163-175 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:163-175 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:163` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:158— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:158-170 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceInvoice.java:160-172 — 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 (13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:127— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:127-139 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:118-130 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:309— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:309-315 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:502-508 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:72-78 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:116— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:116-124 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MinimalUnderlined.java:113-120 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ModernProfessional.java:169-175 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:116` 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165-171 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:144-150 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:132-138 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165` 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:119— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:119-125 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredMasthead.java:237-243 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformParties.java:118-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:119` 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:284— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:284-290 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:385-391 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:384-390 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:55— examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:55-61 | examples/src/main/java/com/demcha/examples/features/layout/RowFlexExample.java:48-54 | examples/src/main/java/com/demcha/examples/features/navigation/TocExample.java:58-64 — 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 `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:55` 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, `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:54` calls `parse` and `examples/src/main/java/com/demcha/examples/features/layout/RowFlexExample.java:46` 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 (7 lines × 3) examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:86— examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:86-92 | examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:106-112 | examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:136-142 — 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 `examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:114` calls `dashed` and `examples/src/main/java/com/demcha/examples/features/shapes/VectorPathExample.java:94` 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.
AC4 · Keyboard semantics· Anchor without href · ×6
Anchor without href web-src/pages/index.html:377— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href web-src/pages/index.html:378— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href web-src/pages/index.html:379— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href web/index.html:701— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href web/index.html:702— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href web/index.html:703— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×6
Edited copy of a member (29 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:114— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:114-142 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:292-324 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:178— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:178-216 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformWidgets.java:86-114 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulse.java:162— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulse.java:162-190 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGrid.java:163-199 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:482— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:482-516 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:521-549 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:68— examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterTemplateGalleryFileExample.java:68-98 | examples/src/main/java/com/demcha/examples/templates/cv/CvTemplateGalleryFileExample.java:69-97 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:172— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:172-207 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:238-266 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8–9 lines × 2) core/src/main/java/com/demcha/compose/document/layout/definitions/LayerStackDefinition.java:45— core/src/main/java/com/demcha/compose/document/layout/definitions/LayerStackDefinition.java:45-52 | core/src/main/java/com/demcha/compose/document/layout/definitions/ShapeContainerDefinition.java:59-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/definitions/LayerStackDefinition.java:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `node` to `LayerStackNode` in one and `ShapeContainerNode` 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–9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:206— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:206-213 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:475-483 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java` as WHOLE FILES: this scan already matched 6 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:206` 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–9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:419— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:419-426 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:449-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:419` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 2) examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:189— examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:189-197 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:420-427 — 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 `examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:189` 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–9 lines × 2) examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:60— examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:60-67 | examples/src/main/java/com/demcha/examples/features/shapes/LineFillExample.java:50-58 — 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 `examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/shapes/LineFillExample.java:49` calls `of` and `examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:59` 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 (8–9 lines × 2) examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:91— examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:91-99 | examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:110-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:91` 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 (5 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:161— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:161-165 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:270-274 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsMain.java:339-343 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:161` 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, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:275` calls `size` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsMain.java:344` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:144— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:144-149 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:244-248 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:349-354 — 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.
Duplicated block (5 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:152— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:152-156 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:185-189 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:543-548 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantText.java:30— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantText.java:30-34 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformText.java:30-34 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java: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 all 3 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 × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:222— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:222-226 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:271-275 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:332-336 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyAside.java:222` 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) examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:193— examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:193-197 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:423-427 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:596-600 — 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 `examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×5
Edited copy of a member (21 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:640— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:640-665 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:610-633 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:85— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsAside.java:85-107 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsMain.java:93-113 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:130— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:130-150 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:143-164 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:572— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:572-592 | core/src/main/java/com/demcha/compose/engine/text/markdown/MarkDownParser.java:153-175 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:405— examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:405-429 | examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:460-480 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×5
Edited copy of a member (22 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfGuideLinesRenderer.java:98— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfGuideLinesRenderer.java:98-119 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfGuideLinesRenderer.java:123-144 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:107— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantLines.java:107-128 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformLines.java:126-147 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:88— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:88-116 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:87-108 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:188— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:188-209 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseMasthead.java:148-170 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:247— core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:247-274 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:334-355 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×5
Edited copies of one member (3 members, 9+ corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:353— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:353-362 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:393-401 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:477-485 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2203— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2203-2211 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:626-634 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxDeckAssembly.java:143-151 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:126— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:126-134 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:142-150 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:104-112 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:632— examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:632-640 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:369-378 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarWidgets.java:145-154 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingMasthead.java:199— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingMasthead.java:199-208 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioSidebar.java:118-127 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioWidgets.java:97-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (15 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:121— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:121-135 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:98-112 — 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 (15 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:163— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:163-177 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:446-460 — 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:163` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:191— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:191-205 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:673-687 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:206` calls `jobTitle`, `isBlank` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:688` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1300— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1300-1314 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1321-1335 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1300` 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 (15 lines × 2) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10276— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10276-10290 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11887-11901 — both copies are in the same file, so extract the 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 `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10276` 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, `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10291` calls `put` and `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11902` 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 × 3) core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:395— core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:395-402 | core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:591-598 | core/src/main/java/com/demcha/compose/document/svg/SvgStyles.java:290-297 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsStyles.java:336— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsStyles.java:336-343 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeStyles.java:296-303 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridStyles.java:396-403 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeStyles.java:296` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:187— examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:187-194 | examples/src/main/java/com/demcha/examples/features/transforms/TransformsExample.java:183-190 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:414-421 — 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.
Duplicated block (8 lines × 3) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:74— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:74-82 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:101-108 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:67-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) examples/src/main/java/com/demcha/examples/flagships/BusinessReportPptxExample.java:30— examples/src/main/java/com/demcha/examples/flagships/BusinessReportPptxExample.java:30-37 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportPptxExample.java:30-37 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcasePptxExample.java:31-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (5 members, 50+ identical tokens) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:248— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:248-477 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:497-691 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:746-784 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:946-1198 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:61-183 — 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) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:536— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:536-544 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6544-6569 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6605-6616 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11591-11601 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18550-18619 — 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) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:47— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:47-58 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:26-32 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoicePaymentBlock.java:44-52 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceRecipient.java:41-50 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalParty.java:26-32 — 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) examples/src/main/java/com/demcha/examples/features/canvas/CanvasLayerExample.java:48— examples/src/main/java/com/demcha/examples/features/canvas/CanvasLayerExample.java:48-194 | examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:66-213 | examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:34-197 | examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:55-336 | examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:50-117 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×4
Edited copy of a member (34 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:272— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:272-306 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:305-338 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:89— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:89-123 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:68-101 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:219— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:219-253 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:255-288 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:105— core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:105-148 | core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:165-198 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:948— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:948-956 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1091-1099 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1133-1141 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:112— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:112-120 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:71-79 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:90-98 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java` as WHOLE FILES: this scan already matched 5 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:143— core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:143-151 | core/src/main/java/com/demcha/compose/document/api/DocumentSession.java:159-167 | core/src/main/java/com/demcha/compose/document/api/MultiSectionDocument.java:298-306 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `RenderingBody<R>` in one and `ImageRenderingBody<R>` 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 × 3) examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:292— examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:292-300 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:402-410 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:431-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.
Duplicated block (6–7 lines × 2) core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:243— core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:243-248 | core/src/main/java/com/demcha/compose/engine/text/bidi/BidiMirroring.java:34-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:243` 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–7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:155— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:155-160 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:206-212 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:155` 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–7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:217— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:217-222 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:401-407 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:217` 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 (6–7 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:90— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:90-95 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:69-75 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java` as WHOLE FILES: this scan already matched 5 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. 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java: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. 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.
Off the main sequence: graph-compose-emoji — graph-compose-emoji: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: graph-compose-fonts — graph-compose-fonts: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: graph-compose-core — graph-compose-core: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
Off the main sequence: graph-compose-render-pdf — graph-compose-render-pdf: abstractness 0.03, instability 0.20, distance 0.77 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
FunctionTooLong: gallery-viewer.createViewer REDACTED:305— FunctionTooLong — createViewer runs 381 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 281 over it, 3.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.
FunctionTooLong: extract-api.buildSurface knowledge/tools/api-surface/extract-api.mjs:351— FunctionTooLong — buildSurface runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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.
FunctionTooLong: api-query.query knowledge/tools/api-query/api-query.mjs:414— FunctionTooLong — query runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (7 members, 50+ identical tokens) core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:45— core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:45-67 | core/src/main/java/com/demcha/compose/document/layout/definitions/EllipseDefinition.java:45-68 | core/src/main/java/com/demcha/compose/document/layout/definitions/ImageDefinition.java:47-70 | core/src/main/java/com/demcha/compose/document/layout/definitions/LineDefinition.java:59-90 | core/src/main/java/com/demcha/compose/document/layout/definitions/PathDefinition.java:51-96 | core/src/main/java/com/demcha/compose/document/layout/definitions/PolygonDefinition.java:47-67 | core/src/main/java/com/demcha/compose/document/layout/definitions/ShapeDefinition.java:46-86 — These 7 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 7 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 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:126— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:126-134 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsWidgets.java:187-195 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:411-419 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseBody.java:224-232 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:330-338 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:421-429 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridWidgets.java:132-140 — These 7 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 7 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 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:60— examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:60-75 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:83-98 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:106-121 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:132-147 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:158-173 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:184-199 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:210-225 — These 7 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 7 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 7 times.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×3
Edited copy of a member (37 corresponding lines) core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:277— core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:277-313 | core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:322-365 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:188— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeAside.java:188-224 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java:371-407 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java:156— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java:156-192 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:174-216 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×3
Edited copy of a member (35 corresponding lines) core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:139— core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:139-173 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:932-975 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:233— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:233-267 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:281-319 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:49— examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:49-97 | examples/src/main/java/com/demcha/examples/features/navigation/PageReferenceExample.java:46-80 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:185— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageOne.java:185-211 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageOne.java:222-247 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:275— templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:275-300 | templates/src/main/java/com/demcha/compose/document/templates/core/identity/ContactLine.java:307-336 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:182— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:182-207 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:430-458 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:223— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:223-241 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:201-221 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:81— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:81-99 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:72-90 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:296— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:296-314 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:337-356 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×3
Edited copy of a member (28 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:209— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:209-236 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java:338-370 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:150— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:150-177 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:433-460 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:403— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:403-430 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:463-492 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoBand.java:113— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoBand.java:113-136 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoLower.java:136-160 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:314— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:314-345 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:347-370 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:80— templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:80-103 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/IconTextRow.java:125-148 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:264— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:264-286 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:166-191 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/receipt/widgets/PartyPair.java:95— templates/src/main/java/com/demcha/compose/document/templates/receipt/widgets/PartyPair.java:95-118 | templates/src/main/java/com/demcha/compose/document/templates/receipt/widgets/ReceiptFooter.java:100-122 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:113— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialProposal.java:113-135 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineProposal.java:108-132 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×3
Edited copies of one member (4 members, 9+ corresponding lines) core/src/main/java/com/demcha/compose/document/layout/definitions/AlignDefinition.java:37— core/src/main/java/com/demcha/compose/document/layout/definitions/AlignDefinition.java:37-53 | core/src/main/java/com/demcha/compose/document/layout/definitions/HorizontalBandContentDefinition.java:48-59 | core/src/main/java/com/demcha/compose/document/layout/definitions/HorizontalBandsDefinition.java:45-53 | core/src/main/java/com/demcha/compose/document/layout/definitions/LayoutAnchorDefinition.java:55-65 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:676— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:676-684 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:729-741 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:743-752 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:816-825 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:320— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:320-328 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:422-430 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:505-517 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:181-189 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×3
Edited copies of one member (3 members, 8+ corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClipInk.java:245— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClipInk.java:245-252 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClipInk.java:261-268 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClipInk.java:270-277 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:116— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:116-123 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailProjects.java:74-82 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:112-119 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:273— examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:273-280 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:477-484 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:268-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 3+ corresponding lines) · ×3
Edited copies of one member (5 members, 3+ corresponding lines) core/src/main/java/com/demcha/compose/document/node/LineNode.java:121— core/src/main/java/com/demcha/compose/document/node/LineNode.java:121-124 | core/src/main/java/com/demcha/compose/document/node/ListNode.java:169-172 | core/src/main/java/com/demcha/compose/document/node/SectionNode.java:141-144 | core/src/main/java/com/demcha/compose/document/node/ShapeNode.java:97-100 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java:145-147 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 3+ corresponding lines) core/src/main/java/com/demcha/compose/document/node/ParagraphNode.java:222— core/src/main/java/com/demcha/compose/document/node/ParagraphNode.java:222-225 | core/src/main/java/com/demcha/compose/document/node/PathNode.java:155-158 | core/src/main/java/com/demcha/compose/document/node/SectionNode.java:173-176 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java:139-141 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/StructuredProposalData.java:117-120 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 3+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:910— examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:910-912 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:668-674 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:402-404 | examples/src/main/java/com/demcha/examples/support/SiteSocialCoverRenderer.java:250-256 | examples/src/main/java/com/demcha/examples/templates/proposal/CinematicProposalFileExample.java:178-184 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Duplicated block (19 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EditorialBlueLetter.java:113— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EditorialBlueLetter.java:113-131 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:310-328 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:202— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:202-220 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:380-398 — both copies are in the same file, so extract the 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 `examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:202` 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) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:226— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:226-244 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:410-428 — both copies are in the same file, so extract the 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 `examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:226` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:126— templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:126-141 | templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:254-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. 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) templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:278— templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:278-293 | templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java:302-317 — both copies are in the same file, so extract the 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 (16 lines × 2) examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:107— examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:107-122 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:128-143 — 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 `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:107` 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 × 4) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:100— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:100-111 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:116-127 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:121-132 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:119-130 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` as WHOLE FILES: this scan already matched 4 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. 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:100` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:116` calls `spacing`, `bannerInnerPadding` and `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:99` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGold.java:249— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGold.java:249-260 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebar.java:227-238 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebar.java:256-267 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadline.java:249-260 — 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. 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 × 4) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:233— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:233-244 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulse.java:207-218 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRail.java:263-274 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGrid.java:216-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 7) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:127— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:127-134 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsWidgets.java:188-195 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:412-419 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseBody.java:225-232 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailAside.java:331-338 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:422-429 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridWidgets.java:133-140 — 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 7 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:431` calls `hasBody`, `body`, `isBlank` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:421` 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 × 7) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyStyles.java:168— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyStyles.java:168-175 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredStyles.java:272-279 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianStyles.java:180-187 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsStyles.java:448-455 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformStyles.java:163-170 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionStyles.java:194-201 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceStyles.java:336-343 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyStyles.java: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 7) examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:144— examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:144-151 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:149-156 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:167-174 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:172-179 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:523-530 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:532-539 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:440-447 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java` and `examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java` as WHOLE FILES: this scan already matched 5 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. 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–8 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:132— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:132-139 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:132-138 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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. 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–8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:183— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:183-189 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:431-438 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:183` 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–8 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:128— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:128-134 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:109-116 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:76— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:76-83 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:66-71 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:80-86 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceMasthead.java:108-113 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:217— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:217-222 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:214-219 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:782-788 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:569-575 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:655— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:655-660 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:813-818 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:928-933 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:949-954 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:122— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:122-127 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CenteredHeadline.java:149-155 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MinimalUnderlined.java:118-122 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ModernProfessional.java:173-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 all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165-169 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:144-148 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionMasthead.java:132-136 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionParties.java:89-93 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 40 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:165` 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 × 4) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:144— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:144-148 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/SidebarPortraitLetter.java:140-144 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:502-507 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:898-903 — 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. 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 × 5) core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:43— core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:43-47 | core/src/main/java/com/demcha/compose/document/node/LineNode.java:316-320 | core/src/main/java/com/demcha/compose/document/style/DocumentPaint.java:208-212 | core/src/main/java/com/demcha/compose/document/style/DocumentPathSegment.java:145-149 | core/src/main/java/com/demcha/compose/document/style/DocumentTransform.java:119-123 — 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.
Duplicated block (5 lines × 5) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:627— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:627-632 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1172-1176 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:856-861 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:978-983 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:992-997 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. 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 × 5) examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:139— examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:139-143 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:156-160 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:179-183 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:204-208 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:221-225 — 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 `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:139` 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, `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:137` calls `plain`, `accent` and `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:178` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:327— examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:327-336 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:362-371 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:465-474 — 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 `examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:327` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) examples/src/main/java/com/demcha/examples/templates/invoice/v2/ModernInvoiceV2Example.java:44— examples/src/main/java/com/demcha/examples/templates/invoice/v2/ModernInvoiceV2Example.java:44-53 | examples/src/main/java/com/demcha/examples/templates/proposal/v2/ModernProposalV2Example.java:44-53 | examples/src/main/java/com/demcha/examples/templates/receipt/ModernReceiptExample.java:61-70 — 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 `examples/src/main/java/com/demcha/examples/templates/invoice/v2/ModernInvoiceV2Example.java:44` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 3) examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:107— examples/src/main/java/com/demcha/examples/features/text/ArabicArticleExample.java:107-116 | examples/src/main/java/com/demcha/examples/features/text/HebrewInvoiceExample.java:76-85 | examples/src/main/java/com/demcha/examples/features/text/WorldScriptsExample.java:49-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 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.
Swallowed exception (empty catch) web/home.js:52— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) knowledge/tools/api-query/api-query.mjs:190— 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.
Swallowed exception (empty catch) dev-tools/PdfRebuildOpenInAdobe.java:115— 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.
Empty <h2> heading web-src/pages/index.html:372— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
Empty <h2> heading web/index.html:696— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
Change coupling: RowBuilder.java ↔ LayoutCompiler.java core/src/main/java/com/demcha/compose/document/dsl/RowBuilder.java:1— `core/src/main/java/com/demcha/compose/document/dsl/RowBuilder.java` and `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `09315e3e` feat(api): row flexSpacer / pushRight / arrangement — main-axis row l… (at that commit the files were still `src/main/java/com/demcha/compose/document/dsl/RowBuilder.java` and `src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java`); `cb01014a` feat(api): RowBuilder.verticalAlign(...) — cross-axis row child align… (at that commit the files were still `src/main/java/com/demcha/compose/document/dsl/RowBuilder.java` and `src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java`); `ad89fc76` feat(api): RowBuilder.columns() — fixed / auto / weight row columns (… (at that commit the files were still `src/main/java/com/demcha/compose/document/dsl/RowBuilder.java` and `src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java`) — run `git show` on any of them.
Change coupling: DocxDrawings.java ↔ DocxLayoutMetrics.java render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java:1— `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawings.java` and `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e0c0bf24` fix(docx): draw a timeline's rail as a bar LibreOffice draws upright,…; `579d5258` fix(docx): stack drawings in Word as the page paints them (#922); `c8e57a3c` fix(docx): stop reporting drawn tiles as dropped and alike corners as… — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×2
Edited copy of a member (52 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:85— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:85-141 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformParties.java:88-139 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (52 corresponding lines) examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:152— examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:152-203 | examples/src/main/java/com/demcha/examples/features/title/PoetryTitlePageExample.java:35-120 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:99— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:99-135 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MinimalUnderlined.java:99-130 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:114— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineClosing.java:114-146 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:257-288 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×2
Edited copy of a member (31 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:273— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:273-312 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:249-279 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyMain.java:127— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyMain.java:127-157 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:209-241 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:268— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:268-292 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java:120-150 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsParties.java:57— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsParties.java:57-81 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceMasthead.java:207-233 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:224— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:224-261 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:303-329 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:475— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:475-501 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:522-564 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:165— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:165-184 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:240-259 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:289— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:289-310 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:256-275 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×2
Edited copies of one member (3 members, 19+ corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:76— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOptionsAdapter.java:76-100 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfOutputOptionsTranslator.java:115-133 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxChromeRenderer.java:449-472 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 19+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:330— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:330-348 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:693-711 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:274-292 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:95— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:95-111 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:111-127 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:116-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/BlueBannerLetter.java:84— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/BlueBannerLetter.java:84-101 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EditorialBlueLetter.java:93-110 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/SidebarPortraitLetter.java:88-104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×2
Edited copies of one member (3 members, 12+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:66— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:66-77 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:88-99 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailWidgets.java:82-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 12+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:502— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:502-513 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:515-526 | templates/src/main/java/com/demcha/compose/document/templates/cv/widgets/SectionHeader.java:287-299 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×2
Edited copies of one member (3 members, 7+ corresponding lines) examples/src/main/java/com/demcha/examples/features/text/LetterSpacingExample.java:100— examples/src/main/java/com/demcha/examples/features/text/LetterSpacingExample.java:100-111 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:400-415 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:353-359 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/java/com/demcha/compose/document/node/CanvasLayerNode.java:90— core/src/main/java/com/demcha/compose/document/node/CanvasLayerNode.java:90-96 | core/src/main/java/com/demcha/compose/document/node/LayerStackNode.java:76-82 | core/src/main/java/com/demcha/compose/document/node/ShapeContainerNode.java:120-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×2
Edited copies of one member (3 members, 10+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:204— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:204-213 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:455-465 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:473-483 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16669— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16669-16678 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:71-83 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java:407-416 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantInvoice.java:165— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantInvoice.java:165-175 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformInvoice.java:172-182 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionInvoice.java:168-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxCellDrawings.java:66— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxCellDrawings.java:66-76 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:610-620 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:23993-24003 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×2
Edited copies of one member (3 members, 6+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:641— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:641-646 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:942-947 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:605-610 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) core/src/main/java/com/demcha/compose/document/dsl/DocumentDsl.java:159— core/src/main/java/com/demcha/compose/document/dsl/DocumentDsl.java:159-164 | core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java:302-307 | core/src/main/java/com/demcha/compose/document/dsl/ParagraphBuilder.java:958-963 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (26 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:898— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:898-923 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1014-1039 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 (26 lines × 2) core/src/main/java/com/demcha/compose/document/snapshot/LayoutNodeSnapshot.java:1— core/src/main/java/com/demcha/compose/document/snapshot/LayoutNodeSnapshot.java:1-26 | core/src/main/java/com/demcha/compose/engine/debug/LayoutNodeSnapshot.java:1-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/snapshot/LayoutNodeSnapshot.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:121— core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:121-143 | core/src/main/java/com/demcha/compose/document/layout/CompositeDecoration.java:171-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.
Duplicated block (23 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:645— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:645-667 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:113-135 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:31— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java:31-52 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShapeClipBeginRenderHandler.java:51-72 — 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 (22 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:246— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:246-267 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:239-260 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:246` 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, `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:268` calls `repeatHeader` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:261` 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 (21 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:671— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:671-691 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:163-183 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 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 `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:671` 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) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1073— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1073-1093 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:156-176 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 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 `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1073` 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–21 lines × 2) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1080— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1080-1100 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1173-1192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1080` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (20–21 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:367— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:367-386 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:260-280 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:367` 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 (12–13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:288— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:288-299 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:527-539 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:288` 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 (12–13 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:112— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:112-124 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MinimalUnderlined.java:109-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/BoxedSections.java:112` 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–12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:220— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:220-230 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:242-253 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:220` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11–12 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:657— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:657-667 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:704-715 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:657` 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–10 lines × 2) core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:116— core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:116-122 | core/src/main/java/com/demcha/compose/document/layout/TextFlowSupport.java:489-498 — both copies are in the same file, so extract the 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `prepared` to `PreparedNode<ParagraphNode>` in one and `PreparedNode<ListNode>` 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 (7–10 lines × 2) examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:99— examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:99-108 | examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:70-76 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java` and `examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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 `examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:99` 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, `examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:109` calls `markdown` and `examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:77` 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 (8–10 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:90— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:90-99 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:112-119 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `environment` to `PdfRenderEnvironment` in one and `PptxRenderEnvironment` 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–10 lines × 2) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:293— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:293-302 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:282-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 `examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:293` 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 × 4) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:247— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:247-254 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:124-131 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:189-196 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionClosing.java:293-300 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java` as WHOLE FILES: this scan already matched 5 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. 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 (8 lines × 4) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148-155 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:238-245 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:163-170 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:368-375 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148` 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, `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:234` calls `plain`, `accent` and `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35 lines × 2) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfLinkOptions.java:1— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfLinkOptions.java:1-35 | core/src/main/java/com/demcha/compose/document/node/DocumentLinkOptions.java:1-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfLinkOptions.java:1` 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 (35 lines × 2) core/src/main/java/com/demcha/compose/document/layout/payloads/ParagraphShapeSpan.java:1— core/src/main/java/com/demcha/compose/document/layout/payloads/ParagraphShapeSpan.java:1-35 | core/src/main/java/com/demcha/compose/document/layout/payloads/ParagraphSvgSpan.java:1-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/payloads/ParagraphShapeSpan.java:1` 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 × 6) core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:31— core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:31-35 | core/src/main/java/com/demcha/compose/document/layout/definitions/EllipseDefinition.java:31-35 | core/src/main/java/com/demcha/compose/document/layout/definitions/PathDefinition.java:37-41 | core/src/main/java/com/demcha/compose/document/layout/definitions/PolygonDefinition.java:33-37 | core/src/main/java/com/demcha/compose/document/layout/definitions/ShapeDefinition.java:32-36 | core/src/main/java/com/demcha/compose/document/layout/definitions/SpacerDefinition.java:30-34 — 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 6 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `node` to `BarcodeNode` in one and `EllipseNode` 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 × 6) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:137— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:137-142 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:238-242 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:156-160 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:233-237 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:342-347 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:506-511 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java` as WHOLE FILES: this scan already matched 6 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. 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 × 7) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:205— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:205-210 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:227-231 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/SidebarPortraitLetter.java:154-158 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:231-236 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:820-825 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:499-504 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:913-918 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 7) examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:65— examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:65-69 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:88-92 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:111-115 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:137-141 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:163-167 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:189-193 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:215-219 — all 7 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 `examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java:65— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java:65-74 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java:47-56 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionText.java:56-65 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java:47-56 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:133— examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:133-142 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:129-138 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:156-165 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:161-170 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java` and `examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java` as WHOLE FILES: this scan already matched 5 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.
Low cohesion: DocxFidelityGateTest (LCOM4 28) qa/src/test/java/com/demcha/compose/document/templates/fidelity/DocxFidelityGateTest.java:27— DocxFidelityGateTest's methods fall into 28 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 28 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PageMarginTest (LCOM4 13) qa/src/test/java/com/demcha/compose/document/api/PageMarginTest.java:26— PageMarginTest's methods fall into 13 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 13 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.
Duplicated block (8 lines × 2 locations) knowledge/tools/api-query/api-query.mjs:94— knowledge/tools/api-query/api-query.mjs:94 · knowledge/tools/api-surface/extract-api.mjs:135 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) knowledge/tools/api-surface/lib/javap.mjs:89— knowledge/tools/api-surface/lib/javap.mjs:89 · knowledge/tools/api-surface/lib/source-names.mjs:27 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) knowledge/tools/claims/check-claims.mjs:73— knowledge/tools/claims/check-claims.mjs:73 · knowledge/tools/routing/check-routes.mjs:117 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) web/examples.js:587— web/examples.js:587 · web/examples.js:700 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Complex function parseArgs (cyclomatic 15, cognitive 16) knowledge/tools/api-query/api-query.mjs:90— parseArgs has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseArgs (cyclomatic 15, cognitive 16) knowledge/tools/api-surface/extract-api.mjs:132— parseArgs has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Low contrast colour pair in CSS (2.9:1) web/styles.css:1286— `.example-card[data-id] .example-preview-fallback` sets color: #52606d on background-color: #0b1220 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) web/styles.css:1391— `.example-action` sets color: #fff on background-color: #6366f1 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
DocxSemanticBackend.writePanelPiece (cyclomatic 72) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:9294— DocxSemanticBackend.writePanelPiece has cyclomatic complexity 72 (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 file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.reportZoneLine (cyclomatic 54) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3896— DocxSemanticBackend.reportZoneLine has cyclomatic complexity 54 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
gallery-viewer.panelModel (cyclomatic 46) REDACTED:81— gallery-viewer.panelModel has cyclomatic complexity 46 (threshold 15). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
buildSurface (cyclomatic 44) knowledge/tools/api-surface/extract-api.mjs:351— buildSurface has cyclomatic complexity 44 (threshold 15). Of this number, 35 points are the body's own statements and 9 belong to 18 function items inside it that branch. 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.
DocxSemanticBackend.applyPageZones (cyclomatic 43) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2339— DocxSemanticBackend.applyPageZones has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
gallery-viewer.createViewer (cyclomatic 43) REDACTED:305— gallery-viewer.createViewer has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 778, 836, 740, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DocxTimelineRails.apply (cyclomatic 41) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:106— DocxTimelineRails.apply has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SvgPathParser.apply (cyclomatic 39) core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:85— SvgPathParser.apply has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
query (cyclomatic 39) knowledge/tools/api-query/api-query.mjs:414— query has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to 16 function literals inside it that branch. 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.
BarChartLayout.resolveHorizontal (cyclomatic 38) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:164— BarChartLayout.resolveHorizontal has cyclomatic complexity 38 (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.
DocxSemanticBackend.zonePlacement (cyclomatic 35) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3538— DocxSemanticBackend.zonePlacement has cyclomatic complexity 35 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeParagraphRuns (cyclomatic 32) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:15313— DocxSemanticBackend.writeParagraphRuns has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.reportTheItemsPictures (cyclomatic 31) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16719— DocxSemanticBackend.reportTheItemsPictures has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.write (cyclomatic 30) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:1313— DocxSemanticBackend.write has cyclomatic complexity 30 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
LayoutCompiler.compileComposite (cyclomatic 29) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:235— LayoutCompiler.compileComposite has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RowNode.<init> (cyclomatic 29) core/src/main/java/com/demcha/compose/document/node/RowNode.java:61— RowNode.<init> has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.takeFromTheLineAbove (cyclomatic 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11805— DocxSemanticBackend.takeFromTheLineAbove has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.dispatchNode (cyclomatic 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5549— DocxSemanticBackend.dispatchNode has cyclomatic complexity 28 (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 file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeBand (cyclomatic 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2687— DocxSemanticBackend.writeBand has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeLayerColumns (cyclomatic 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20975— DocxSemanticBackend.writeLayerColumns has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ParagraphWrapping.toInlineParagraphLine (cyclomatic 27) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:731— ParagraphWrapping.toInlineParagraphLine has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxLinePair.of (cyclomatic 27) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLinePair.java:129— DocxLinePair.of has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.writeLinePair (cyclomatic 27) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12913— DocxSemanticBackend.writeLinePair has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeNodeContentOf (cyclomatic 27) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5394— DocxSemanticBackend.writeNodeContentOf has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
PdfParagraphFragmentRenderHandler.renderLine (cyclomatic 27) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:326— PdfParagraphFragmentRenderHandler.renderLine has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
loadSurfaces (cyclomatic 27) knowledge/tools/api-query/api-query.mjs:318— loadSurfaces has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 7 function literals inside it that branch. 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.
DocxPageMarginSections.plan (cyclomatic 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:188— DocxPageMarginSections.plan has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.drawAndNameOwnFragments (cyclomatic 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6151— DocxSemanticBackend.drawAndNameOwnFragments has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeRule (cyclomatic 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:17700— DocxSemanticBackend.writeRule has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ParagraphWrapping.wrapInlineParagraph (cyclomatic 25) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:273— ParagraphWrapping.wrapInlineParagraph has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxNodeValues.alike (cyclomatic 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNodeValues.java:42— DocxNodeValues.alike has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.carriedWithout (cyclomatic 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5729— DocxSemanticBackend.carriedWithout has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.textBadgeParagraph (cyclomatic 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:17418— DocxSemanticBackend.textBadgeParagraph has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeTableRows (cyclomatic 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19390— DocxSemanticBackend.writeTableRows has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
TimelineMinimal.sectionLines (cyclomatic 24) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:646— TimelineMinimal.sectionLines has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
examples.render (cyclomatic 24) web/examples.js:406— examples.render has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LineChartLayout.resolve (cyclomatic 23) core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:35— LineChartLayout.resolve 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.
ParagraphWrapping.wrapMarkdownParagraph (cyclomatic 23) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:429— ParagraphWrapping.wrapMarkdownParagraph 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.
DocxGrownLines.reachOf (cyclomatic 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:137— DocxGrownLines.reachOf 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.
DocxSemanticBackend.writeCellContent (cyclomatic 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19926— DocxSemanticBackend.writeCellContent 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeRichListLine (cyclomatic 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:7992— DocxSemanticBackend.writeRichListLine 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.zoneStops (cyclomatic 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3693— DocxSemanticBackend.zoneStops 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
PdfTableRowFragmentRenderHandler.renderCellText (cyclomatic 23) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:186— PdfTableRowFragmentRenderHandler.renderCellText 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.
PieChartLayout.resolve (cyclomatic 22) core/src/main/java/com/demcha/compose/document/chart/PieChartLayout.java:24— PieChartLayout.resolve has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SvgPathParser.number (cyclomatic 22) core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:300— SvgPathParser.number has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
javap.parseMember (cyclomatic 22) knowledge/tools/api-surface/lib/javap.mjs:158— javap.parseMember has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gallery-viewer.createViewer.render (cyclomatic 22) REDACTED:391— gallery-viewer.createViewer.render 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.
createViewer.render (cyclomatic 22) REDACTED:391— createViewer.render 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.
render (cyclomatic 22) knowledge/tools/api-query/api-query.mjs:559— render has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 belong to 2 function items inside it that branch. 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.
Part.legend (cyclomatic 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:746— Part.legend has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocxSemanticBackend.moveTheRowsText (cyclomatic 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20162— DocxSemanticBackend.moveTheRowsText 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ParagraphWrapping.tokenizeInlineRuns (cyclomatic 20) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:658— ParagraphWrapping.tokenizeInlineRuns has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SvgIconReader.stylize (cyclomatic 20) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:455— SvgIconReader.stylize 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.
SvgIconReader.walk (cyclomatic 20) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:154— SvgIconReader.walk has cyclomatic complexity 20 (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.
DocxLayerColumns.flow (cyclomatic 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:392— DocxLayerColumns.flow has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxLineStartHyphens.hold (cyclomatic 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLineStartHyphens.java:111— DocxLineStartHyphens.hold has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.reportBandText (cyclomatic 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2941— DocxSemanticBackend.reportBandText has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxTimelineRails.offsetOfTheBar (cyclomatic 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:258— DocxTimelineRails.offsetOfTheBar has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Found.look (cyclomatic 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:140— Found.look has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
examples.renderCard (cyclomatic 20) web/examples.js:679— examples.renderCard has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DocxLayoutMetrics.lineHeight (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:940— DocxLayoutMetrics.lineHeight has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxLayoutMetrics.solidFillAt (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1930— DocxLayoutMetrics.solidFillAt has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocxSemanticBackend.anchorComposedDrawing (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18550— DocxSemanticBackend.anchorComposedDrawing 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.placeZone (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3265— DocxSemanticBackend.placeZone 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.twentiethsToThePage (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12592— DocxSemanticBackend.twentiethsToThePage has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.withRowEditorSlack (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22377— DocxSemanticBackend.withRowEditorSlack has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeContainerChildren (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:8535— DocxSemanticBackend.writeContainerChildren 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeList (cyclomatic 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6942— DocxSemanticBackend.writeList 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ChartStyle.<init> (cyclomatic 18) core/src/main/java/com/demcha/compose/document/chart/ChartStyle.java:84— ChartStyle.<init> has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SvgIconReader.emitLayer (cyclomatic 18) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:234— SvgIconReader.emitLayer 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.
DocxMarkdown.laidOutAt (cyclomatic 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxMarkdown.java:330— DocxMarkdown.laidOutAt 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.
DocxSemanticBackend.fittedSize (cyclomatic 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14379— DocxSemanticBackend.fittedSize 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.measureAtWordsSize (cyclomatic 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12486— DocxSemanticBackend.measureAtWordsSize has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeTableWithItsOwnSpacing (cyclomatic 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18083— DocxSemanticBackend.writeTableWithItsOwnSpacing has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeZoneLine (cyclomatic 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3357— DocxSemanticBackend.writeZoneLine 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
PdfTableRowFragmentRenderHandler.resolveTextLines (cyclomatic 18) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:299— PdfTableRowFragmentRenderHandler.resolveTextLines 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.
claims.stripCommentsAndLiterals (cyclomatic 18) knowledge/tools/claims/lib/claims.mjs:198— claims.stripCommentsAndLiterals has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, 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.
BarChartLayout.resolveVertical (cyclomatic 17) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:49— BarChartLayout.resolveVertical 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.
ChartStyle.mergedUnder (cyclomatic 17) core/src/main/java/com/demcha/compose/document/chart/ChartStyle.java:137— ChartStyle.mergedUnder has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ImageNode.<init> (cyclomatic 17) core/src/main/java/com/demcha/compose/document/node/ImageNode.java:46— ImageNode.<init> has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocxDrawingAnchors.endSection (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:446— DocxDrawingAnchors.endSection 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.
Run.of (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:593— Run.of 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.
DocxNativeCharts.scaleOf (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:932— DocxNativeCharts.scaleOf 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.
Part.bar (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:359— Part.bar has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Part.line (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:416— Part.line 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.
DocxSemanticBackend.composedRowStarts (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22058— DocxSemanticBackend.composedRowStarts 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.drawnBesideItsText (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:21846— DocxSemanticBackend.drawnBesideItsText 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.dropTheSpaceBelow (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11644— DocxSemanticBackend.dropTheSpaceBelow 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.indentAsThePrefixDoes (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14575— DocxSemanticBackend.indentAsThePrefixDoes has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.reportTheLayersOfItsPanel (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10620— DocxSemanticBackend.reportTheLayersOfItsPanel 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.resolveRowSlots (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22692— DocxSemanticBackend.resolveRowSlots 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeInlinePicture (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16472— DocxSemanticBackend.writeInlinePicture has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeParagraph (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13761— DocxSemanticBackend.writeParagraph has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeShapeContainer (cyclomatic 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13117— DocxSemanticBackend.writeShapeContainer 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ParagraphWrapping.wrapParagraph (cyclomatic 16) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:60— ParagraphWrapping.wrapParagraph 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.
SplittableLeafCompiler.compile (cyclomatic 16) core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:50— SplittableLeafCompiler.compile 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.
ArabicShaper.shape (cyclomatic 16) core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:148— ArabicShaper.shape 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.
DocxClosingSpaces.fillTheClosingSpaces (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClosingSpaces.java:105— DocxClosingSpaces.fillTheClosingSpaces 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.
DocxLayerColumns.columnsOf (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:148— DocxLayerColumns.columnsOf 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.
DocxLayoutMetrics.entriesOf (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:2182— DocxLayoutMetrics.entriesOf 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.
DocxSemanticBackend.carryTheRowsRounding (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18853— DocxSemanticBackend.carryTheRowsRounding 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.fitBlankLinesToTheRow (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19034— DocxSemanticBackend.fitBlankLinesToTheRow 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.floatable (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4939— DocxSemanticBackend.floatable 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.holdIn (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:21487— DocxSemanticBackend.holdIn has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.keepTheLastBookmarkOfEachAnchor (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13649— DocxSemanticBackend.keepTheLastBookmarkOfEachAnchor has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.newBodyParagraph (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11291— DocxSemanticBackend.newBodyParagraph has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.paragraphLost (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13874— DocxSemanticBackend.paragraphLost 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.raiseRows (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11976— DocxSemanticBackend.raiseRows 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.reportUnwrittenRowPaint (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20447— DocxSemanticBackend.reportUnwrittenRowPaint has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.takeTheDrawingOf (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18643— DocxSemanticBackend.takeTheDrawingOf 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.valueGridOf (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:8345— DocxSemanticBackend.valueGridOf 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxSemanticBackend.writeRow (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20638— DocxSemanticBackend.writeRow 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. This file is where this pass's cyclomatic complexity CONCENTRATES: render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java holds 54 of the 116 methods over the threshold — including the worst — and 419 of the 897 points over it (47%), 6.3× the next-largest file (REDACTED at 66). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
DocxTimelineRails.cutAt (cyclomatic 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:632— DocxTimelineRails.cutAt 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.
StructuredProposalData.<init> (cyclomatic 16) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/StructuredProposalData.java:61— StructuredProposalData.<init> has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
api-query.renderTask (cyclomatic 16) knowledge/tools/api-query/api-query.mjs:233— api-query.renderTask has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
examples.injectFullItemListJsonLd (cyclomatic 16) web/examples.js:118— examples.injectFullItemListJsonLd 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.
extract-api.buildSurface (cognitive 100) knowledge/tools/api-surface/extract-api.mjs:351— extract-api.buildSurface has cognitive complexity 100 (threshold 15). Drivers by points: ternaries 12 (36 pts), if/else 13 (33 pts), loops 10 (21 pts), boolean chains 6, error handling 1 (4 pts) (nesting depth added 58). Of this number, 80 points are the body's own statements and 20 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.reportZoneLine (cognitive 91) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3896— DocxSemanticBackend.reportZoneLine has cognitive complexity 91 (threshold 15). Drivers by points: if/else 24 (39 pts), ternaries 13 (33 pts), boolean chains 13, loops 6 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writePanelPiece (cognitive 89) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:9294— DocxSemanticBackend.writePanelPiece has cognitive complexity 89 (threshold 15). Drivers by points: ternaries 26 (36 pts), if/else 28 (35 pts), boolean chains 18 (nesting depth added 17). 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.
BarChartLayout.resolveHorizontal (cognitive 80) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:164— BarChartLayout.resolveHorizontal has cognitive complexity 80 (threshold 15). Drivers by points: if/else 19 (48 pts), loops 8 (17 pts), ternaries 6 (10 pts), boolean chains 5 (nesting depth added 42). 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.
ParagraphWrapping.wrapInlineParagraph (cognitive 73) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:273— ParagraphWrapping.wrapInlineParagraph has cognitive complexity 73 (threshold 15). Drivers by points: if/else 15 (47 pts), ternaries 5 (19 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 49). 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.
DocxSemanticBackend.applyPageZones (cognitive 67) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2339— DocxSemanticBackend.applyPageZones has cognitive complexity 67 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 10 (14 pts), boolean chains 13, ternaries 6 (13 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxTimelineRails.apply (cognitive 61) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:106— DocxTimelineRails.apply has cognitive complexity 61 (threshold 15). Drivers by points: if/else 19 (30 pts), loops 10 (14 pts), boolean chains 11, ternaries 2 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PdfParagraphFragmentRenderHandler.renderLine (cognitive 60) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:326— PdfParagraphFragmentRenderHandler.renderLine has cognitive complexity 60 (threshold 15). Drivers by points: if/else 22 (54 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 34). 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.
query (cognitive 59) knowledge/tools/api-query/api-query.mjs:414— query has cognitive complexity 59 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 8 (16 pts), loops 5 (10 pts), boolean chains 8, other 4 (nesting depth added 23). Of this number, 55 points are the body's own statements and 4 belong to 16 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParagraphWrapping.wrapMarkdownParagraph (cognitive 58) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:429— ParagraphWrapping.wrapMarkdownParagraph has cognitive complexity 58 (threshold 15). Drivers by points: if/else 15 (47 pts), loops 3 (6 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 36). 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.
DocxSemanticBackend.zonePlacement (cognitive 57) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3538— DocxSemanticBackend.zonePlacement has cognitive complexity 57 (threshold 15). Drivers by points: if/else 15 (30 pts), ternaries 8 (16 pts), boolean chains 8, loops 3 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgPathParser.apply (cognitive 55) core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:85— SvgPathParser.apply has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 24 (48 pts), if/else 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 26). 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.
DocxSemanticBackend.write (cognitive 53) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:1313— DocxSemanticBackend.write has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 5 (10 pts), ternaries 6 (10 pts), boolean chains 5 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeParagraphRuns (cognitive 53) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:15313— DocxSemanticBackend.writeParagraphRuns has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (26 pts), ternaries 11 (18 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 22). 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.
DocxSemanticBackend.writeTableRows (cognitive 53) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19390— DocxSemanticBackend.writeTableRows has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 9 (18 pts), ternaries 4 (13 pts), boolean chains 3 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimelineMinimal.sectionLines (cognitive 52) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:646— TimelineMinimal.sectionLines has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (44 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
loadSurfaces (cognitive 52) knowledge/tools/api-query/api-query.mjs:318— loadSurfaces has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 5 (22 pts), loops 4 (10 pts), other 9, if/else 3 (7 pts), boolean chains 4 (nesting depth added 27). Of this number, 44 points are the body's own statements and 8 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParagraphWrapping.tokenizeInlineRuns (cognitive 50) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:658— ParagraphWrapping.tokenizeInlineRuns has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (25 pts), ternaries 4 (14 pts), loops 4 (11 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.reportTheItemsPictures (cognitive 49) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16719— DocxSemanticBackend.reportTheItemsPictures has cognitive complexity 49 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 6 (10 pts), ternaries 4 (8 pts), boolean chains 5 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutCompiler.compileComposite (cognitive 48) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:235— LayoutCompiler.compileComposite has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 10, loops 3 (8 pts), ternaries 2 (6 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxPageMarginSections.plan (cognitive 48) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:188— DocxPageMarginSections.plan has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (26 pts), ternaries 6 (16 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LineChartLayout.resolve (cognitive 47) core/src/main/java/com/demcha/compose/document/chart/LineChartLayout.java:35— LineChartLayout.resolve has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 8 (18 pts), ternaries 4 (6 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParagraphWrapping.toInlineParagraphLine (cognitive 46) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:731— ParagraphWrapping.toInlineParagraphLine has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (27 pts), loops 7 (15 pts), boolean chains 4 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeBand (cognitive 45) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2687— DocxSemanticBackend.writeBand has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 12 (23 pts), if/else 12 (19 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BarChartLayout.resolveVertical (cognitive 43) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:49— BarChartLayout.resolveVertical has cognitive complexity 43 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 3 (7 pts), ternaries 3 (7 pts), boolean chains 2 (nesting depth added 26). 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.
gallery-viewer.panelModel (cognitive 41) REDACTED:81— gallery-viewer.panelModel has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, if/else 14 (16 pts), ternaries 8 (nesting depth added 2). Of this number, 40 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
gallery-viewer.createViewer (cognitive 41) REDACTED:305— gallery-viewer.createViewer has cognitive complexity 41 (threshold 15). Drivers by points: if/else 24 (28 pts), boolean chains 9, ternaries 3 (4 pts) (nesting depth added 5). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 778, 740, 836, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DocxSemanticBackend.drawAndNameOwnFragments (cognitive 40) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6151— DocxSemanticBackend.drawAndNameOwnFragments has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 4 (8 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeLayerColumns (cognitive 40) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20975— DocxSemanticBackend.writeLayerColumns has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 8, ternaries 2 (4 pts), loops 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxTimelineRails.offsetOfTheBar (cognitive 39) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:258— DocxTimelineRails.offsetOfTheBar has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 4 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeNodeContentOf (cognitive 38) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5394— DocxSemanticBackend.writeNodeContentOf has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 10, loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParagraphWrapping.wrapParagraph (cognitive 37) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:60— ParagraphWrapping.wrapParagraph has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 3 (6 pts), ternaries 2 (5 pts) (nesting depth added 22). 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.
PdfTableRowFragmentRenderHandler.renderCellText (cognitive 37) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:186— PdfTableRowFragmentRenderHandler.renderCellText has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 6 (9 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLayoutMetrics.lineHeight (cognitive 36) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:940— DocxLayoutMetrics.lineHeight has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 4 (10 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxNodeValues.alike (cognitive 36) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNodeValues.java:42— DocxNodeValues.alike has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (23 pts), loops 3 (6 pts), boolean chains 5, error handling 1 (2 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.
RowNode.<init> (cognitive 35) core/src/main/java/com/demcha/compose/document/node/RowNode.java:61— RowNode.<init> has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 9, boolean chains 7, loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLayerColumns.flow (cognitive 35) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:392— DocxLayerColumns.flow has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 8 (15 pts), boolean chains 3, ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeRule (cognitive 35) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:17700— DocxSemanticBackend.writeRule has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 15 (21 pts), if/else 12 (13 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocxSemanticBackend.writeRichListLine (cognitive 34) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:7992— DocxSemanticBackend.writeRichListLine has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 7 (11 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
examples.injectFullItemListJsonLd (cognitive 34) web/examples.js:118— examples.injectFullItemListJsonLd has cognitive complexity 34 (threshold 15). Drivers by points: if/else 4 (13 pts), ternaries 2 (9 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 34) web/examples.js:406— render has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 9, loops 3 (5 pts), ternaries 1 (2 pts) (nesting depth added 11). Of this number, 32 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stripCommentsAndLiterals (cognitive 34) knowledge/tools/claims/lib/claims.mjs:198— stripCommentsAndLiterals has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 2 (6 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 16). Of this number, 29 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutCompiler.compileHorizontalRow (cognitive 33) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:479— LayoutCompiler.compileHorizontalRow has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 6 (13 pts), loops 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.dispatchNode (cognitive 33) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5549— DocxSemanticBackend.dispatchNode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (24 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocxSemanticBackend.moveTheRowsText (cognitive 33) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20162— DocxSemanticBackend.moveTheRowsText has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (9 pts), ternaries 3 (8 pts), boolean chains 6 (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.
DocxSemanticBackend.takeFromTheLineAbove (cognitive 32) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11805— DocxSemanticBackend.takeFromTheLineAbove has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 12, ternaries 7 (10 pts), if/else 7 (8 pts), loops 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SplittableLeafCompiler.compile (cognitive 31) core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:50— SplittableLeafCompiler.compile has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxGrownLines.reachOf (cognitive 31) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:137— DocxGrownLines.reachOf has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 9, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLinePair.of (cognitive 31) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLinePair.java:129— DocxLinePair.of has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 7, ternaries 2 (6 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.reportTheLayersOfItsPanel (cognitive 31) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10620— DocxSemanticBackend.reportTheLayersOfItsPanel has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 7 (12 pts), boolean chains 4, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Template.addReferences (cognitive 31) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1004— Template.addReferences has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 9 (26 pts), loops 2 (3 pts), boolean chains 1, if/else 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PieChartLayout.resolve (cognitive 30) core/src/main/java/com/demcha/compose/document/chart/PieChartLayout.java:24— PieChartLayout.resolve has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 7 (9 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutCompiler.compileNodeInFixedSlot (cognitive 30) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:938— LayoutCompiler.compileNodeInFixedSlot has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SidebarPortrait.languageItems (cognitive 30) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1110— SidebarPortrait.languageItems has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (11 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableGrid.resolve (cognitive 29) core/src/main/java/com/demcha/compose/document/layout/TableGrid.java:80— TableGrid.resolve has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (10 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxNativeCharts.scaleOf (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:932— DocxNativeCharts.scaleOf has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 4 (10 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Part.line (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:416— Part.line has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.carriedWithout (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5729— DocxSemanticBackend.carriedWithout has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 5, ternaries 2 (4 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.
DocxSemanticBackend.reportBandText (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2941— DocxSemanticBackend.reportBandText has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 10 (20 pts), boolean chains 5, if/else 4 (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.
DocxSemanticBackend.writeLinePair (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12913— DocxSemanticBackend.writeLinePair has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 6 (8 pts), loops 5 (6 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocxSemanticBackend.zoneStops (cognitive 29) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3693— DocxSemanticBackend.zoneStops has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render (cognitive 29) knowledge/tools/api-query/api-query.mjs:559— render has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11, loops 5 (10 pts), ternaries 3 (6 pts), boolean chains 1, other 1 (nesting depth added 8). Of this number, 25 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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.
DocxDrawingAnchors.endSection (cognitive 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:446— DocxDrawingAnchors.endSection has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLineStartHyphens.hold (cognitive 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLineStartHyphens.java:111— DocxLineStartHyphens.hold has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 5 (7 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.carryTheRowsRounding (cognitive 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18853— DocxSemanticBackend.carryTheRowsRounding has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (6 pts), boolean chains 5, ternaries 2 (5 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.
DocxSemanticBackend.dropTheSpaceBelow (cognitive 28) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11644— DocxSemanticBackend.dropTheSpaceBelow has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 6, loops 2 (5 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgIconReader.emitLayer (cognitive 27) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:234— SvgIconReader.emitLayer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 6, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLayoutMetrics.solidFillAt (cognitive 27) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1930— DocxLayoutMetrics.solidFillAt has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 6 (8 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.twentiethsToThePage (cognitive 27) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12592— DocxSemanticBackend.twentiethsToThePage has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 6, loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
javap.parseMember (cognitive 27) knowledge/tools/api-surface/lib/javap.mjs:158— javap.parseMember has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, ternaries 4 (5 pts), loops 3 (4 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.
originatingBetas (cognitive 27) knowledge/tools/api-surface/lib/stability-doc.mjs:27— originatingBetas has cognitive complexity 27 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 4 (10 pts), other 3, boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxClosingSpaces.fillTheClosingSpaces (cognitive 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxClosingSpaces.java:105— DocxClosingSpaces.fillTheClosingSpaces has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 3 (7 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.fittedSize (cognitive 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14379— DocxSemanticBackend.fittedSize has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (5 pts), ternaries 3 (5 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.raiseRows (cognitive 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11976— DocxSemanticBackend.raiseRows has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeZoneLine (cognitive 26) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3357— DocxSemanticBackend.writeZoneLine has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (6 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayoutSupport.resolveNaturalColumnWidths (cognitive 25) core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:503— TableLayoutSupport.resolveNaturalColumnWidths has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 5 (7 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.
SvgIconReader.clipShapeData (cognitive 25) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:369— SvgIconReader.clipShapeData has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgPathParser.number (cognitive 25) core/src/main/java/com/demcha/compose/document/svg/SvgPathParser.java:300— SvgPathParser.number has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (9 pts), loops 3 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArabicShaper.shape (cognitive 25) core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:148— ArabicShaper.shape has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (6 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLayoutMetrics.matchComposedText (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:1452— DocxLayoutMetrics.matchComposedText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (5 pts), ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.composedRowStarts (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22058— DocxSemanticBackend.composedRowStarts has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (5 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.keepOnOnePage (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4697— DocxSemanticBackend.keepOnOnePage has cognitive complexity 25 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 4 (9 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.resolveRowSlots (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22692— DocxSemanticBackend.resolveRowSlots has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (9 pts), match/switch 1 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.weighTextStyles (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11033— DocxSemanticBackend.weighTextStyles has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 3 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.withRowEditorSlack (cognitive 25) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22377— DocxSemanticBackend.withRowEditorSlack has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (7 pts), boolean chains 6, loops 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.
ChartLayoutSupport.domain (cognitive 24) core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:139— ChartLayoutSupport.domain has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Seat.paragraphTop (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:859— Seat.paragraphTop has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 5 (nesting depth added 11). 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.
DocxLayoutMetrics.entriesOf (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java:2182— DocxLayoutMetrics.entriesOf has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (5 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLineStartHyphens.lettersOf (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLineStartHyphens.java:196— DocxLineStartHyphens.lettersOf has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxMarkdown.laidOutAt (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxMarkdown.java:330— DocxMarkdown.laidOutAt has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 5 (6 pts), ternaries 3 (5 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.
DocxSemanticBackend.laidOverAPaintedNeighbour (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5104— DocxSemanticBackend.laidOverAPaintedNeighbour has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 4 (6 pts), boolean chains 2 (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.
DocxSemanticBackend.writtenContent (cognitive 24) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18907— DocxSemanticBackend.writtenContent has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (8 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeDefinitionSupport.measureRow (cognitive 23) core/src/main/java/com/demcha/compose/document/layout/NodeDefinitionSupport.java:417— NodeDefinitionSupport.measureRow has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (10 pts), loops 4 (7 pts), if/else 5 (6 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.
DocxLayerColumns.columnsOf (cognitive 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:148— DocxLayerColumns.columnsOf has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.placeZone (cognitive 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:3265— DocxSemanticBackend.placeZone has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 5, boolean chains 3 (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.
DocxSemanticBackend.textBadgeParagraph (cognitive 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:17418— DocxSemanticBackend.textBadgeParagraph has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 15, if/else 6, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DocxSemanticBackend.valueGridOf (cognitive 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:8345— DocxSemanticBackend.valueGridOf has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 5 (8 pts), loops 2, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxTimelineRails.gapsBetween (cognitive 23) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:414— DocxTimelineRails.gapsBetween has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check-claims.loadProofTargets (cognitive 23) knowledge/tools/claims/check-claims.mjs:92— check-claims.loadProofTargets has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 10). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to one function item inside it that branches (walkTests). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
createViewer.render (cognitive 23) REDACTED:391— createViewer.render has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 7, if/else 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TableLayoutSupport.resolveTableLayout (cognitive 22) core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java:45— TableLayoutSupport.resolveTableLayout has cognitive complexity 22 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 4 (10 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Part.legend (cognitive 22) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:746— Part.legend has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, loops 2 (4 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocxSemanticBackend.writePanel (cognitive 22) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:8643— DocxSemanticBackend.writePanel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeShapeContainer (cognitive 22) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13117— DocxSemanticBackend.writeShapeContainer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, ternaries 2 (4 pts), loops 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.
DocxTimelineRails.cutAt (cognitive 22) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:632— DocxTimelineRails.cutAt has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 5 (6 pts), ternaries 4 (6 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BarcodeRuns.of (cognitive 22) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/BarcodeRuns.java:40— BarcodeRuns.of has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
javap.findJavap (cognitive 22) knowledge/tools/api-surface/lib/javap.mjs:48— javap.findJavap has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (6 pts), ternaries 2, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
source-names.indexParameterNames (cognitive 22) knowledge/tools/api-surface/lib/source-names.mjs:80— source-names.indexParameterNames has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolvedLayoutPasses.apply (cognitive 21) core/src/main/java/com/demcha/compose/document/api/ResolvedLayoutPasses.java:59— ResolvedLayoutPasses.apply has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.fitBlankLinesToTheRow (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19034— DocxSemanticBackend.fitBlankLinesToTheRow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (6 pts), boolean chains 5, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.keepTheLastBookmarkOfEachAnchor (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13649— DocxSemanticBackend.keepTheLastBookmarkOfEachAnchor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 7 (9 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.paragraphLost (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13874— DocxSemanticBackend.paragraphLost has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.picturesLost (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13933— DocxSemanticBackend.picturesLost has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (5 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.seatByTheLines (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20233— DocxSemanticBackend.seatByTheLines has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (12 pts), boolean chains 4, if/else 2 (3 pts), loops 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.
DocxSemanticBackend.slackTheMarginsHold (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:22925— DocxSemanticBackend.slackTheMarginsHold has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 5 (10 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.takeFromTheFoot (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12193— DocxSemanticBackend.takeFromTheFoot has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), boolean chains 4, loops 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.
DocxSemanticBackend.writeRow (cognitive 21) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20638— DocxSemanticBackend.writeRow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 4 (7 pts), boolean chains 3, loops 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.
ColumnPages.plan (cognitive 21) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ColumnPages.java:145— ColumnPages.plan has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 6 (8 pts), ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api-query.renderTask (cognitive 21) knowledge/tools/api-query/api-query.mjs:233— api-query.renderTask has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocxSemanticBackend.anchorComposedDrawing (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18550— DocxSemanticBackend.anchorComposedDrawing has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 4, loops 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocxSemanticBackend.drawnBesideItsText (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:21846— DocxSemanticBackend.drawnBesideItsText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 9, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.floatable (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4939— DocxSemanticBackend.floatable has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.measureAtWordsSize (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12486— DocxSemanticBackend.measureAtWordsSize has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 5, boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocxSemanticBackend.takeTheDrawingOf (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18643— DocxSemanticBackend.takeTheDrawingOf has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeContainerChildren (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:8535— DocxSemanticBackend.writeContainerChildren has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8, boolean chains 6, ternaries 4 (6 pts) (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.
DocxSemanticBackend.writeList (cognitive 20) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6942— DocxSemanticBackend.writeList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 4, if/else 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PdfShapeFragmentRenderHandler.render (cognitive 20) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShapeFragmentRenderHandler.java:80— PdfShapeFragmentRenderHandler.render has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MarkdownText.parse (cognitive 20) templates/src/main/java/com/demcha/compose/document/templates/core/text/MarkdownText.java:59— MarkdownText.parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimelineBuilder.layout (cognitive 19) core/src/main/java/com/demcha/compose/document/dsl/TimelineBuilder.java:528— TimelineBuilder.layout has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (7 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgIconReader.stylize (cognitive 19) core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java:455— SvgIconReader.stylize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, ternaries 3 (6 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.
Part.bar (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:359— Part.bar has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 5, boolean chains 4, loops 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.
DocxSemanticBackend.evenTheRowsMargins (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19111— DocxSemanticBackend.evenTheRowsMargins has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.holdIn (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:21487— DocxSemanticBackend.holdIn has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocxSemanticBackend.letTheOneRowTablesKeptWithTheNextBreak (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2124— DocxSemanticBackend.letTheOneRowTablesKeptWithTheNextBreak has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 3 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DocxSemanticBackend.newBodyParagraph (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11291— DocxSemanticBackend.newBodyParagraph has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 3 (4 pts) (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.
DocxSemanticBackend.piecesWordMaySplit (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4490— DocxSemanticBackend.piecesWordMaySplit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (9 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.placeComposedAcross (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:21376— DocxSemanticBackend.placeComposedAcross has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 3, if/else 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.
DocxSemanticBackend.reportUnwrittenRowPaint (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:20447— DocxSemanticBackend.reportUnwrittenRowPaint has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, ternaries 5 (8 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.
DocxSemanticBackend.writeCellContent (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:19926— DocxSemanticBackend.writeCellContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (5 pts), boolean chains 3, loops 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.
DocxSemanticBackend.writeInlinePicture (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:16472— DocxSemanticBackend.writeInlinePicture has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (5 pts), boolean chains 2, error handling 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.
Found.look (cognitive 19) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxWithoutLayout.java:140— Found.look has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 7, loops 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PptxParagraphFragmentRenderHandler.renderLine (cognitive 19) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxParagraphFragmentRenderHandler.java:67— PptxParagraphFragmentRenderHandler.renderLine has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build-emoji-set.main (cognitive 19) emoji/tools/build-emoji-set.py:52— build-emoji-set.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (6 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
claims.readDeclaration (cognitive 19) knowledge/tools/claims/lib/claims.mjs:309— claims.readDeclaration has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gallery-viewer.createViewer.render (cognitive 19) REDACTED:391— gallery-viewer.createViewer.render has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ArabicShaper.toBaseLetters (cognitive 18) core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:242— ArabicShaper.toBaseLetters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxFontTable.collectFonts (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java:491— DocxFontTable.collectFonts has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxLayerColumns.lowestEdge (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:832— DocxLayerColumns.lowestEdge has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (6 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.indentAsThePrefixDoes (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14575— DocxSemanticBackend.indentAsThePrefixDoes has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 5, if/else 5 (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.
DocxSemanticBackend.itemsMarkdownLost (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:7123— DocxSemanticBackend.itemsMarkdownLost has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 4 (6 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeTableWithItsOwnSpacing (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18083— DocxSemanticBackend.writeTableWithItsOwnSpacing has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocxSemanticBackend.zoneContentsIn (cognitive 18) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:1802— DocxSemanticBackend.zoneContentsIn has cognitive complexity 18 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 3 (6 pts), ternaries 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PptxShapeFragmentRenderHandler.render (cognitive 18) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxShapeFragmentRenderHandler.java:48— PptxShapeFragmentRenderHandler.render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, ternaries 1 (2 pts) (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.
claims.resolveSymbol (cognitive 18) knowledge/tools/claims/lib/claims.mjs:162— claims.resolveSymbol has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
examples.renderCard (cognitive 18) web/examples.js:679— examples.renderCard has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
membersOf (cognitive 18) knowledge/tools/changeset/changeset.mjs:90— membersOf has cognitive complexity 18 (threshold 15). Drivers by points: other 7, loops 3 (6 pts), ternaries 1 (4 pts), if/else 1 (nesting depth added 6). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ChartStyle.<init> (cognitive 17) core/src/main/java/com/demcha/compose/document/chart/ChartStyle.java:84— ChartStyle.<init> has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParagraphWrapping.directionOf (cognitive 17) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:914— ParagraphWrapping.directionOf has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4, boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Seat.inTheRow (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxDrawingAnchors.java:1112— Seat.inTheRow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Run.of (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:593— Run.of has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxMarkdown.split (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxMarkdown.java:251— DocxMarkdown.split has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1, ternaries 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.
Part.excelCode (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:865— Part.excelCode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (5 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.
DocxSemanticBackend.numberingFor (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6732— DocxSemanticBackend.numberingFor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.reportClipCut (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4804— DocxSemanticBackend.reportClipCut has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeParagraph (cognitive 17) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13761— DocxSemanticBackend.writeParagraph has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PptxClipSafety.requiredInset (cognitive 17) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxClipSafety.java:264— PptxClipSafety.requiredInset has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (6 pts), boolean chains 2 (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.
ChartStyle.mergedUnder (cognitive 16) core/src/main/java/com/demcha/compose/document/chart/ChartStyle.java:137— ChartStyle.mergedUnder has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 15, if/else 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TimelineRailOwner.segments (cognitive 16) core/src/main/java/com/demcha/compose/document/dsl/TimelineRailOwner.java:123— TimelineRailOwner.segments has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 3 (5 pts), ternaries 2 (4 pts), loops 2 (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.
ImageNode.<init> (cognitive 16) core/src/main/java/com/demcha/compose/document/node/ImageNode.java:46— ImageNode.<init> has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocxLayerColumns.edgeIn (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayerColumns.java:800— DocxLayerColumns.edgeIn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (5 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxPageMarginSections.apply (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:337— DocxPageMarginSections.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 1 (3 pts), loops 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.
DocxSemanticBackend.applyMetadata (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2237— DocxSemanticBackend.applyMetadata has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.drawCellDrawing (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18297— DocxSemanticBackend.drawCellDrawing has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.planTheRailsAlongTheirCells (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2025— DocxSemanticBackend.planTheRailsAlongTheirCells has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DocxSemanticBackend.sidesLost (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:5854— DocxSemanticBackend.sidesLost has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (6 pts), if/else 2 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DocxSemanticBackend.spaceTheSlotAsThePage (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:2821— DocxSemanticBackend.spaceTheSlotAsThePage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, loops 3, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocxSemanticBackend.writeContainerBody (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:10167— DocxSemanticBackend.writeContainerBody has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocxSemanticBackend.writeNodeContent (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:4728— DocxSemanticBackend.writeNodeContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DocxTimelineRails.empty (cognitive 16) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTimelineRails.java:537— DocxTimelineRails.empty has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PptxClipSafety.clipCannotRemoveInk (cognitive 16) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxClipSafety.java:86— PptxClipSafety.clipCannotRemoveInk has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PptxClipSafety.segmentsInsideUnitBox (cognitive 16) render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxClipSafety.java:325— PptxClipSafety.segmentsInsideUnitBox has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SectionDispatcher.renderBody (cognitive 16) templates/src/main/java/com/demcha/compose/document/templates/cv/components/SectionDispatcher.java:36— SectionDispatcher.renderBody has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
api-query.parseArgs (cognitive 16) knowledge/tools/api-query/api-query.mjs:90— api-query.parseArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extract-api.parseArgs (cognitive 16) knowledge/tools/api-surface/extract-api.mjs:132— extract-api.parseArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
createViewer.renderThumbnails (cognitive 16) REDACTED:532— createViewer.renderThumbnails has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling clique: Palette.java, Spacing.java, Typography.java templates/src/main/java/com/demcha/compose/document/templates/core/theme/Palette.java— 3 files — `templates/src/main/java/com/demcha/compose/document/templates/core/theme/Palette.java`, `templates/src/main/java/com/demcha/compose/document/templates/core/theme/Spacing.java`, `templates/src/main/java/com/demcha/compose/document/templates/core/theme/Typography.java` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Near-duplicate member pair (48 shared lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:121— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:121-292 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:124-339 — These two members are variants of one another: 48 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 (25 shared lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:115— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:115-207 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:103-189 — These two members are variants of one another: 25 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 (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:959— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:959-1000 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1005-1067 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (18 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (18 members, 50+ identical tokens) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:76— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:76-88 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyIcons.java:87-98 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1351-1364 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1073-1087 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeIcons.java:102-113 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseIcons.java:93-104 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailIcons.java:84-96 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridIcons.java:100-111 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioIcons.java:53-64 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantIcons.java:65-76 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredIcons.java:63-74 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianIcons.java:43-54 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsIcons.java:82-93 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformIcons.java:71-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionIcons.java:61-73 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceIcons.java:75-86 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoIcons.java:84-95 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltIcons.java:67-77 — These 18 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 18 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 18 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:31— core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:31-41 | core/src/main/java/com/demcha/compose/document/layout/SplitRequest.java:20-27 | core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java:42-58 | core/src/main/java/com/demcha/compose/document/node/EllipseNode.java:42-54 | core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:38-50 | core/src/main/java/com/demcha/compose/document/node/InlineSvgRun.java:43-55 | core/src/main/java/com/demcha/compose/document/node/PathNode.java:73-101 | core/src/main/java/com/demcha/compose/document/node/PolygonNode.java:46-62 | core/src/main/java/com/demcha/compose/document/node/ShapeNode.java:170-183 | core/src/main/java/com/demcha/compose/document/style/DocumentTextAutoSize.java:24-37 — 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) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:47— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:47-55 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:244-252 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredWidgets.java:48-56 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianWidgets.java:42-50 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsWidgets.java:42-50 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformWidgets.java:50-58 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionWidgets.java:40-48 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceWidgets.java:48-56 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoFlow.java:107-115 — 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· Edited copy of a member (101 corresponding lines) · ×1
Edited copy of a member (101 corresponding lines) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:280— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:280-407 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:436-536 — These two members are one piece of code written twice and then edited apart: 101 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:126— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:126-190 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:117-182 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:302— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:302-361 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:189-264 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (68 corresponding lines) · ×1
Edited copy of a member (68 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebar.java:170— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebar.java:170-247 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRail.java:179-246 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:217— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:217-270 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:209-262 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:210— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantSettlement.java:210-271 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformSettlement.java:199-247 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:152— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:152-204 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:133-175 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:178— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:178-225 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfShapeClipBeginRenderHandler.java:82-134 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:151— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsLines.java:151-204 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceLines.java:128-173 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoBand.java:146— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoBand.java:146-185 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoMasthead.java:305-345 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:345— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:345-388 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:630-687 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 34+ corresponding lines) · ×1
Edited copies of one member (3 members, 34+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:519— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:519-553 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:730-778 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:568-601 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:179— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:179-214 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:657-693 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:107— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMain.java:107-149 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMain.java:139-180 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 22+ corresponding lines) · ×1
Edited copies of one member (5 members, 22+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantInvoice.java:130— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantInvoice.java:130-154 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsInvoice.java:124-145 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformInvoice.java:127-157 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionInvoice.java:130-156 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceInvoice.java:122-144 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:118— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:118-139 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantParties.java:52-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformMasthead.java:99-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:187— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldAside.java:187-199 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarAside.java:186-198 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarAside.java:261-273 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineMasthead.java:177-189 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 17+ corresponding lines) · ×1
Edited copies of one member (5 members, 17+ corresponding lines) core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:57— core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:57-91 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:183-201 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:217-233 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:276-305 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:307-332 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 18+ corresponding lines) · ×1
Edited copies of one member (6 members, 18+ corresponding lines) core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:55— core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:55-76 | core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:89-108 | core/src/main/java/com/demcha/compose/engine/text/TextControlSanitizer.java:157-179 | core/src/main/java/com/demcha/compose/engine/text/bidi/ArabicShaper.java:242-265 | core/src/main/java/com/demcha/compose/engine/text/bidi/BidiMirroring.java:33-51 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxTextControls.java:79-96 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:427— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:427-442 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:302-320 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:361-379 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:154— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/EngineeringResumeLetter.java:154-169 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:141-154 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:332-345 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:381— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:381-395 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:418-431 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:433-446 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:448-461 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) examples/src/main/java/com/demcha/examples/support/ConsultingInvoiceSampleData.java:47— examples/src/main/java/com/demcha/examples/support/ConsultingInvoiceSampleData.java:47-57 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarIcons.java:73-84 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarIcons.java:69-82 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineIcons.java:100-112 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingIcons.java:57-69 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineIcons.java:41-54 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java:58— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java:58-63 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java:35-38 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionText.java:39-44 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java:35-38 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 5+ corresponding lines) · ×1
Edited copies of one member (5 members, 5+ corresponding lines) core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java:82— core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java:82-86 | core/src/main/java/com/demcha/compose/document/node/EllipseNode.java:80-84 | core/src/main/java/com/demcha/compose/document/node/ImageNode.java:91-95 | core/src/main/java/com/demcha/compose/document/node/ShapeNode.java:131-135 | core/src/main/java/com/demcha/compose/document/node/TableNode.java:157-161 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) core/src/main/java/com/demcha/compose/document/layout/payloads/MarkerContentItem.java:117— core/src/main/java/com/demcha/compose/document/layout/payloads/MarkerContentItem.java:117-121 | core/src/main/java/com/demcha/compose/document/style/DocumentFlowWidth.java:68-74 | templates/src/main/java/com/demcha/compose/document/templates/core/widgets/Divider.java:131-136 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CenteredHeadlineLetter.java:124— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CenteredHeadlineLetter.java:124-127 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:232-235 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:591-596 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 6+ corresponding lines) · ×1
Edited copies of one member (5 members, 6+ corresponding lines) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:327— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:327-333 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:343-348 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:606-611 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1159-1164 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:509-514 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Duplicated block (29–30 lines × 2) core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:84— core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:84-112 | core/src/main/java/com/demcha/compose/document/layout/SplittableLeafCompiler.java:159-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.
Duplicated block (21–29 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:346— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:346-366 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:631-659 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (28 lines × 2) core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:140— core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:140-167 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:933-960 — 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 (21–26 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:368— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:368-388 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:662-687 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:368` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32–35 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:960— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:960-991 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1006-1040 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:960` 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 (25 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:172— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:172-196 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:174-198 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:198-222 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:291-315 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` as WHOLE FILES: this scan already matched 4 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. 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:172` 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–25 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:158— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:158-180 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:372-396 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:158` 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–23 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:134— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:134-148 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:226-248 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java` as WHOLE FILES: this scan already matched 6 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–22 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:185— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:185-206 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:138-158 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:139-154 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20–21 lines × 3) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:453— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:453-472 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:664-684 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1166-1186 — 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 `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:453` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17–20 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:313— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:313-329 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:226-245 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:313` 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 × 6) core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:458— core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:458-476 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:670-688 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:765-783 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1079-1097 | core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1172-1190 | core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java:162-180 — before extracting anything, compare `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java` and `core/src/main/java/com/demcha/compose/document/layout/StackedLayerCompiler.java` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 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 `core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:458` 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–19 lines × 2) core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:190— core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:190-201 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:256-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. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:190` 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–19 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:642— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:642-660 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/PptxFixedLayoutBackend.java:612-629 — 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/PdfFixedLayoutBackend.java:642` 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 `environment` to `PdfRenderEnvironment` in one and `PptxRenderEnvironment` 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 (17–19 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:191— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:191-207 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:440-458 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 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 `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:191` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16–19 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:741— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:741-759 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:577-592 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:741` 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) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:150— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:150-166 | render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:442-459 — both copies are in the same file, so extract the 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 `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfParagraphFragmentRenderHandler.java:150` 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–18 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:243— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:243-260 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:276-288 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:243` 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–17 lines × 3) core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:225— core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:225-233 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:289-305 | core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:316-332 — 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 `core/src/main/java/com/demcha/compose/document/api/DocumentRenderingFacade.java:225` 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–17 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:380— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:380-396 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java:277-289 — before extracting anything, compare `render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java` and `render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java` as WHOLE FILES: this scan already matched 6 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. 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 (25 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:166— templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:166-190 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java:158-182 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java` and `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlinePageTwo.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 84 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 `templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialPageTwo.java:166` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:77— core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:77-91 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:289-303 | core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:445-459 — 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 `core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:461` calls `tokenizeMarkdownLine` and `core/src/main/java/com/demcha/compose/document/layout/ParagraphWrapping.java:305` 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 (13–15 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:247— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java:247-259 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:458-472 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MintEditorialLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 109 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 (8–13 lines × 18) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:79— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:79-88 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyIcons.java:90-98 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1353-1364 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:1075-1087 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeIcons.java:105-113 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseIcons.java:96-104 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailIcons.java:87-96 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridIcons.java:103-111 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/LumaStudioIcons.java:56-64 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantIcons.java:68-76 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredIcons.java:66-74 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianIcons.java:46-54 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsIcons.java:85-93 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformIcons.java:74-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionIcons.java:64-73 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceIcons.java:78-86 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoIcons.java:87-95 | templates/src/main/java/com/demcha/compose/document/templates/rota/presets/CobaltIcons.java:70-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 18 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 18 times. Read the line range as the matched WINDOW rather than a finished unit: at `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:79` 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 × 4) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:247— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:247-259 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1299-1311 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1320-1332 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:729-741 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 120 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:428— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:428-440 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:303-315 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/ModernProposal.java:362-374 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 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 `party` to `InvoiceParty` in one and `ProposalParty` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ModernInvoice.java:316` calls `taxId`, `isBlank` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ClassicInvoice.java:441` 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–13 lines × 4) core/src/main/java/com/demcha/compose/document/layout/BoxConstraints.java:24— core/src/main/java/com/demcha/compose/document/layout/BoxConstraints.java:24-30 | core/src/main/java/com/demcha/compose/document/layout/MeasureResult.java:14-20 | core/src/main/java/com/demcha/compose/document/node/ListNode.java:93-105 | core/src/main/java/com/demcha/compose/document/node/SpacerNode.java:33-42 — 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 `core/src/main/java/com/demcha/compose/document/node/ListNode.java: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 (9–12 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:225— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:225-233 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:101-111 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java:165-176 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionClosing.java:272-280 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformClosing.java` as WHOLE FILES: this scan already matched 5 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. 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 `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredClosing.java:99` calls `addIfPresent`, `contactPhone`, `telLink` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantClosing.java:223` 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 (2–11 lines × 7) core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:48— core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:48-58 | core/src/main/java/com/demcha/compose/document/layout/definitions/EllipseDefinition.java:48-58 | core/src/main/java/com/demcha/compose/document/layout/definitions/ImageDefinition.java:50-60 | core/src/main/java/com/demcha/compose/document/layout/definitions/LineDefinition.java:61-62 | core/src/main/java/com/demcha/compose/document/layout/definitions/PathDefinition.java:53-54 | core/src/main/java/com/demcha/compose/document/layout/definitions/PolygonDefinition.java:49-50 | core/src/main/java/com/demcha/compose/document/layout/definitions/ShapeDefinition.java:48-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/src/main/java/com/demcha/compose/document/layout/definitions/BarcodeDefinition.java:48` calls `max`, `height`, `padding` and `core/src/main/java/com/demcha/compose/document/layout/definitions/LineDefinition.java:61` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–10 lines × 8) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:96— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:96-102 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/CompactMonoLetter.java:112-118 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:117-123 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:124-130 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/TimelineMinimalLetter.java:113-120 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CenteredHeadline.java:126-135 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EditorialBlue.java:104-110 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:115-121 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java` as WHOLE FILES: this scan already matched 6 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `doc` to `CoverLetterDocument` in one and `CvDocument` 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–10 lines × 2) render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java:45— render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java:45-54 | render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxBarcodeFragmentRenderHandler.java:49-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:27— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldText.java:27-35 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarMain.java:326-334 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ProfessionalSidebarMain.java:319-327 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineText.java:26-34 — 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. 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 (6–9 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:533— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:533-538 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:745-753 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:581-586 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java` and `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 169 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:533` 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–9 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:299— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:299-307 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:375-381 — both copies are in the same file, so extract the 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailMain.java:299` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 9) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:48— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyWidgets.java:48-55 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantMasthead.java:245-252 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredWidgets.java:49-56 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianWidgets.java:43-50 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsWidgets.java:43-50 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformWidgets.java:51-58 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionWidgets.java:41-48 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceWidgets.java:49-56 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/IndigoFlow.java:108-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsWidgets.java:61` calls `disc` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformWidgets.java:61` 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–8 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:123— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CompactMono.java:123-130 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:169-175 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:277-283 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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 (2–7 lines × 5) render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:538— render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:538-544 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6560-6561 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:6609-6615 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:11592-11595 | render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:18590-18591 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxPageMarginSections.java:538` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. 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 (6 lines × 6) core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36— core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36-41 | core/src/main/java/com/demcha/compose/document/layout/SplitRequest.java:22-27 | core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java:53-58 | core/src/main/java/com/demcha/compose/document/node/EllipseNode.java:49-54 | core/src/main/java/com/demcha/compose/document/node/PolygonNode.java:57-62 | core/src/main/java/com/demcha/compose/document/node/ShapeNode.java:178-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36` 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, `core/src/main/java/com/demcha/compose/document/node/EllipseNode.java:47` calls `isBlank`, `trim` and `core/src/main/java/com/demcha/compose/document/node/PolygonNode.java:55` 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 (4–6 lines × 4) core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:91— core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:91-96 | core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:131-134 | core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:293-298 | core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:328-331 — 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 `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:96` calls `ShapeNode` and `core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:134` 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 × 10) core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36— core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36-40 | core/src/main/java/com/demcha/compose/document/layout/SplitRequest.java:22-26 | core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java:53-57 | core/src/main/java/com/demcha/compose/document/node/EllipseNode.java:49-53 | core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:41-45 | core/src/main/java/com/demcha/compose/document/node/InlineSvgRun.java:46-50 | core/src/main/java/com/demcha/compose/document/node/PathNode.java:92-96 | core/src/main/java/com/demcha/compose/document/node/PolygonNode.java:57-61 | core/src/main/java/com/demcha/compose/document/node/ShapeNode.java:178-182 | core/src/main/java/com/demcha/compose/document/style/DocumentTextAutoSize.java:26-30 — 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 `core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:36` 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, `core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:33` calls `requireFinite` and `core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:39` 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 (4–5 lines × 3) core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:47— core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:47-51 | core/src/main/java/com/demcha/compose/document/node/RowNode.java:90-93 | core/src/main/java/com/demcha/compose/document/node/SectionNode.java:59-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/src/main/java/com/demcha/compose/document/node/ContainerNode.java:51` calls `zero` and `core/src/main/java/com/demcha/compose/document/node/RowNode.java:93` 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 (4–5 lines × 5) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:48— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:48-51 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:28-32 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoicePaymentBlock.java:45-48 | templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceRecipient.java:44-47 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalParty.java:28-32 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:28` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceParty.java:28` calls `copyOf`, `requireNonNullElse`, `of` and `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceContactBlock.java:48` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (34 lines × 2) core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfBookmarkOptions.java:1— core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfBookmarkOptions.java:1-36 | core/src/main/java/com/demcha/compose/document/node/DocumentBookmarkOptions.java:1-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfBookmarkOptions.java:1` 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 (36 lines × 2) examples/src/main/java/com/demcha/examples/support/theme/TablePreset.java:1— examples/src/main/java/com/demcha/examples/support/theme/TablePreset.java:1-36 | templates/src/main/java/com/demcha/compose/document/templates/core/theme/BrandTheme.java:1-497 — 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 `examples/src/main/java/com/demcha/examples/support/theme/TablePreset.java:1` 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 (23 lines × 3) templates/src/main/java/com/demcha/compose/document/templates/core/text/TextStyles.java:12— templates/src/main/java/com/demcha/compose/document/templates/core/text/TextStyles.java:12-34 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/EditorialStyles.java:19-221 | templates/src/main/java/com/demcha/compose/document/templates/proposal/presets/NorthlineStyles.java:28-206 — 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.
Duplicated block (27 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/cv/data/CvRow.java:1— templates/src/main/java/com/demcha/compose/document/templates/cv/data/CvRow.java:1-33 | templates/src/main/java/com/demcha/compose/document/templates/cv/data/ParagraphSection.java:1-27 — 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 `templates/src/main/java/com/demcha/compose/document/templates/cv/data/CvRow.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 5) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceSummaryBlock.java:1— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceSummaryBlock.java:1-22 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalPricingRow.java:1-100 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalTimelineItem.java:1-86 | templates/src/main/java/com/demcha/compose/document/templates/data/receipt/ReceiptEvent.java:1-37 | templates/src/main/java/com/demcha/compose/document/templates/data/rota/RotaVenue.java:1-32 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceSummaryBlock.java:1` 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 (30 lines × 2) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalAcceptance.java:1— templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalAcceptance.java:1-30 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalMetaLine.java:1-78 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalAcceptance.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–33 lines × 5) templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceData.java:48— templates/src/main/java/com/demcha/compose/document/templates/data/invoice/InvoiceData.java:48-50 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalData.java:48-50 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalDeliverables.java:1-33 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalPhaseGrid.java:1-68 | templates/src/main/java/com/demcha/compose/document/templates/data/schedule/WeeklyScheduleData.java:43-45 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalDeliverables.java:1` 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 (26 lines × 4) templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalRecipient.java:1— templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalRecipient.java:1-38 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalSummaryBlock.java:1-27 | templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalTermsBlock.java:1-26 | templates/src/main/java/com/demcha/compose/document/templates/data/rota/RotaGroup.java:1-34 — 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 `templates/src/main/java/com/demcha/compose/document/templates/data/proposal/ProposalRecipient.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 8) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:130— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ClassicSerifLetter.java:130-135 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:232-236 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/NordicCleanLetter.java:150-154 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/ClassicSerif.java:335-340 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1184-1188 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:806-811 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:834-839 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NordicClean.java:516-521 — there are 8 copies across 7 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 8 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 9) templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:212— templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java:212-217 | templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java:221-225 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/EngineeringResume.java:648-653 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Executive.java:238-243 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MintEditorial.java:1178-1182 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java:849-854 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/Panel.java:492-497 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SidebarPortrait.java:971-976 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TimelineMinimal.java:619-624 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/ExecutiveLetter.java` and `templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/PanelLetter.java` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 5) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyIcons.java:65— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavyIcons.java:65-74 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOpsIcons.java:97-106 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SerifHeadlineIcons.java:73-82 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeIcons.java:80-89 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridIcons.java:78-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 all 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 6) templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingText.java:102— templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ConsultingText.java:102-108 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantText.java:21-27 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java:76-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java:26-32 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/SubscriptionText.java:67-73 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java:26-32 — before extracting anything, compare `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java` and `templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceText.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 7) templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:66— templates/src/main/java/com/demcha/compose/document/templates/cv/presets/CharcoalGoldIcons.java:66-74 | templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRailIcons.java:74-82 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantIcons.java:55-63 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredIcons.java:53-61 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsIcons.java:72-80 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PlatformIcons.java:61-69 | templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/WorkspaceIcons.java:65-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 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.
Near-duplicate member pair (19 shared lines) examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:51— examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:51-134 | examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:63-127 — These two members are variants of one another: 19 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:39— examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:39-127 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:47-123 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:43-150 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:87-155 | examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:39-165 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:34-229 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) examples/src/main/java/com/demcha/examples/features/shapes/LineCapExample.java:43— examples/src/main/java/com/demcha/examples/features/shapes/LineCapExample.java:43-83 | examples/src/main/java/com/demcha/examples/features/shapes/LineFillExample.java:45-82 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:54— examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:54-86 | examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:56-82 | examples/src/main/java/com/demcha/examples/features/navigation/ContainerBookmarkExample.java:50-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 25+ corresponding lines) · ×1
Edited copies of one member (4 members, 25+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:314— examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:314-338 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:381-412 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:416-441 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:445-476 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) examples/src/main/java/com/demcha/examples/support/MidnightNavySampleData.java:42— examples/src/main/java/com/demcha/examples/support/MidnightNavySampleData.java:42-52 | examples/src/main/java/com/demcha/examples/support/SlateOrangeSampleData.java:41-53 | examples/src/main/java/com/demcha/examples/support/TealPulseSampleData.java:45-55 | examples/src/main/java/com/demcha/examples/support/VioletGridSampleData.java:41-52 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 13+ corresponding lines) · ×1
Edited copies of one member (7 members, 13+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:526— examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:526-540 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:390-408 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:425-443 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:519-538 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:629-641 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:317-340 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:342-360 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:434— examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:434-448 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:457-471 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:485-496 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:499-511 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) examples/src/main/java/com/demcha/examples/templates/invoice/InvoiceCinematicFileExample.java:28— examples/src/main/java/com/demcha/examples/templates/invoice/InvoiceCinematicFileExample.java:28-43 | examples/src/main/java/com/demcha/examples/templates/invoice/v2/ModernInvoiceV2Example.java:36-53 | examples/src/main/java/com/demcha/examples/templates/proposal/ProposalCinematicFileExample.java:28-43 | examples/src/main/java/com/demcha/examples/templates/proposal/v2/ModernProposalV2Example.java:36-53 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 13+ corresponding lines) · ×1
Edited copies of one member (6 members, 13+ corresponding lines) examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:860— examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:860-873 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:875-888 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:908-920 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:922-934 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:950-963 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:965-979 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 9+ corresponding lines) · ×1
Edited copies of one member (7 members, 9+ corresponding lines) examples/src/main/java/com/demcha/examples/features/svg/SvgIconGalleryExample.java:182— examples/src/main/java/com/demcha/examples/features/svg/SvgIconGalleryExample.java:182-190 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:749-757 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:889-897 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:546-555 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:684-692 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:388-396 | examples/src/main/java/com/demcha/examples/support/SiteSocialCoverRenderer.java:258-266 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 12+ corresponding lines) · ×1
Edited copies of one member (6 members, 12+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:146— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:146-157 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:131-142 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:150-161 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:150-161 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:173-184 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:83-96 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 3+ corresponding lines) · ×1
Edited copies of one member (8 members, 3+ corresponding lines) examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:899— examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:899-906 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:559-566 | examples/src/main/java/com/demcha/examples/flagships/LinkedInCarouselExample.java:531-538 | examples/src/main/java/com/demcha/examples/flagships/MavenBannerPptxExample.java:914-916 | examples/src/main/java/com/demcha/examples/flagships/SocialCardExample.java:659-666 | examples/src/main/java/com/demcha/examples/flagships/TwinOutputExample.java:398-400 | examples/src/main/java/com/demcha/examples/support/SiteSocialCoverRenderer.java:241-248 | examples/src/main/java/com/demcha/examples/templates/proposal/CinematicProposalFileExample.java:186-193 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 3+ corresponding lines) · ×1
Edited copies of one member (7 members, 3+ corresponding lines) examples/src/main/java/com/demcha/examples/features/navigation/InPdfNavigationExample.java:128— examples/src/main/java/com/demcha/examples/features/navigation/InPdfNavigationExample.java:128-130 | examples/src/main/java/com/demcha/examples/features/text/TextDirectionExample.java:113-115 | examples/src/main/java/com/demcha/examples/features/text/WorldScriptsExample.java:168-170 | examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:567-573 | examples/src/main/java/com/demcha/examples/flagships/EngineShowcase.java:295-301 | examples/src/main/java/com/demcha/examples/flagships/FinancialReportExample.java:551-557 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:268-274 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) examples/src/main/java/com/demcha/examples/features/text/TextDirectionExample.java:117— examples/src/main/java/com/demcha/examples/features/text/TextDirectionExample.java:117-119 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:629-631 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:466-472 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (106–107 lines × 2) examples/src/main/java/com/demcha/examples/support/EditorialProposalSampleData.java:41— examples/src/main/java/com/demcha/examples/support/EditorialProposalSampleData.java:41-146 | examples/src/main/java/com/demcha/examples/support/StructuredProposalSampleData.java:40-146 — 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 (15–27 lines × 3) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148-162 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:238-264 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:163-177 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:148` 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, `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:234` calls `plain`, `accent` and `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:160` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20–22 lines × 2) examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:82— examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:82-103 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:107-126 — 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 `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:82` 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–18 lines × 6) examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:110— examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:110-127 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:106-123 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:133-150 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:138-155 | examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:148-165 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:213-229 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java` and `examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java` as WHOLE FILES: this scan already matched 5 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 `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:110` 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–16 lines × 2) examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:891— examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:891-906 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:982-995 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10–15 lines × 3) examples/src/main/java/com/demcha/examples/flagships/EngineShowcase.java:85— examples/src/main/java/com/demcha/examples/flagships/EngineShowcase.java:85-96 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:40-54 | examples/src/main/java/com/demcha/examples/templates/proposal/CinematicProposalFileExample.java:53-62 — 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 `examples/src/main/java/com/demcha/examples/flagships/EngineShowcase.java:85` 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, `examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:55` calls `spacing` and `examples/src/main/java/com/demcha/examples/flagships/EngineShowcase.java:97` 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–15 lines × 2) examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:79— examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:79-93 | examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:61-67 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java` and `examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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 `examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–15 lines × 2) examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:53— examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:53-67 | examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:74-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:68` calls `fillColor` and `examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:86` 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 (14–15 lines × 2) examples/src/main/java/com/demcha/examples/templates/cv/CvFileExample.java:33— examples/src/main/java/com/demcha/examples/templates/cv/CvFileExample.java:33-46 | examples/src/main/java/com/demcha/examples/templates/cv/v2/CvModernV2Example.java:28-42 — 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 (12–14 lines × 3) examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:74— examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java:74-85 | examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:37-50 | examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:58-71 — 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 `examples/src/main/java/com/demcha/examples/features/docx/WordExportExample.java: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. 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–13 lines × 2) examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:143— examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:143-155 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:198-208 — both copies are in the same file, so extract the 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 `examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java: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 (4–12 lines × 4) examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:106— examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:106-110 | examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:99-102 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:55-66 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:104-115 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java: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. 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–11 lines × 10) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:53— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:53-62 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:188-197 | examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:44-53 | examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:43-52 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:51-60 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:47-56 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:91-100 | examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:43-52 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:44-54 | examples/src/main/java/com/demcha/examples/features/transforms/TransformsExample.java:46-55 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:63` calls `accentLeft` and `examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:198` 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 (8–11 lines × 2) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:174— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:174-184 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:509-516 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java: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. 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–11 lines × 2) examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:57— examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:57-67 | examples/src/main/java/com/demcha/examples/flagships/FeatureCatalogExample.java:95-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 `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:57` 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 × 4) examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:141— examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:141-151 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:158-168 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:181-191 | examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:206-216 — 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 `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java:170` calls `accent`, `plain` and `examples/src/main/java/com/demcha/examples/features/chrome/PdfChromeExample.java: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 (7–10 lines × 3) examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:35— examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:35-44 | examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:56-65 | examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:51-57 — 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 (3–10 lines × 3) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:176— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:176-185 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java:710-712 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:243-252 — 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 `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:176` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:242` calls `accentTop` and `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:175` 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 (6–10 lines × 2) examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:196— examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:196-201 | examples/src/main/java/com/demcha/examples/features/title/PoetryTitlePageExample.java:105-114 — 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 `examples/src/main/java/com/demcha/examples/features/title/BookTemplateExample.java:196` 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 × 12) examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:52— examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:52-60 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:187-195 | examples/src/main/java/com/demcha/examples/features/navigation/InPdfNavigationExample.java:45-53 | examples/src/main/java/com/demcha/examples/features/shapes/ShapeContainerExample.java:43-51 | examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:42-50 | examples/src/main/java/com/demcha/examples/features/text/InlineHighlightExample.java:50-58 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:46-54 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:90-98 | examples/src/main/java/com/demcha/examples/features/text/RichTextShowcaseExample.java:42-50 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:43-51 | examples/src/main/java/com/demcha/examples/features/transforms/TransformsExample.java:45-53 | examples/src/main/java/com/demcha/examples/templates/coverletter/CoverLetterFileExample.java:37-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 12 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 12 times. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:52` 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, `examples/src/main/java/com/demcha/examples/features/barcodes/BarcodeShowcaseExample.java:63` calls `accentLeft` and `examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:198` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 6) examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:84— examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:84-92 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:107-115 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:133-141 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:159-167 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:185-193 | examples/src/main/java/com/demcha/examples/support/theme/BusinessTheme.java:211-219 — 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.
Duplicated block (5–9 lines × 4) examples/src/main/java/com/demcha/examples/features/canvas/CanvasLayerExample.java:90— examples/src/main/java/com/demcha/examples/features/canvas/CanvasLayerExample.java:90-98 | examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:43-51 | examples/src/main/java/com/demcha/examples/features/tables/ComposedTableCellExample.java:64-72 | examples/src/main/java/com/demcha/examples/features/tables/InlineCodeColumnWrapExample.java:53-57 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/lists/NestedListExample.java:41` calls `decoration` and `examples/src/main/java/com/demcha/examples/features/canvas/CanvasLayerExample.java:88` 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 (8 lines × 10) examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:215— examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:215-222 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:224-231 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:233-240 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:242-249 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:251-258 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:260-267 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:269-276 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:278-285 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:287-294 | examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:296-303 — all 10 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 `examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–8 lines × 5) examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:58— examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:58-65 | examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:63-68 | examples/src/main/java/com/demcha/examples/features/shapes/LineCapExample.java:51-57 | examples/src/main/java/com/demcha/examples/features/shapes/LineFillExample.java:53-59 | examples/src/main/java/com/demcha/examples/features/svg/SvgIconGalleryExample.java:106-113 — 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 `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:54` calls `parse`, `withSize`, `withColor` and `examples/src/main/java/com/demcha/examples/features/svg/SvgIconGalleryExample.java:103` 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–8 lines × 5) examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:85— examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:85-92 | examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:97-104 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:90-96 | examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java:113-120 | examples/src/main/java/com/demcha/examples/features/text/InlineSvgIconExample.java:125-132 — before extracting anything, compare `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java` and `examples/src/main/java/com/demcha/examples/features/text/InlineShapesExample.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 64 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 `examples/src/main/java/com/demcha/examples/features/text/EmojiShortcodeExample.java:85` 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 (8 lines × 6) examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99— examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99-106 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:108-115 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:117-124 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:126-133 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:134-141 | examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:145-152 — 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 `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:154` calls `accentBottom`, `spacing` and `examples/src/main/java/com/demcha/examples/features/text/SectionPresetsExample.java:108` 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–8 lines × 4) examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:57— examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java:57-64 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:99-104 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckCharts.java:115-120 | examples/src/main/java/com/demcha/examples/flagships/EngineDeckV2Example.java:772-777 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/charts/ChartShowcaseExample.java: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 (6–8 lines × 3) examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:56— examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:56-63 | examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:88-93 | examples/src/main/java/com/demcha/examples/features/text/EmojiSvgVsPngExample.java:77-82 — 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 `examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/text/EmojiClipPathReportExample.java:87` calls `textStyle`, `builder`, `fontName` and `examples/src/main/java/com/demcha/examples/features/tables/TableAdvancedExample.java:55` 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 (4–7 lines × 6) examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:53— examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:53-59 | examples/src/main/java/com/demcha/examples/features/chrome/PageZoneExample.java:69-75 | examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:57-63 | examples/src/main/java/com/demcha/examples/features/navigation/ContainerBookmarkExample.java:53-59 | examples/src/main/java/com/demcha/examples/features/navigation/PageReferenceExample.java:50-56 | examples/src/main/java/com/demcha/examples/features/navigation/TocExample.java:53-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/chrome/PageNumberingExample.java:52` calls `withSize`, `withColor` and `examples/src/main/java/com/demcha/examples/features/chrome/ViewerPreferencesExample.java:55` 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 (7 lines × 4) examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:297— examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:297-303 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:284-290 | examples/src/main/java/com/demcha/examples/flagships/MasterShowcaseExample.java:306-312 | examples/src/main/java/com/demcha/examples/support/WeeklyScheduleRenderer.java:967-973 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/flagships/BusinessReportExample.java:297` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 7) examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:57— examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:57-63 | examples/src/main/java/com/demcha/examples/features/layout/RowColumnsExample.java:62-67 | examples/src/main/java/com/demcha/examples/features/layout/RowVerticalAlignExample.java:48-53 | examples/src/main/java/com/demcha/examples/features/navigation/ContainerBookmarkExample.java:56-61 | examples/src/main/java/com/demcha/examples/features/shapes/LineCapExample.java:50-56 | examples/src/main/java/com/demcha/examples/features/shapes/LineFillExample.java:52-58 | examples/src/main/java/com/demcha/examples/features/svg/SvgIconGalleryExample.java:105-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/src/main/java/com/demcha/examples/features/layout/BlockAlignExample.java:54` calls `parse`, `withSize`, `withColor` and `examples/src/main/java/com/demcha/examples/features/layout/RowVerticalAlignExample.java:46` 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.
Duplication concentrated across 6 sibling directories (10 clone groups) knowledge/tools/api-query/api-query.mjs:215— 10 duplicated blocks under knowledge/tools/ have copies in at least two of the sibling directories api-query, api-surface, bundle, changeset, claims, routing — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×1
Duplicated block with local edits (15 matched lines × 2 locations) knowledge/tools/api-query/api-query.mjs:215— knowledge/tools/api-query/api-query.mjs:215 · knowledge/tools/routing/lib/pack-version.mjs:30 — the two spans are one implementation copied and then locally edited — 170 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (12 lines × 2 locations) knowledge/tools/bundle/build-bundle.mjs:44— knowledge/tools/bundle/build-bundle.mjs:44 · knowledge/tools/routing/check-routes.mjs:69 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×1
Duplicated block with local edits (10 matched lines × 2 locations) knowledge/tools/api-query/api-query.mjs:342— knowledge/tools/api-query/api-query.mjs:342 · knowledge/tools/claims/check-claims.mjs:58 — the two spans are one implementation copied and then locally edited — 78 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (9 matched lines × 2 locations) · ×1
Duplicated block with local edits (9 matched lines × 2 locations) knowledge/tools/api-surface/lib/provenance.mjs:46— knowledge/tools/api-surface/lib/provenance.mjs:46 · knowledge/tools/api-surface/lib/tree.mjs:34 — the two spans are one implementation copied and then locally edited — 103 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) knowledge/tools/api-query/api-query.mjs:349— knowledge/tools/api-query/api-query.mjs:349 · knowledge/tools/routing/check-routes.mjs:107 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (6 lines × 2 locations) knowledge/tools/api-query/api-query.mjs:463— knowledge/tools/api-query/api-query.mjs:463 · knowledge/tools/api-query/api-query.mjs:470 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (5 matched lines × 2 locations) · ×1
Duplicated block with local edits (5 matched lines × 2 locations) knowledge/tools/api-query/api-query.mjs:361— knowledge/tools/api-query/api-query.mjs:361 · knowledge/tools/api-surface/lib/render-markdown.mjs:30 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (5 lines × 3 locations) knowledge/tools/api-query/api-query.mjs:95— knowledge/tools/api-query/api-query.mjs:95 · knowledge/tools/api-surface/extract-api.mjs:136 · knowledge/tools/changeset/changeset.mjs:62 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (5 lines × 2 locations) knowledge/tools/claims/lib/claims.mjs:286— knowledge/tools/claims/lib/claims.mjs:286 · knowledge/tools/claims/lib/claims.mjs:318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Complex function panelModel (cyclomatic 45, cognitive 40) REDACTED:81— panelModel has cyclomatic complexity 45 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function query (cyclomatic 37, cognitive 55) knowledge/tools/api-query/api-query.mjs:414— query has cyclomatic complexity 37 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildSurface (cyclomatic 35, cognitive 81) knowledge/tools/api-surface/extract-api.mjs:351— buildSurface has cyclomatic complexity 35 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadSurfaces (cyclomatic 23, cognitive 44) knowledge/tools/api-query/api-query.mjs:318— loadSurfaces has cyclomatic complexity 23 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 23, cognitive 32) web/examples.js:406— render has cyclomatic complexity 23 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseMember (cyclomatic 22, cognitive 27) knowledge/tools/api-surface/lib/javap.mjs:158— parseMember has cyclomatic complexity 22 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 22, cognitive 23) REDACTED:391— render has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderCard (cyclomatic 20, cognitive 17) web/examples.js:679— renderCard has cyclomatic complexity 20 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 19, cognitive 25) knowledge/tools/api-query/api-query.mjs:559— render has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function injectFullItemListJsonLd (cyclomatic 16, cognitive 33) web/examples.js:118— injectFullItemListJsonLd has cyclomatic complexity 16 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderTask (cyclomatic 16, cognitive 21) knowledge/tools/api-query/api-query.mjs:233— renderTask has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 19) REDACTED:778— (anonymous) has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function stripCommentsAndLiterals (cyclomatic 14, cognitive 29) knowledge/tools/claims/lib/claims.mjs:198— stripCommentsAndLiterals has cyclomatic complexity 14 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function membersOf (cyclomatic 14, cognitive 18) knowledge/tools/changeset/changeset.mjs:90— membersOf has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderHighlight (cyclomatic 14, cognitive 11) web/examples.js:581— renderHighlight has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function originatingBetas (cyclomatic 13, cognitive 27) knowledge/tools/api-surface/lib/stability-doc.mjs:27— originatingBetas has cyclomatic complexity 13 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function findJavap (cyclomatic 13, cognitive 22) knowledge/tools/api-surface/lib/javap.mjs:48— findJavap has cyclomatic complexity 13 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 12) knowledge/tools/claims/lib/claims.mjs:86— (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolve (cyclomatic 12, cognitive 14) REDACTED:254— resolve has cyclomatic complexity 12 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function indexParameterNames (cyclomatic 11, cognitive 22) knowledge/tools/api-surface/lib/source-names.mjs:80— indexParameterNames has cyclomatic complexity 11 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function readDeclaration (cyclomatic 11, cognitive 19) knowledge/tools/claims/lib/claims.mjs:309— readDeclaration has cyclomatic complexity 11 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderThumbnails (cyclomatic 11, cognitive 16) REDACTED:532— renderThumbnails has cyclomatic complexity 11 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onViewerClosed (cyclomatic 11, cognitive 13) web/examples.js:308— onViewerClosed has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderPanel (cyclomatic 11, cognitive 13) REDACTED:435— renderPanel has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 795 lines of code REDACTED:1— REDACTED has 795 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· knowledge/tools/api-surface/extract-api.mjs · ×1
knowledge/tools/api-surface/extract-api.mjs: 787 lines of code knowledge/tools/api-surface/extract-api.mjs:1— knowledge/tools/api-surface/extract-api.mjs has 787 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
web/examples.js: 724 lines of code web/examples.js:1— web/examples.js has 724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· knowledge/tools/api-query/api-query.mjs · ×1
knowledge/tools/api-query/api-query.mjs: 589 lines of code knowledge/tools/api-query/api-query.mjs:1— knowledge/tools/api-query/api-query.mjs has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· knowledge/tools/claims/check-claims.mjs · ×1
knowledge/tools/claims/check-claims.mjs: 463 lines of code knowledge/tools/claims/check-claims.mjs:1— knowledge/tools/claims/check-claims.mjs has 463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Third-party script without Subresource Integrity web-src/pages/index.html:390— `https://cdn.jsdelivr.net/npm/prismjs@1.29.0/components/prism-core.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 10 such include(s) across the repository's markup.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) dev-tools/PdfRebuildOpenInAdobe.java:146— The JDK merges `stderr` into `stdout` here (`redirectErrorStream(true)`), and that one stream is still a pipe — and the parent waits on `p.waitFor(…)` while nothing in this scope ever reads stdout. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the bounded wait then times out on a command that was only waiting to be read, and the output is lost. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped web/examples.js:109— `escAttr(SOURCE_TREE+encodeURIComponent(ref)+SOURCE_PATH)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Duplicated predicate templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java:265— `!trimmed.isEmpty() && Character.isLetter(trimmed.charAt(0))` appears character-identically in 2 files — templates/src/main/java/com/demcha/compose/document/templates/coverletter/presets/MonogramSidebarLetter.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MonogramSidebar.java. 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 templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java:203— `!type.isInstance(section) || isTaken(section, taken)` appears character-identically in 2 files — templates/src/main/java/com/demcha/compose/document/templates/cv/presets/MidnightNavy.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/OrangeOps.java. 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 templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java:234— `!type.isInstance(section) || section == taken` appears character-identically in 4 files — templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrange.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulse.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TerracottaRail.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGrid.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java:164— `Double.isInfinite(min) || Double.isInfinite(max)` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java, render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java:46— `Double.isNaN(baselineOffset) || Double.isInfinite(baselineOffset)` appears character-identically in 3 files — core/src/main/java/com/demcha/compose/document/node/InlineImageRun.java, core/src/main/java/com/demcha/compose/document/node/InlineShapeRun.java, core/src/main/java/com/demcha/compose/document/node/InlineSvgRun.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/node/LineNode.java:317— `Double.isNaN(value) || Double.isInfinite(value)` appears character-identically in 5 files — core/src/main/java/com/demcha/compose/document/node/LineNode.java, core/src/main/java/com/demcha/compose/document/style/DocumentPaint.java, core/src/main/java/com/demcha/compose/document/style/DocumentPathSegment.java, core/src/main/java/com/demcha/compose/document/style/DocumentTransform.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:189— `axis.baselineAtZero() && axis.min() == null` appears character-identically in 3 files — core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java, core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java, render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java:252— `axis.showGridLines() && gridStroke != null` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/chart/BarChartLayout.java, core/src/main/java/com/demcha/compose/document/chart/ChartLayoutSupport.java. 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 render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java:52— `background.getAlpha() == 0 && foreground.getAlpha() == 0` appears character-identically in 2 files — render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java, render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxBarcodeFragmentRenderHandler.java. 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 render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java:132— `cell.style().stroke() == null || cell.style().stroke().width() <= 0` appears character-identically in 2 files — render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfTableRowFragmentRenderHandler.java, render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxTableRowFragmentRenderHandler.java. 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 templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java:282— `channel.href() == null || channel.href().isBlank()` appears character-identically in 3 files — templates/src/main/java/com/demcha/compose/document/templates/cv/presets/SlateOrangeMasthead.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseMasthead.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridMasthead.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java:412— `colon > 0 && declaration.substring(0, colon).trim().equals(property)` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/svg/SvgGradients.java, core/src/main/java/com/demcha/compose/document/svg/SvgIconReader.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/layout/payloads/ShapeFragmentPayload.java:88— `cornerRadius < 0 || Double.isNaN(cornerRadius) || Double.isInfinite(cornerRadius)` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/layout/payloads/ShapeFragmentPayload.java, core/src/main/java/com/demcha/compose/document/style/ShapeOutline.java. 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 templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantText.java:31— `currencyCode == null || currencyCode.isBlank()` appears character-identically in 8 files — templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MerchantText.java, templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/MeteredText.java, templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/ObsidianText.java, templates/src/main/java/com/demcha/compose/document/templates/invoice/presets/PaymentsText.java. 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 render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java:829— `decoration == DocumentTextDecoration.BOLD || decoration == DocumentTextDecoration.BOLD_ITALIC` appears character-identically in 2 files — render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxNativeCharts.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/NavySidebarStyles.java. 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 templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseClosing.java:118— `education == null || education.entries().isEmpty()` appears character-identically in 2 files — templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseClosing.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridClosing.java. 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 templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseBody.java:171— `experience == null || experience.entries().isEmpty()` appears character-identically in 2 files — templates/src/main/java/com/demcha/compose/document/templates/cv/presets/TealPulseBody.java, templates/src/main/java/com/demcha/compose/document/templates/cv/presets/VioletGridBody.java. 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 render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java:45— `fragment.width() <= 0 || fragment.height() <= 0` appears character-identically in 11 files — render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfBarcodeFragmentRenderHandler.java, render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfEllipseFragmentRenderHandler.java, render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfImageFragmentRenderHandler.java, render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/PdfPathFragmentRenderHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/layout/MeasureResult.java:17— `height < 0 || Double.isNaN(height) || Double.isInfinite(height)` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/layout/MeasureResult.java, core/src/main/java/com/demcha/compose/document/node/SpacerNode.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java:38— `height <= 0 || Double.isNaN(height) || Double.isInfinite(height)` appears character-identically in 9 files — core/src/main/java/com/demcha/compose/document/chart/ChartPrimitive.java, core/src/main/java/com/demcha/compose/document/node/BarcodeNode.java, core/src/main/java/com/demcha/compose/document/node/CanvasLayerNode.java, core/src/main/java/com/demcha/compose/document/node/EllipseNode.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfWatermarkOptions.java:72— `imagePath != null || (imageBytes != null && imageBytes.length > 0)` appears character-identically in 3 files — core/src/main/java/com/demcha/compose/document/backend/fixed/pdf/options/PdfWatermarkOptions.java, core/src/main/java/com/demcha/compose/document/output/DocumentWatermark.java, core/src/main/java/com/demcha/compose/engine/components/content/watermark/WatermarkConfig.java. 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 render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java:144— `layer.clip() != null && !layer.clip().isEmpty()` appears character-identically in 2 files — render-pdf/src/main/java/com/demcha/compose/document/backend/fixed/pdf/handlers/InlineSvgRasters.java, render-pptx/src/main/java/com/demcha/compose/document/backend/fixed/pptx/handlers/PptxInlineSvgRasterizer.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/node/ListNode.java:93— `lineSpacing < 0 || Double.isNaN(lineSpacing) || Double.isInfinite(lineSpacing)` appears character-identically in 3 files — core/src/main/java/com/demcha/compose/document/node/ListNode.java, core/src/main/java/com/demcha/compose/document/node/ParagraphNode.java, core/src/main/java/com/demcha/compose/engine/components/content/table/TableCellLayoutStyle.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java:460— `markerGap < 0 || Double.isNaN(markerGap) || Double.isInfinite(markerGap)` appears character-identically in 2 files — core/src/main/java/com/demcha/compose/document/dsl/ListBuilder.java, core/src/main/java/com/demcha/compose/document/node/ListNode.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java:1417— `node.name() == null || node.name().isBlank()` appears character-identically in 3 files — core/src/main/java/com/demcha/compose/document/layout/LayoutCompiler.java, core/src/main/java/com/demcha/compose/document/layout/TableLayoutSupport.java, render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxLayoutMetrics.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxFontTable.java:229— `characterMapOf` swallows every exception into `return java.util.Optional.empty()` — 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 Javadoc, and the row stops firing.
Silent fallback default in catch render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:12708— `nextWordAtWordsSize` swallows every exception into `return 0` — 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 Javadoc, and the row stops firing.
Silent fallback default in catch render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:13332— `styleLineHeight` swallows every exception into `return 0` — 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 Javadoc, and the row stops firing.
Silent fallback default in catch render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxSemanticBackend.java:14628— `styleWidth` swallows every exception into `return 0` — 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 Javadoc, and the row stops firing.
Silent fallback default in catch scripts/docx-visual/edit-protocol-libreoffice.py:703— `alive` swallows every exception into `return False` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. 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 on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/docx-visual/edit-protocol-libreoffice.py:182— `clip_honoured` swallows every exception into `return False` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. 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 on the handler or in the docstring, and the row stops firing.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion templates/pom.xml:1— `templates` (63861 LoC, 256 module-visible types across 23 directories) overshoots its size bounds. 3 of 9 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 3.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/pom.xml:1— `core` (49822 LoC, 411 module-visible types across 42 directories) overshoots its size bounds. 3 of 9 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 3.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion REDACTED:1— `(repository root)` (8781 LoC, 32 module-visible types across 16 directories) overshoots its size bounds. 3 of 9 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 3.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
redundant comment knowledge/tools/api-surface/test/classifier.test.mjs:238— "B1 — type-level @Beta." repeats the code it sits on: 3 of its 3 words (type, level, beta) are already in `check(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
P10 · Library API & versioning· Implementation type on the public API · ×1
Implementation type on the public API core/src/main/java/com/demcha/compose/document/dsl/internal/BuilderSupport.java:9— 2 public types in `com.demcha.compose.document.dsl.internal` are marked as implementation by their own namespace, folder or name: `BuilderSupport` (core/src/main/java/com/demcha/compose/document/dsl/internal/BuilderSupport.java:9, `internal`), `SemanticNameNormalizer` (core/src/main/java/com/demcha/compose/document/dsl/internal/SemanticNameNormalizer.java:6, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Interpolated log message defeats structured logging render-pdf/src/main/java/com/demcha/compose/engine/render/pdf/PdfFont.java:292— `debug` at line 292 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/78 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Silent fallback default on parse failure render-docx/src/main/java/com/demcha/compose/document/backend/semantic/docx/DocxGrownLines.java:644— `number` returns `-1` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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 01a1e62b-9457-7591-9c58-f80ca83575a7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 59 · Warnings: 1266 · Recommendations: 57 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 21:02 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.