Public report of softmata/horus, 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, 20:57 UTC · Survey ID cd_77c6224b580e41c4894076d69e4dcf86
softmata/horus
Measured 16 November 2026, 20:54 UTC, at code version 39dfb3e
First survey, so nothing to compare with yet
CAI scoreStrong
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: 313,793 lines of product code in 11 projects, tests not counted · Estimated rebuild effort: about 3.9 person-years · Weakest lens: Code Health, 60.7
Findings by how serious they are
13 critical1264 serious135 minor
8 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, 20:54 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 ▸
63of 63 dimensions measured by tools.
1385of 1412 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
63dimensions across 7 lenses, read from 313,793 lines of product code in 11 projects.
softmata/horus meets our standard for a preview release. It scores 70.4 out of 100 and is rated Strong, and all 13 of its critical findings are security problems.
Code Health, at 60.7, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3.5 points. Writing log messages as searchable templates would lift Code Health itself, worth about 6.9 points. Raising Code Health to 67 would lift the score to about 73.3.
Five pipeline steps install packages that can change without warning. Three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning what the pipeline installs and passing outside input through environment variables would close both risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 313,793 lines, about €570,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 60.7 to 67, the lowest score rated Strong, the score would rise from 70.4 to about 73.3.
Code composition: what the lines of code are
Product code 73%Tests 27%
Rebuild cost: about €570,000 · Estimate
Cost to rebuild
€190,000 to €950,000, for 3,161 to 10,029 hours of work, about 3.9 person-years for 2 to 8 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
×1.0 at a score of 70. 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: 313,793 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
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Raises the score by about 3.5 points · Low effort · ADR Quality
Raises the score by about 6.9 points · Medium effort · Structured logging
3
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 €570,000 to build again, about 3.9 person-years of work. Its weakest lens is Code Health, at 60.7 (Adequate). 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
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3.5 points for low effort, because it clears the 1 ADR Quality findings. 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 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 217,816 lines over the last 90 days, which is about 883,365 lines a year. At that pace, the extra work comes to an estimated 79.4 to 476.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — 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.
311 modules, with 348 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 271 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.
horus_core.scheduling.safety_monitor uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_core.scheduling.safety_monitor, while a change to horus_core.scheduling.safety_monitor can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_core.scheduling.safety_monitor uses a module listed above it, which is the healthy direction.
horus_core.types.image_encoding uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.types.image_encoding, while a change to horus_core.types.image_encoding can't break horus_core.core.node.
Position
Below the diagonal: horus_core.types.image_encoding uses a module listed above it, which is the healthy direction.
horus_core.types.image_encoding uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.types.image_encoding, while a change to horus_core.types.image_encoding can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.types.image_encoding uses a module listed above it, which is the healthy direction.
horus_core.types.tensor uses horus_core.communication.pod, so a change to horus_core.communication.pod can break horus_core.types.tensor, while a change to horus_core.types.tensor can't break horus_core.communication.pod.
Position
Below the diagonal: horus_core.types.tensor uses a module listed above it, which is the healthy direction.
horus_core.types.tensor uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.types.tensor, while a change to horus_core.types.tensor can't break horus_core.core.node.
Position
Below the diagonal: horus_core.types.tensor uses a module listed above it, which is the healthy direction.
horus_core.types.tensor uses horus_core.types.device, so a change to horus_core.types.device can break horus_core.types.tensor, while a change to horus_core.types.tensor can't break horus_core.types.device.
Position
Below the diagonal: horus_core.types.tensor uses a module listed above it, which is the healthy direction.
horus_core.types.tensor uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.types.tensor, while a change to horus_core.types.tensor can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.types.tensor uses a module listed above it, which is the healthy direction.
horus_manager.discovery uses horus_core.core.node, so a change to horus_core.core.node can break horus_manager.discovery, while a change to horus_manager.discovery can't break horus_core.core.node.
Position
Below the diagonal: horus_manager.discovery uses a module listed above it, which is the healthy direction.
horus_manager.discovery uses horus_manager.commands.doc_extract, so a change to horus_manager.commands.doc_extract can break horus_manager.discovery, while a change to horus_manager.discovery can't break horus_manager.commands.doc_extract.
Position
Below the diagonal: horus_manager.discovery uses a module listed above it, which is the healthy direction.
horus_manager.manifest uses horus_sys.sync, so a change to horus_sys.sync can break horus_manager.manifest, while a change to horus_manager.manifest can't break horus_sys.sync.
Position
Below the diagonal: horus_manager.manifest uses a module listed above it, which is the healthy direction.
horus_net.wire uses horus_net.priority, so a change to horus_net.priority can break horus_net.wire, while a change to horus_net.wire can't break horus_net.priority.
Position
Below the diagonal: horus_net.wire uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_pool uses horus_core.types.device, so a change to horus_core.types.device can break horus_core.memory.tensor_pool, while a change to horus_core.memory.tensor_pool can't break horus_core.types.device.
Position
Below the diagonal: horus_core.memory.tensor_pool uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_pool uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.tensor_pool, while a change to horus_core.memory.tensor_pool can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.tensor_pool uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_pool uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.memory.tensor_pool, while a change to horus_core.memory.tensor_pool can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.memory.tensor_pool uses a module listed above it, which is the healthy direction.
horus_core.scheduling.types uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.scheduling.types, while a change to horus_core.scheduling.types can't break horus_core.core.node.
Position
Below the diagonal: horus_core.scheduling.types uses a module listed above it, which is the healthy direction.
horus_core.scheduling.types uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_core.scheduling.types, while a change to horus_core.scheduling.types can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_core.scheduling.types uses a module listed above it, which is the healthy direction.
horus_core.scheduling.types uses horus_core.scheduling.safety_monitor, so a change to horus_core.scheduling.safety_monitor can break horus_core.scheduling.types, while a change to horus_core.scheduling.types can't break horus_core.scheduling.safety_monitor.
Position
Below the diagonal: horus_core.scheduling.types uses a module listed above it, which is the healthy direction.
horus_core.types.action_chunk uses horus_core.communication.pod, so a change to horus_core.communication.pod can break horus_core.types.action_chunk, while a change to horus_core.types.action_chunk can't break horus_core.communication.pod.
Position
Below the diagonal: horus_core.types.action_chunk uses a module listed above it, which is the healthy direction.
horus_core.types.action_chunk uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.types.action_chunk, while a change to horus_core.types.action_chunk can't break horus_core.core.node.
Position
Below the diagonal: horus_core.types.action_chunk uses a module listed above it, which is the healthy direction.
horus_core.types.action_chunk uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.types.action_chunk, while a change to horus_core.types.action_chunk can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.types.action_chunk uses a module listed above it, which is the healthy direction.
horus_core.types.image_descriptor uses horus_core.communication.pod, so a change to horus_core.communication.pod can break horus_core.types.image_descriptor, while a change to horus_core.types.image_descriptor can't break horus_core.communication.pod.
Position
Below the diagonal: horus_core.types.image_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.image_descriptor uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.types.image_descriptor, while a change to horus_core.types.image_descriptor can't break horus_core.core.node.
Position
Below the diagonal: horus_core.types.image_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.image_descriptor uses horus_core.types.image_encoding, so a change to horus_core.types.image_encoding can break horus_core.types.image_descriptor, while a change to horus_core.types.image_descriptor can't break horus_core.types.image_encoding.
Position
Below the diagonal: horus_core.types.image_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.image_descriptor uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.types.image_descriptor, while a change to horus_core.types.image_descriptor can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.types.image_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.pointcloud_descriptor uses horus_core.communication.pod, so a change to horus_core.communication.pod can break horus_core.types.pointcloud_descriptor, while a change to horus_core.types.pointcloud_descriptor can't break horus_core.communication.pod.
Position
Below the diagonal: horus_core.types.pointcloud_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.pointcloud_descriptor uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.types.pointcloud_descriptor, while a change to horus_core.types.pointcloud_descriptor can't break horus_core.core.node.
Position
Below the diagonal: horus_core.types.pointcloud_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.pointcloud_descriptor uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.types.pointcloud_descriptor, while a change to horus_core.types.pointcloud_descriptor can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.types.pointcloud_descriptor uses a module listed above it, which is the healthy direction.
horus_core.types.pointcloud_descriptor uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.types.pointcloud_descriptor, while a change to horus_core.types.pointcloud_descriptor can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.types.pointcloud_descriptor uses a module listed above it, which is the healthy direction.
horus_manager.dispatch uses horus_manager.manifest, so a change to horus_manager.manifest can break horus_manager.dispatch, while a change to horus_manager.dispatch can't break horus_manager.manifest.
Position
Below the diagonal: horus_manager.dispatch uses a module listed above it, which is the healthy direction.
horus_net.optimize uses horus_net.priority, so a change to horus_net.priority can break horus_net.optimize, while a change to horus_net.optimize can't break horus_net.priority.
Position
Below the diagonal: horus_net.optimize uses a module listed above it, which is the healthy direction.
horus_net.optimize uses horus_net.wire, so a change to horus_net.wire can break horus_net.optimize, while a change to horus_net.optimize can't break horus_net.wire.
Position
Below the diagonal: horus_net.optimize uses a module listed above it, which is the healthy direction.
horus_core.memory.depth_image uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.depth_image, while a change to horus_core.memory.depth_image can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.depth_image uses a module listed above it, which is the healthy direction.
horus_core.memory.depth_image uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.memory.depth_image, while a change to horus_core.memory.depth_image can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.memory.depth_image uses a module listed above it, which is the healthy direction.
horus_core.memory.image uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.image, while a change to horus_core.memory.image can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.image uses a module listed above it, which is the healthy direction.
horus_core.memory.image uses horus_core.types.image_encoding, so a change to horus_core.types.image_encoding can break horus_core.memory.image, while a change to horus_core.memory.image can't break horus_core.types.image_encoding.
Position
Below the diagonal: horus_core.memory.image uses a module listed above it, which is the healthy direction.
horus_core.memory.image uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.memory.image, while a change to horus_core.memory.image can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.memory.image uses a module listed above it, which is the healthy direction.
horus_core.memory.image uses horus_core.types.image_descriptor, so a change to horus_core.types.image_descriptor can break horus_core.memory.image, while a change to horus_core.memory.image can't break horus_core.types.image_descriptor.
Position
Below the diagonal: horus_core.memory.image uses a module listed above it, which is the healthy direction.
horus_core.memory.pointcloud uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.pointcloud, while a change to horus_core.memory.pointcloud can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.pointcloud uses a module listed above it, which is the healthy direction.
horus_core.memory.pointcloud uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.memory.pointcloud, while a change to horus_core.memory.pointcloud can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.memory.pointcloud uses a module listed above it, which is the healthy direction.
horus_core.memory.pointcloud uses horus_core.types.pointcloud_descriptor, so a change to horus_core.types.pointcloud_descriptor can break horus_core.memory.pointcloud, while a change to horus_core.memory.pointcloud can't break horus_core.types.pointcloud_descriptor.
Position
Below the diagonal: horus_core.memory.pointcloud uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_handle uses horus_core.types.device, so a change to horus_core.types.device can break horus_core.memory.tensor_handle, while a change to horus_core.memory.tensor_handle can't break horus_core.types.device.
Position
Below the diagonal: horus_core.memory.tensor_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_handle uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.tensor_handle, while a change to horus_core.memory.tensor_handle can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.tensor_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_handle uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.memory.tensor_handle, while a change to horus_core.memory.tensor_handle can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.memory.tensor_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.tensor_handle uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.memory.tensor_handle, while a change to horus_core.memory.tensor_handle can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.memory.tensor_handle uses a module listed above it, which is the healthy direction.
horus_core.scheduling.primitives uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_core.scheduling.primitives, while a change to horus_core.scheduling.primitives can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_core.scheduling.primitives uses a module listed above it, which is the healthy direction.
horus_core.scheduling.primitives uses horus_core.scheduling.safety_monitor, so a change to horus_core.scheduling.safety_monitor can break horus_core.scheduling.primitives, while a change to horus_core.scheduling.primitives can't break horus_core.scheduling.safety_monitor.
Position
Below the diagonal: horus_core.scheduling.primitives uses a module listed above it, which is the healthy direction.
horus_core.scheduling.primitives uses horus_core.scheduling.types, so a change to horus_core.scheduling.types can break horus_core.scheduling.primitives, while a change to horus_core.scheduling.primitives can't break horus_core.scheduling.types.
Position
Below the diagonal: horus_core.scheduling.primitives uses a module listed above it, which is the healthy direction.
horus_net.replicator uses horus_net.config, so a change to horus_net.config can break horus_net.replicator, while a change to horus_net.replicator can't break horus_net.config.
Position
Below the diagonal: horus_net.replicator uses a module listed above it, which is the healthy direction.
horus_net.replicator uses horus_net.wire, so a change to horus_net.wire can break horus_net.replicator, while a change to horus_net.replicator can't break horus_net.wire.
Position
Below the diagonal: horus_net.replicator uses a module listed above it, which is the healthy direction.
horus_net.replicator uses horus_net.optimize, so a change to horus_net.optimize can break horus_net.replicator, while a change to horus_net.replicator can't break horus_net.optimize.
Position
Below the diagonal: horus_net.replicator uses a module listed above it, which is the healthy direction.
horus_core.memory.action_chunk_handle uses horus_core.types.device, so a change to horus_core.types.device can break horus_core.memory.action_chunk_handle, while a change to horus_core.memory.action_chunk_handle can't break horus_core.types.device.
Position
Below the diagonal: horus_core.memory.action_chunk_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.action_chunk_handle uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.memory.action_chunk_handle, while a change to horus_core.memory.action_chunk_handle can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.memory.action_chunk_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.action_chunk_handle uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.memory.action_chunk_handle, while a change to horus_core.memory.action_chunk_handle can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.memory.action_chunk_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.action_chunk_handle uses horus_core.types.action_chunk, so a change to horus_core.types.action_chunk can break horus_core.memory.action_chunk_handle, while a change to horus_core.memory.action_chunk_handle can't break horus_core.types.action_chunk.
Position
Below the diagonal: horus_core.memory.action_chunk_handle uses a module listed above it, which is the healthy direction.
horus_core.memory.action_chunk_handle uses horus_core.memory.tensor_handle, so a change to horus_core.memory.tensor_handle can break horus_core.memory.action_chunk_handle, while a change to horus_core.memory.action_chunk_handle can't break horus_core.memory.tensor_handle.
Position
Below the diagonal: horus_core.memory.action_chunk_handle uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.communication.topic.header, so a change to horus_core.communication.topic.header can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.communication.topic.header.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.communication.topic.local_state, so a change to horus_core.communication.topic.local_state can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.communication.topic.local_state.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.core.node.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.types.device, so a change to horus_core.types.device can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.types.device.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.types.dtype, so a change to horus_core.types.dtype can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.types.dtype.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.depth_image, so a change to horus_core.memory.depth_image can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.depth_image.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.image, so a change to horus_core.memory.image can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.image.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.pointcloud, so a change to horus_core.memory.pointcloud can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.pointcloud.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.tensor_handle, so a change to horus_core.memory.tensor_handle can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.tensor_handle.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic uses horus_core.memory.action_chunk_handle, so a change to horus_core.memory.action_chunk_handle can break horus_core.communication.topic, while a change to horus_core.communication.topic can't break horus_core.memory.action_chunk_handle.
Position
Below the diagonal: horus_core.communication.topic uses a module listed above it, which is the healthy direction.
horus_core.communication.topic.dispatch uses horus_core.communication.topic.header, so a change to horus_core.communication.topic.header can break horus_core.communication.topic.dispatch, while a change to horus_core.communication.topic.dispatch can't break horus_core.communication.topic.header.
Position
Below the diagonal: horus_core.communication.topic.dispatch uses a module listed above it, which is the healthy direction.
horus_core.communication.topic.dispatch uses horus_core.communication.topic.local_state, so a change to horus_core.communication.topic.local_state can break horus_core.communication.topic.dispatch, while a change to horus_core.communication.topic.dispatch can't break horus_core.communication.topic.local_state.
Position
Below the diagonal: horus_core.communication.topic.dispatch uses a module listed above it, which is the healthy direction.
horus_core.communication.topic.dispatch uses horus_core.types.tensor, so a change to horus_core.types.tensor can break horus_core.communication.topic.dispatch, while a change to horus_core.communication.topic.dispatch can't break horus_core.types.tensor.
Position
Below the diagonal: horus_core.communication.topic.dispatch uses a module listed above it, which is the healthy direction.
horus_core.communication.topic.dispatch uses horus_core.memory.tensor_pool, so a change to horus_core.memory.tensor_pool can break horus_core.communication.topic.dispatch, while a change to horus_core.communication.topic.dispatch can't break horus_core.memory.tensor_pool.
Position
Below the diagonal: horus_core.communication.topic.dispatch uses a module listed above it, which is the healthy direction.
horus_core.communication.topic.dispatch uses horus_core.communication.topic, so a change to horus_core.communication.topic can break horus_core.communication.topic.dispatch, while a change to horus_core.communication.topic.dispatch can't break horus_core.communication.topic.
Position
Below the diagonal: horus_core.communication.topic.dispatch uses a module listed above it, which is the healthy direction.
horus_core.error uses horus_core.communication.topic, so a change to horus_core.communication.topic can break horus_core.error, while a change to horus_core.error can't break horus_core.communication.topic.
Position
Below the diagonal: horus_core.error uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_core.core.node, so a change to horus_core.core.node can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.core.node.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_sys.rt, so a change to horus_sys.rt can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_sys.rt.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_core.scheduling.safety_monitor, so a change to horus_core.scheduling.safety_monitor can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.scheduling.safety_monitor.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_core.scheduling.types, so a change to horus_core.scheduling.types can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.scheduling.types.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
horus_core.scheduling.scheduler uses horus_core.communication.topic, so a change to horus_core.communication.topic can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.communication.topic.
Position
Below the diagonal: horus_core.scheduling.scheduler uses a module listed above it, which is the healthy direction.
38→39 horus_core.scheduling.scheduler uses horus_core.scheduling.node_builderpart of a loop✕
Connections
2 pairs of types, where a type in horus_core.scheduling.scheduler uses a type in horus_core.scheduling.node_builder.
horus_core.scheduling.scheduler uses horus_core.scheduling.node_builder, so a change to horus_core.scheduling.node_builder can break horus_core.scheduling.scheduler, while a change to horus_core.scheduling.scheduler can't break horus_core.scheduling.node_builder.
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.
horus_core.scheduling.node_builder uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_core.scheduling.node_builder, while a change to horus_core.scheduling.node_builder can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_core.scheduling.node_builder uses a module listed above it, which is the healthy direction.
horus_core.scheduling.node_builder uses horus_core.scheduling.safety_monitor, so a change to horus_core.scheduling.safety_monitor can break horus_core.scheduling.node_builder, while a change to horus_core.scheduling.node_builder can't break horus_core.scheduling.safety_monitor.
Position
Below the diagonal: horus_core.scheduling.node_builder uses a module listed above it, which is the healthy direction.
horus_core.scheduling.node_builder uses horus_core.scheduling.types, so a change to horus_core.scheduling.types can break horus_core.scheduling.node_builder, while a change to horus_core.scheduling.node_builder can't break horus_core.scheduling.types.
Position
Below the diagonal: horus_core.scheduling.node_builder uses a module listed above it, which is the healthy direction.
horus_core.scheduling.node_builder uses horus_core.scheduling.scheduler, so a change to horus_core.scheduling.scheduler can break horus_core.scheduling.node_builder, while a change to horus_core.scheduling.node_builder can't break horus_core.scheduling.scheduler.
Position
Below the diagonal: horus_core.scheduling.node_builder uses a module listed above it, which is the healthy direction.
horus_cpp.types_ffi uses horus_core.communication.pod, so a change to horus_core.communication.pod can break horus_cpp.types_ffi, while a change to horus_cpp.types_ffi can't break horus_core.communication.pod.
Position
Below the diagonal: horus_cpp.types_ffi uses a module listed above it, which is the healthy direction.
horus_cpp.types_ffi uses horus_core.core.rt_node, so a change to horus_core.core.rt_node can break horus_cpp.types_ffi, while a change to horus_cpp.types_ffi can't break horus_core.core.rt_node.
Position
Below the diagonal: horus_cpp.types_ffi uses a module listed above it, which is the healthy direction.
horus_cpp.types_ffi uses horus_core.scheduling.scheduler, so a change to horus_core.scheduling.scheduler can break horus_cpp.types_ffi, while a change to horus_cpp.types_ffi can't break horus_core.scheduling.scheduler.
Position
Below the diagonal: horus_cpp.types_ffi uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 60.7 · Adequate · gated by D2, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
28
Medium
A05:2025 — Injection
14
High / Critical
A02:2025 — Security Misconfiguration
3
High / Critical
A01:2025 — Broken Access Control
1
Medium
Roadmap
Top priorities: Interpolated log message defeats structured logging; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Bring the 6 bodies over 120 down to 120 or less in Cognitive Complexity — start with horus_manager::commands::check::check_manifest_file (cognitive 253), horus_manager::run_command (cognitive 240), horus_manager::commands::check::check_workspace (cognitive 218).
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 — 13
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 — 1264
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 — 135
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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 63 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 — 63 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, 1385 of 1412 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — horus_manager/tests/web_e2e/ (puppeteer) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`cargo llvm-cov`), uploaded by `codecov/codecov-action` and a Codecov configuration (.github/codecov.yml, target 60%) shows coverage is measured in your own CI.
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 46 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 359 test source file(s) (.rs, .py) 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. Test source is present (.rs, .py, .js) and this repository declares a Cargo test suite (repository root, 547 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 (4 contributor(s) across 661 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 3 hold 3.7% 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. 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
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.
X3 Exception handling — 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.
X5 Nullable reference types — 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. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
125 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was horus_manager::run_command at 215. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PyTopic::backend_type at 81 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: horus_core/src/error.rs (HorusError::help at 44), horus_cpp_macros/src/cpp_gen.rs (horus_cpp_macros::cpp_gen::type_to_cpp at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with horus_manager::run_command (cyclomatic 215). — Refactoring it lifts Cyclomatic Complexity from 5.2 to about 5.8/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.
+ 55 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 120 down to 120 or less in Cognitive Complexity — start with horus_manager::commands::check::check_manifest_file (cognitive 253), horus_manager::run_command (cognitive 240), horus_manager::commands::check::check_workspace (cognitive 218). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 2.8 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 45 FunctionTooLong finding(s) in God Classes — start with REDACTED (5), pkg.rs (4), helpers.rs (4). — One of this dimension's main actionable groups (45 warning-level).
Resolve the 44 FileTooLong finding(s) in God Classes — start with mod.rs (5), install.rs (2), topic.rs (2). — One of this dimension's main actionable groups (44 warning-level).
Resolve the 19 MethodTooLong finding(s) in God Classes — start with install.rs (4), mod.rs (3), topic.rs (3). — One of this dimension's main actionable groups (19 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.
325 duplicated block group(s) detected. 4.0 % of the production lines (12,553 of 313,793) are in a reported copy. A further 178 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 503 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.
+ 185 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 23 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with install.rs (3), pkg.rs (2), main.rs (2). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 22 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with pkg.rs (3), deploy.rs (3), msg.rs (2). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 22 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with pkg.rs (2), deploy.rs (2), presence.rs. — One of this dimension's main actionable groups (22 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 1 serious finding✓ 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.
11 production modules (Cargo+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 8 of the 11 (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: horus_sys
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with node_builder.rs, node.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test 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, 43 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 46 tests (1 harness-style project(s) excluded from the assertion penalty). Measured on the JavaScript/TypeScript suite only — at least 359 test source file(s) (.rs, .py) went unread, so its test quality is unmeasured and is not in these counts.
No direct assertions: page loads with correct title · ×43horus_manager/tests/web_e2e/basic.test.js:25
Test project verifies nothing: horus_manager/tests/web_e2ehorus_manager/tests/web_e2e/basic.test.js:25
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
20 outdated, 0 yanked direct Cargo dependencies. 65 of 68 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: ctor · ×20
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 418 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 2 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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: horus_manager/src/main.rs (29×215=6235); horus_core/src/scheduling/scheduler/mod.rs (53×48=2544); horus_core/src/scheduling/rt_executor.rs (33×61=2013) Repeated repair below the complexity floor: horus_core/src/memory/tensor_pool.rs (19 of 32 changes were fixes); horus_sys/src/shm/mod.rs (14 of 26 changes were fixes); horus_net/src/estop.rs (7 of 13 changes were fixes)
Resolve the 45 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (5), install.rs (2), topic.rs (2). — One of this dimension's main actionable groups (45 warning-level).
Resolve the 34 Repeated repair finding(s) in Churn × Complexity Hotspots — start with mod.rs (4), tensor_pool.rs, estop.rs. — One of this dimension's main actionable groups (34 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.
7 deducted task-comment markers across 313793 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.
Resolve the 7 TodoComment finding(s) in Explicit Debt — start with doc_extract_cpp.rs (3), doc_extract_rust.rs (2), doc_extract_python.rs. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 21 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion4.5 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
3 of 11 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3horus_manager/Cargo.toml:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (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: 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).
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 1 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) — `install.sh` (line 520, line 791), `scripts/deps.sh` (line 18, line 19, line 20, …), `uninstall.sh` (line 120) — 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 14 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
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 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).
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 12 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 321 of the 360 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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, 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.
`set_realtime_priority`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it. — horus_sys/src/rt/macos.rs:56
`lock_memory`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it. — horus_sys/src/rt/macos.rs:75
What to do
Finish or delete the functions that are still `todo!()`/`unimplemented!()` or panic "not implemented", and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls 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.
`warn_abandoned_claim` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/communication/topic/dispatch.rs:843
`decrement_to_floor` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/communication/topic/header.rs:206
`mark_thread_live` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/communication/topic/header.rs:2437
`try_init_log_bridge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/core/log_bridge.rs:127
`set_blackbox_hook` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×2) — horus_core/src/scheduling/blackbox.rs:16, horus_core/src/scheduling/mod.rs:263
`impl TelemetryManager` has 6 unfinished methods out of 8 — a scaffolded type that was never implemented. — horus_core/src/scheduling/mod.rs:84
`set_scheduler_name` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:88
`counter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:89
`gauge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:90
`counter_with_labels` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:91
`gauge_with_labels` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:98
`export` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — horus_core/src/scheduling/mod.rs:108
`record` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:217
`record_prestamped` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:223
`load` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — horus_core/src/scheduling/mod.rs:240
`record_external_event` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/mod.rs:266
`set_network_auto_wire` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_core/src/scheduling/scheduler/mod.rs:38
`pointcloud_destroy` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_cpp/src/pool_ffi.rs:179
`remove_generated_build_configs` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_manager/src/cargo_gen.rs:875
`error` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_manager/src/cli_output.rs:23
`warn` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_manager/src/cli_output.rs:28
`suggest_install` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_manager/src/commands/deps.rs:375
`write_head` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — horus_manager/src/commands/doc_extract_html.rs:48
`wait_for_oauth_callback` does real work, but one of its branches is `Err` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — REDACTED:277
`nodes_to_features` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — horus_manager/src/node_detector.rs:130
`register_custom_messages` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — horus_py/src/custom_messages/mod.rs:19
`set_realtime_priority`'s whole body panics or returns an error whose message says it isn't finished — a not-implemented stub in ordinary clothes. Implement it or remove it. — horus_sys/src/rt/macos.rs:56
`lock_memory`'s whole body panics or returns an error whose message says it isn't finished — a not-implemented stub in ordinary clothes. Implement it or remove it. — horus_sys/src/rt/macos.rs:75
`set_best_effort_class` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — horus_sys/src/rt/macos.rs:114
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
`for tool in cargo python3 cmake g++ clang-format clang-tidy; do` invokes clang-format in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--dry-run --Werror` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:124
`for tool in cargo rustfmt cargo-clippy python3 cmake g++ clang-format; do` invokes clang-format in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--dry-run --Werror` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:184
What to do
Add `--dry-run --Werror` to the clang-format step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
Add `--dry-run --Werror` to the clang-format step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.0 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`render_rust` is public and takes `t: &Type` from its caller, and it calls itself at line 23 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `render_rust` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — horus_manager/src/msgspec/canonical.rs:23
`render_cpp` is public and takes `t: &Type` from its caller, and it calls itself at line 35 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `render_cpp` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — horus_manager/src/msgspec/canonical.rs:35
`size_align` is public and takes `t: &Type` from its caller, and it calls itself at line 43 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `size_align` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — horus_manager/src/msgspec/layout.rs:43
`as_slice_mut` is public and takes a `ShmRegion` as its receiver from its caller, and it calls itself at line 113 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice_mut` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — horus_core/src/memory/shm_region.rs:113
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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.
`mem::forget(msg)` (line 687) takes `msg` out of Rust's ownership: its `Drop` never runs, so whatever it holds — a descriptor, a socket, a buffer, a lock — is never given back, and nothing can give it back later because the value is gone. Let it drop (or call its explicit close) where its work ends; if the handle must outlive this function, turn it into a raw handle with `into_raw`/`into_raw_fd` and reclaim it with the matching `from_raw` when the owner is done. — horus_core/src/communication/topic/mod.rs:687
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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.
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.
`ActionServerConfig.result_history_size` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_core/src/actions/types.rs:348
`NodeTickSnapshot.duration_ns` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_core/src/scheduling/record_replay.rs:397
`RuntimeCapabilities.is_linux` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_core/src/scheduling/rt.rs:344
`PointCloudDescriptor.field_count` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_core/src/types/pointcloud_descriptor.rs:49
`PointCloudDescriptor.is_dense` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_core/src/types/pointcloud_descriptor.rs:51
`ToolchainPins.cmake` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/lockfile.rs:92
`DriverTableConfig.topic_state` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/manifest.rs:923
`DriverTableConfig.topic_command` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/manifest.rs:926
`DriverTableConfig.simulated` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/manifest.rs:941
`PluginRegistry.schema_version` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/plugins/registry.rs:20
`PluginRegistry.project_name` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/plugins/registry.rs:27
`PluginRegistry.horus_version` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/plugins/registry.rs:30
`InstallManifest.installed_at` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_manager/src/version.rs:134
`Clock._pad` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:64
`SimSync.sim_time_ns` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:415
`SimSync._pad` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:421
`RateRequest.desired_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:480
`RateRequest.min_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:482
`RateRequest.max_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:484
`RateRequest.requester_id` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — horus_types/src/time.rs:486
What to do
Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` 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.
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.
`info!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:185
`warn!` at line 199 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:199
`error!` at line 205 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:205
`error!` at line 247 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:247
`warn!` at line 267 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:267
`info!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:282
`warn!` at line 307 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/drivers/exec_driver.rs:307
`warn!` at line 1203 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/dispatch.rs:1203
`warn!` at line 1325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/dispatch.rs:1325
`warn!` at line 1894 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/dispatch.rs:1894
`warn!` at line 2636 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/dispatch.rs:2636
`warn!` at line 2204 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/mod.rs:2204
`warn!` at line 3639 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — horus_core/src/communication/topic/mod.rs:3639
Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`std::time::SystemTime::now().duration_since(std::time::UNIX_EPOCH)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `timestamp_now` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_types/src/diagnostics.rs:14
`src.find("\nclass Node:")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `node_class_body` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_py/src/python_api_docs.rs:34
`class_body.find("\n def __init__(")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `init_annotation` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_py/src/python_api_docs.rs:104
`class_body[at..].find("\"\"\"")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `init_annotation` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_py/src/python_api_docs.rs:107
`std::ffi::CString::new("topic endpoint host ignored")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_py/src/topic.rs:724
`self.pending.remove(&key)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `feed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_net/src/fragment.rs:281
`writeln!(cargo,"# Generated by horus from horus.toml — do not edit manually.\n\
# Edits are lost on the next build; add a [rust] section to horus.toml instead.")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:55
`writeln!(cargo,"[package]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:56
`writeln!(cargo,"name = \"{}\"",sanitize_cargo_name(project_name))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:57
`writeln!(cargo,"version = \"{}\"",version)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:58
`writeln!(cargo,"edition = \"{}\"",rust_edition(manifest))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:59
`writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). (×3) — horus_manager/src/cargo_gen.rs:60, horus_manager/src/cargo_gen.rs:65, horus_manager/src/cargo_gen.rs:154
`writeln!(cargo,"[workspace]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:64
`writeln!(cargo,"[dependencies]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:132
`writeln!(cargo,"[dev-dependencies]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:155
`writeln!(wanted,"!{name}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `ignore_generated_dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:352
`writeln!(text,"{GENERATED_CARGO_CONFIG_HEADER}\n\
# Edits are lost on the next build; change [rust].rustflags instead.")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:852
`writeln!(text,"[build]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:853
`writeln!(text,"rustflags = {}",toml::Value::from(flags.to_vec()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:856
`writeln!(cargo,"\n# Driver dependencies (from [hardware], or legacy [drivers])")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:964
`writeln!(cargo,"{} = \"{}\"",crate_name,ver)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:968
`writeln!(cargo,"{} = {{ version = \"{}\", features = [{}] }}",crate_name,ver,features_str)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:980
`writeln!(cargo,"[[{kind}]]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_target_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1013
`writeln!(cargo,"name = \"{}\"",sanitize_cargo_name(name))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_target_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1014
`writeln!(cargo,"path = \"{}\"",toml_path(path))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_target_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1015
`writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_target_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1016
`writeln!(cargo,"[lib]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_layout_targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1047
`writeln!(cargo,"path = \"{}\"",toml_path(relative_to_horus(&lib,horus_dir)))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_layout_targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1053
`writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_layout_targets` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1054
`writeln!(cargo,"serde = {{ version = \"1\", features = [\"derive\"] }}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_implicit_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1141
`writeln!(cargo,"{}_msgs = {{ path = \"{}\" }}",sanitize_cargo_name(&manifest.package.name),toml_path(generated.display()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_msgs_dep` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1227
`writeln!(cargo,"{} = {{ path = \"{}\", features = [{}] }}",dep_name,toml_path(dep_path.display()),hw_features.iter().map(|f|format!("\"{}\"",f)).collect::<Vec<_>>().join(", "))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_horus_path_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1249
`writeln!(cargo,"{} = {{ path = \"{}\" }}",dep_name,toml_path(dep_path.display()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_horus_path_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1257
`writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_rust_passthrough` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1390
`writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_patch_sections` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1448
`writeln!(cargo,"[patch.\"{}\"]",git_url)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_patch_sections` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1449
`writeln!(cargo,"{} = {{ path = \"{}\" }}",name,toml_path(horus_source.join(name).display()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_patch_sections` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1457
`writeln!(cargo,"{key} = {value}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_patch_sections` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — horus_manager/src/cargo_gen.rs:1472
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 5 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Python 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no interface, protocol or abstract type declares an operation an implementer must write
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Python, Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (horus_core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 24 value object(s); 7 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface: 329 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 Python and Rust were read, and no request in it can be cancelled by a caller — 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; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 1% of this repository's production lines — rust (309,960 lines), cpp (2,635 lines), c (590 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
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.
horus_manager::commands::check::check_manifest_file (cognitive 253) horus_manager/src/commands/check.rs:1054— horus_manager::commands::check::check_manifest_file has cognitive complexity 253 (threshold 15). Drivers by points: if/else 92 (197 pts), loops 14 (31 pts), match/switch 6 (18 pts), boolean chains 7 (nesting depth added 134). 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.
horus_manager::run_command (cognitive 240) horus_manager/src/main.rs:2469— horus_manager::run_command has cognitive complexity 240 (threshold 15). Drivers by points: if/else 79 (164 pts), match/switch 32 (65 pts), loops 2 (7 pts), boolean chains 4 (nesting depth added 123). 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.
horus_manager::commands::check::check_workspace (cognitive 218) horus_manager/src/commands/check.rs:321— horus_manager::commands::check::check_workspace has cognitive complexity 218 (threshold 15). Drivers by points: if/else 57 (145 pts), loops 13 (41 pts), match/switch 6 (23 pts), boolean chains 9 (nesting depth added 133). 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.
horus_manager::commands::launch::run_launch (cognitive 159) horus_manager/src/commands/launch.rs:370— horus_manager::commands::launch::run_launch has cognitive complexity 159 (threshold 15). Drivers by points: if/else 39 (118 pts), loops 12 (22 pts), match/switch 5 (16 pts), boolean chains 3 (nesting depth added 100). 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.
horus_manager::discovery::nodes::discover_nodes_uncached (cognitive 107) horus_manager/src/discovery/nodes.rs:3— horus_manager::discovery::nodes::discover_nodes_uncached has cognitive complexity 107 (threshold 15). Drivers by points: if/else 25 (73 pts), loops 9 (19 pts), match/switch 3 (8 pts), boolean chains 7 (nesting depth added 63). 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.
horus_manager::commands::run::run_rust::execute_build_only (cognitive 86) horus_manager/src/commands/run/run_rust.rs:190— horus_manager::commands::run::run_rust::execute_build_only has cognitive complexity 86 (threshold 15). Drivers by points: if/else 33 (83 pts), match/switch 2 (3 pts) (nesting depth added 51). 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.
horus_manager::commands::plugin::run_info_unified (cognitive 83) horus_manager/src/commands/plugin.rs:260— horus_manager::commands::plugin::run_info_unified has cognitive complexity 83 (threshold 15). Drivers by points: if/else 22 (77 pts), loops 2 (4 pts), match/switch 2 (nesting depth added 57). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
horus_manager::commands::msg::parse_messages_from_source (cognitive 82) horus_manager/src/commands/msg.rs:751— horus_manager::commands::msg::parse_messages_from_source has cognitive complexity 82 (threshold 15). Drivers by points: if/else 16 (64 pts), loops 4 (12 pts), boolean chains 6 (nesting depth added 56). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
horus_manager::commands::action::discover_actions (cognitive 77) horus_manager/src/commands/action.rs:37— horus_manager::commands::action::discover_actions has cognitive complexity 77 (threshold 15). Drivers by points: if/else 12 (46 pts), loops 9 (22 pts), match/switch 2 (7 pts), boolean chains 2 (nesting depth added 52). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_manager::commands::pkg::run_list (cognitive 75) horus_manager/src/commands/pkg.rs:1724— horus_manager::commands::pkg::run_list has cognitive complexity 75 (threshold 15). Drivers by points: if/else 27 (60 pts), loops 5 (13 pts), boolean chains 2 (nesting depth added 41). 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.
horus_manager::commands::node::list_nodes (cognitive 73) horus_manager/src/commands/node.rs:64— horus_manager::commands::node::list_nodes has cognitive complexity 73 (threshold 15). Drivers by points: if/else 23 (47 pts), loops 5 (15 pts), match/switch 5 (11 pts) (nesting depth added 40). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_manager::commands::run::deps::split_dependencies_with_context (cognitive 64) horus_manager/src/commands/run/deps.rs:424— horus_manager::commands::run::deps::split_dependencies_with_context has cognitive complexity 64 (threshold 15). Drivers by points: if/else 20 (52 pts), match/switch 3 (9 pts), boolean chains 2, loops 1 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_manager::commands::record::run_inject (cognitive 63) horus_manager/src/commands/record.rs:719— horus_manager::commands::record::run_inject has cognitive complexity 63 (threshold 15). Drivers by points: if/else 24 (46 pts), match/switch 3 (8 pts), loops 3 (7 pts), boolean chains 2 (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.
horus_manager::commands::clean::run_clean (cognitive 58) horus_manager/src/commands/clean.rs:13— horus_manager::commands::clean::run_clean has cognitive complexity 58 (threshold 15). Drivers by points: if/else 23 (44 pts), boolean chains 8, loops 2 (6 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.
horus_manager::registry::helpers::prompt_package_metadata (cognitive 58) horus_manager/src/registry/helpers.rs:1349— horus_manager::registry::helpers::prompt_package_metadata has cognitive complexity 58 (threshold 15). Drivers by points: if/else 28 (51 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (2 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.
horus_manager::commands::run::run_rust::execute_with_scheduler (cognitive 57) horus_manager/src/commands/run/run_rust.rs:896— horus_manager::commands::run::run_rust::execute_with_scheduler has cognitive complexity 57 (threshold 15). Drivers by points: if/else 20 (56 pts), match/switch 1 (nesting depth added 36). 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.
horus_manager::commands::pkg::detect_plugin_metadata (cognitive 56) horus_manager/src/commands/pkg.rs:25— horus_manager::commands::pkg::detect_plugin_metadata has cognitive complexity 56 (threshold 15). Drivers by points: if/else 14 (43 pts), match/switch 4 (10 pts), loops 1 (3 pts) (nesting depth added 37). 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.
horus_manager::system_deps::check_dependencies (cognitive 56) horus_manager/src/system_deps.rs:138— horus_manager::system_deps::check_dependencies has cognitive complexity 56 (threshold 15). Drivers by points: if/else 11 (41 pts), loops 5 (13 pts), boolean chains 2 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_manager::commands::doc_extract_rust::parse_struct_fields_from_tokens (cognitive 55) horus_manager/src/commands/doc_extract_rust.rs:470— horus_manager::commands::doc_extract_rust::parse_struct_fields_from_tokens has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (46 pts), loops 2 (7 pts), boolean chains 2 (nesting depth added 38). 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.
horus_manager::commands::doc_extract::format_brief (cognitive 54) horus_manager/src/commands/doc_extract.rs:485— horus_manager::commands::doc_extract::format_brief has cognitive complexity 54 (threshold 15). Drivers by points: loops 9 (26 pts), if/else 12 (23 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 30). 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.
horus_manager::registry::helpers::add_features_to_cargo_toml (cognitive 54) horus_manager/src/registry/helpers.rs:73— horus_manager::registry::helpers::add_features_to_cargo_toml has cognitive complexity 54 (threshold 15). Drivers by points: loops 10 (30 pts), if/else 8 (20 pts), match/switch 2 (4 pts) (nesting depth added 34). 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.
horus_manager::commands::run::execute_run (cognitive 52) horus_manager/src/commands/run/mod.rs:165— horus_manager::commands::run::execute_run has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (46 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 27). 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.
horus_manager::commands::pkg::run_remove (cognitive 51) horus_manager/src/commands/pkg.rs:1426— horus_manager::commands::pkg::run_remove has cognitive complexity 51 (threshold 15). Drivers by points: if/else 27 (46 pts), loops 1 (3 pts), boolean chains 2 (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.
horus_manager::registry::helpers::precompile_package (cognitive 51) horus_manager/src/registry/helpers.rs:1202— horus_manager::registry::helpers::precompile_package has cognitive complexity 51 (threshold 15). Drivers by points: if/else 14 (35 pts), loops 3 (10 pts), boolean chains 6 (nesting depth added 28). 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.
horus_manager::commands::migrate::run_migrate (cognitive 50) horus_manager/src/commands/migrate.rs:19— horus_manager::commands::migrate::run_migrate has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (38 pts), loops 4 (10 pts), boolean chains 2 (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.
horus_manager::run_command (cyclomatic 215) horus_manager/src/main.rs:2469— horus_manager::run_command has cyclomatic complexity 215 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
horus_manager::commands::check::check_manifest_file (cyclomatic 100) horus_manager/src/commands/check.rs:1054— horus_manager::commands::check::check_manifest_file has cyclomatic complexity 100 (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.
horus_manager::commands::check::check_workspace (cyclomatic 82) horus_manager/src/commands/check.rs:321— horus_manager::commands::check::check_workspace has cyclomatic complexity 82 (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.
horus_manager::commands::launch::run_launch (cyclomatic 59) horus_manager/src/commands/launch.rs:370— horus_manager::commands::launch::run_launch has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
horus_manager::commands::topic::decode_pod_fields (cyclomatic 45) horus_manager/src/commands/topic.rs:328— horus_manager::commands::topic::decode_pod_fields has cyclomatic complexity 45 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
horus_manager::discovery::nodes::discover_nodes_uncached (cyclomatic 45) horus_manager/src/discovery/nodes.rs:3— horus_manager::discovery::nodes::discover_nodes_uncached has cyclomatic complexity 45 (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.
horus_manager::commands::node::list_nodes (cyclomatic 37) horus_manager/src/commands/node.rs:64— horus_manager::commands::node::list_nodes has cyclomatic complexity 37 (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.
horus_manager::commands::pkg::run_add_dep (cyclomatic 35) horus_manager/src/commands/pkg.rs:1042— horus_manager::commands::pkg::run_add_dep has cyclomatic complexity 35 (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.
horus_manager::commands::action::discover_actions (cyclomatic 34) horus_manager/src/commands/action.rs:37— horus_manager::commands::action::discover_actions has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
horus_manager::error_wrapper::cargo_error_hint (cyclomatic 33) horus_manager/src/error_wrapper.rs:236— horus_manager::error_wrapper::cargo_error_hint has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: horus_manager::error_wrapper::error_code_info (cyclomatic 46) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
horus_manager::commands::clean::run_clean (cyclomatic 32) horus_manager/src/commands/clean.rs:13— horus_manager::commands::clean::run_clean 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.
horus_manager::commands::run::run_rust::execute_build_only (cyclomatic 31) horus_manager/src/commands/run/run_rust.rs:190— horus_manager::commands::run::run_rust::execute_build_only 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.
horus_manager::commands::doc_extract::format_brief (cyclomatic 30) horus_manager/src/commands/doc_extract.rs:485— horus_manager::commands::doc_extract::format_brief has cyclomatic complexity 30 (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.
horus_manager::commands::record::run_inject (cyclomatic 30) horus_manager/src/commands/record.rs:719— horus_manager::commands::record::run_inject 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.
horus_manager::commands::migrate::run_migrate (cyclomatic 29) horus_manager/src/commands/migrate.rs:19— horus_manager::commands::migrate::run_migrate 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.
horus_manager::commands::pkg::run_list (cyclomatic 29) horus_manager/src/commands/pkg.rs:1724— horus_manager::commands::pkg::run_list 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.
horus_manager::registry::helpers::prompt_package_metadata (cyclomatic 29) horus_manager/src/registry/helpers.rs:1349— horus_manager::registry::helpers::prompt_package_metadata 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.
horus_manager::commands::plugin::run_info_unified (cyclomatic 27) horus_manager/src/commands/plugin.rs:260— horus_manager::commands::plugin::run_info_unified 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.
horus_manager::commands::doc_extract_rust::extract_rust_file (cyclomatic 26) horus_manager/src/commands/doc_extract_rust.rs:21— horus_manager::commands::doc_extract_rust::extract_rust_file has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
horus_manager::commands::pkg::run_remove (cyclomatic 26) horus_manager/src/commands/pkg.rs:1426— horus_manager::commands::pkg::run_remove 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.
horus_manager::commands::run::execute_run (cyclomatic 26) horus_manager/src/commands/run/mod.rs:165— horus_manager::commands::run::execute_run 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.
horus_manager::commands::run::deps::split_dependencies_with_context (cyclomatic 25) horus_manager/src/commands/run/deps.rs:424— horus_manager::commands::run::deps::split_dependencies_with_context 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.
horus_manager::commands::msg::parse_messages_from_source (cyclomatic 24) horus_manager/src/commands/msg.rs:751— horus_manager::commands::msg::parse_messages_from_source 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.
horus_manager::registry::helpers::add_features_to_cargo_toml (cyclomatic 24) horus_manager/src/registry/helpers.rs:73— horus_manager::registry::helpers::add_features_to_cargo_toml has cyclomatic complexity 24 (threshold 15). 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.
horus_manager::commands::run::execute_multiple_files (cyclomatic 23) horus_manager/src/commands/run/mod.rs:536— horus_manager::commands::run::execute_multiple_files 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.
Hotspot: horus_manager/src/main.rs horus_manager/src/main.rs:2469— horus_manager/src/main.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 215 in horus_manager::run_command at line 2469. 9 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/main.rs`: 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: horus_core/src/scheduling/scheduler/mod.rs horus_core/src/scheduling/scheduler/mod.rs:3212— horus_core/src/scheduling/scheduler/mod.rs changed 53 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in Scheduler::run_with_filter at line 3212. 30 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/scheduler/mod.rs`: 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: horus_core/src/scheduling/rt_executor.rs horus_core/src/scheduling/rt_executor.rs:1417— horus_core/src/scheduling/rt_executor.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 61 in RtExecutor::tick_node at line 1417. 20 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/rt_executor.rs`: 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: horus_manager/src/commands/check.rs horus_manager/src/commands/check.rs:1054— horus_manager/src/commands/check.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 100 in horus_manager::commands::check::check_manifest_file at line 1054. 6 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/check.rs`: 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: horus_core/src/communication/topic/mod.rs horus_core/src/communication/topic/mod.rs:1179— horus_core/src/communication/topic/mod.rs changed 63 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RingTopic::negotiate_shm_header at line 1179. 28 of those changes were fix/bug commits, and the other 35 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/communication/topic/mod.rs`: 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: horus_core/src/communication/topic/header.rs horus_core/src/communication/topic/header.rs:1828— horus_core/src/communication/topic/header.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in horus_core::communication::topic::header::read_slot_from_region at line 1828. 13 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/communication/topic/header.rs`: 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: horus_core/src/communication/topic/dispatch.rs horus_core/src/communication/topic/dispatch.rs:1742— horus_core/src/communication/topic/dispatch.rs changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in horus_core::communication::topic::dispatch::send_shm_mp_serde at line 1742. 20 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/communication/topic/dispatch.rs`: 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: horus_net/src/replicator.rs horus_net/src/replicator.rs:367— horus_net/src/replicator.rs changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Replicator::process_packet at line 367. 14 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/replicator.rs`: 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: horus_core/src/scheduling/event_executor.rs horus_core/src/scheduling/event_executor.rs:284— horus_core/src/scheduling/event_executor.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in EventExecutor::watcher_thread at line 284. 11 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/event_executor.rs`: 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: horus_manager/src/registry/install.rs horus_manager/src/registry/install.rs:399— horus_manager/src/registry/install.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in RegistryClient::install_from_registry at line 399. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/registry/install.rs`: 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: horus_core/src/scheduling/compute_executor.rs horus_core/src/scheduling/compute_executor.rs:567— horus_core/src/scheduling/compute_executor.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in ComputeExecutor::compute_thread_main at line 567. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/compute_executor.rs`: 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: benchmarks/src/bin/cross_process_benchmark.rs benchmarks/src/bin/cross_process_benchmark.rs:2265— benchmarks/src/bin/cross_process_benchmark.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 80 in horus_benchmarks::bin::cross_process_benchmark::main at line 2265. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- benchmarks/src/bin/cross_process_benchmark.rs`: 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: horus_core/src/scheduling/async_executor.rs horus_core/src/scheduling/async_executor.rs:114— horus_core/src/scheduling/async_executor.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in AsyncExecutor::async_thread_main at line 114. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/async_executor.rs`: 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: horus_manager/src/commands/run/run_rust.rs horus_manager/src/commands/run/run_rust.rs:190— horus_manager/src/commands/run/run_rust.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in horus_manager::commands::run::run_rust::execute_build_only at line 190. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/run/run_rust.rs`: 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: horus_manager/src/commands/pkg.rs horus_manager/src/commands/pkg.rs:1042— horus_manager/src/commands/pkg.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in horus_manager::commands::pkg::run_add_dep at line 1042. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/pkg.rs`: 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: horus_manager/src/commands/new.rs horus_manager/src/commands/new.rs:35— horus_manager/src/commands/new.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in horus_manager::commands::new::create_new_project_with_options at line 35. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/new.rs`: 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: benchmarks/src/output.rs benchmarks/src/output.rs:1007— benchmarks/src/output.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in BaselineHistory::compare_one at line 1007. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- benchmarks/src/output.rs`: 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: horus_core/src/scheduling/node_builder.rs horus_core/src/scheduling/node_builder.rs:559— horus_core/src/scheduling/node_builder.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in NodeRegistration::validate at line 559. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/node_builder.rs`: 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: horus_manager/src/registry/publish.rs horus_manager/src/registry/publish.rs:258— horus_manager/src/registry/publish.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in RegistryClient::publish at line 258. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/registry/publish.rs`: 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: horus_manager/src/commands/node.rs horus_manager/src/commands/node.rs:64— horus_manager/src/commands/node.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in horus_manager::commands::node::list_nodes at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/node.rs`: 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: horus_manager/src/commands/doctor.rs horus_manager/src/commands/doctor.rs:1226— horus_manager/src/commands/doctor.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in horus_manager::commands::doctor::check_drivers at line 1226. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/doctor.rs`: 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: horus_manager/src/commands/run/run_cpp.rs horus_manager/src/commands/run/run_cpp.rs:140— horus_manager/src/commands/run/run_cpp.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in horus_manager::commands::run::run_cpp::build_cpp 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/run/run_cpp.rs`: 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: horus_core/src/scheduling/primitives.rs horus_core/src/scheduling/primitives.rs:320— horus_core/src/scheduling/primitives.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in horus_core::scheduling::primitives::apply_degradation_action at line 320. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/primitives.rs`: 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: horus_py/src/topic.rs horus_py/src/topic.rs:1267— horus_py/src/topic.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PyTopic::recv at line 1267. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_py/src/topic.rs`: 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: horus_net/src/presence.rs horus_net/src/presence.rs:147— horus_net/src/presence.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PresenceReceiver::handle_broadcast at line 147. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/presence.rs`: 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.
FunctionTooLong: horus_manager::run_command horus_manager/src/main.rs:2469— FunctionTooLong — horus_manager::run_command runs 865 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 765 over it, 8.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::launch::run_launch horus_manager/src/commands/launch.rs:370— FunctionTooLong — horus_manager::commands::launch::run_launch runs 348 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 248 over it, 3.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::pkg::run_add_dep horus_manager/src/commands/pkg.rs:1042— FunctionTooLong — horus_manager::commands::pkg::run_add_dep runs 242 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::registry::helpers::prompt_package_metadata horus_manager/src/registry/helpers.rs:1349— FunctionTooLong — horus_manager::registry::helpers::prompt_package_metadata runs 230 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::discovery::nodes::discover_nodes_uncached horus_manager/src/discovery/nodes.rs:3— FunctionTooLong — horus_manager::discovery::nodes::discover_nodes_uncached runs 197 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× 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: horus_manager::commands::node::list_nodes horus_manager/src/commands/node.rs:64— FunctionTooLong — horus_manager::commands::node::list_nodes runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: horus_manager::commands::run::run_rust::execute_build_only horus_manager/src/commands/run/run_rust.rs:190— FunctionTooLong — horus_manager::commands::run::run_rust::execute_build_only runs 188 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: horus_manager::cmake_gen::generate horus_manager/src/cmake_gen.rs:223— FunctionTooLong — horus_manager::cmake_gen::generate runs 186 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::error_wrapper::cargo_error_hint horus_manager/src/error_wrapper.rs:236— FunctionTooLong — horus_manager::error_wrapper::cargo_error_hint runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: horus_manager::msgspec::emit_python::module horus_manager/src/msgspec/emit_python.rs:339— FunctionTooLong — horus_manager::msgspec::emit_python::module runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::tf::hand_eye_calibration REDACTED:2005— FunctionTooLong — horus_manager::commands::tf::hand_eye_calibration runs 174 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::msg::generate_messages horus_manager/src/commands/msg.rs:3043— FunctionTooLong — horus_manager::commands::msg::generate_messages runs 173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: horus_manager::commands::run::execute_multiple_files horus_manager/src/commands/run/mod.rs:536— FunctionTooLong — horus_manager::commands::run::execute_multiple_files runs 169 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::topic::decode_pod_fields horus_manager/src/commands/topic.rs:328— FunctionTooLong — horus_manager::commands::topic::decode_pod_fields runs 169 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::record::run_inject horus_manager/src/commands/record.rs:719— FunctionTooLong — horus_manager::commands::record::run_inject runs 165 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::pkg::run_remove horus_manager/src/commands/pkg.rs:1426— FunctionTooLong — horus_manager::commands::pkg::run_remove runs 163 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::run::install::probe_system_distributions horus_manager/src/commands/run/install.rs:1517— FunctionTooLong — horus_manager::commands::run::install::probe_system_distributions runs 155 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::tf::calibrate_from_points REDACTED:1764— FunctionTooLong — horus_manager::commands::tf::calibrate_from_points runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: horus_manager::commands::deploy::run_deploy_multi horus_manager/src/commands/deploy.rs:355— FunctionTooLong — horus_manager::commands::deploy::run_deploy_multi runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::registry::helpers::detect_package_info horus_manager/src/registry/helpers.rs:796— FunctionTooLong — horus_manager::registry::helpers::detect_package_info runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::run::install::install_pip_packages horus_manager/src/commands/run/install.rs:235— FunctionTooLong — horus_manager::commands::run::install::install_pip_packages runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: horus_manager::commands::run::run_rust::execute_with_scheduler horus_manager/src/commands/run/run_rust.rs:896— FunctionTooLong — horus_manager::commands::run::run_rust::execute_with_scheduler runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
FunctionTooLong: horus_manager::commands::tf::list_frames REDACTED:290— FunctionTooLong — horus_manager::commands::tf::list_frames runs 140 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::clean::clean_shared_memory horus_manager/src/commands/clean.rs:250— FunctionTooLong — horus_manager::commands::clean::clean_shared_memory runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: horus_manager::commands::run::run_cpp::build_cpp horus_manager/src/commands/run/run_cpp.rs:140— FunctionTooLong — horus_manager::commands::run::run_cpp::build_cpp runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: src/messages.rs horus_py/src/messages.rs— FileTooLong — 5455 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 4955 over it, 10.91× 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: scheduler/mod.rs horus_core/src/scheduling/scheduler/mod.rs— FileTooLong — 2974 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 94% of them inside a single declaration: Scheduler (3 blocks, 350-6550). The bar is 500 significant lines; this is 2474 over it, 5.95× 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: src/main.rs horus_manager/src/main.rs— FileTooLong — 2028 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1528 over it, 4.06× 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: topic/mod.rs horus_core/src/communication/topic/mod.rs— FileTooLong — 1808 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: RingTopic (5 blocks, 789-3942). The bar is 500 significant lines; this is 1308 over it, 3.62× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: commands/pkg.rs horus_manager/src/commands/pkg.rs— FileTooLong — 1716 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 45 free functions. The bar is 500 significant lines; this is 1216 over it, 3.43× 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: registry/install.rs horus_manager/src/registry/install.rs— FileTooLong — 1658 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: RegistryClient (3 blocks, 148-2588). The bar is 500 significant lines; this is 1158 over it, 3.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1571 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1071 over it, 3.14× 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: src/topic.rs horus_py/src/topic.rs— FileTooLong — 1358 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: PyTopic (2 blocks, 628-2123). The bar is 500 significant lines; this is 858 over it, 2.72× 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: registry/helpers.rs horus_manager/src/registry/helpers.rs— FileTooLong — 1333 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 833 over it, 2.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/c_api.rs horus_cpp/src/c_api.rs— FileTooLong — 1259 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 124 free functions. The bar is 500 significant lines; this is 759 over it, 2.52× 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: commands/doctor.rs horus_manager/src/commands/doctor.rs— FileTooLong — 1179 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 39 free functions. The bar is 500 significant lines; this is 679 over it, 2.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: memory/tensor_pool.rs horus_core/src/memory/tensor_pool.rs— FileTooLong — 1171 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: TensorPool (3 blocks, 357-2726). The bar is 500 significant lines; this is 671 over it, 2.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: commands/check.rs horus_manager/src/commands/check.rs— FileTooLong — 1168 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 668 over it, 2.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: run/install.rs horus_manager/src/commands/run/install.rs— FileTooLong — 1168 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 41 free functions. The bar is 500 significant lines; this is 668 over it, 2.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scheduling/record_replay.rs horus_core/src/scheduling/record_replay.rs— FileTooLong — 1129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 629 over it, 2.26× 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: commands/deploy.rs horus_manager/src/commands/deploy.rs— FileTooLong — 1043 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 543 over it, 2.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: topic/dispatch.rs horus_core/src/communication/topic/dispatch.rs— FileTooLong — 1034 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 33 free functions. The bar is 500 significant lines; this is 534 over it, 2.07× 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: horus/__init__.py horus_py/horus/__init__.py— FileTooLong — 1020 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 520 over it, 2.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: scheduling/rt_executor.rs horus_core/src/scheduling/rt_executor.rs— FileTooLong — 962 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 462 over it, 1.92× 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: topic/header.rs horus_core/src/communication/topic/header.rs— FileTooLong — 880 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 380 over it, 1.76× 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: src/manifest.rs horus_manager/src/manifest.rs— FileTooLong — 847 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 347 over it, 1.69× 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: run/run_rust.rs horus_manager/src/commands/run/run_rust.rs— FileTooLong — 844 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 344 over it, 1.69× 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: commands/doc_extract.rs horus_manager/src/commands/doc_extract.rs— FileTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 339 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/scheduler.rs horus_py/src/scheduler.rs— FileTooLong — 833 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 333 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: registry/publish.rs horus_manager/src/registry/publish.rs— FileTooLong — 829 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 86% of them inside a single declaration: RegistryClient (201-1251). The bar is 500 significant lines; this is 329 over it, 1.66× 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.
+ 19 more in this group — see findings.md.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded horus_types/src/diagnostics.rs:14— `std::time::SystemTime::now().duration_since(std::time::UNIX_EPOCH)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `timestamp_now` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_py/src/python_api_docs.rs:34— `src.find("\nclass Node:")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `node_class_body` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_py/src/python_api_docs.rs:104— `class_body.find("\n def __init__(")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `init_annotation` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_py/src/python_api_docs.rs:107— `class_body[at..].find("\"\"\"")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `init_annotation` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_py/src/topic.rs:724— `std::ffi::CString::new("topic endpoint host ignored")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_net/src/fragment.rs:281— `self.pending.remove(&key)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `feed` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:55— `writeln!(cargo,"# Generated by horus from horus.toml — do not edit manually.\n\
# Edits are lost on the next build; add a [rust] section to horus.toml instead.")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:56— `writeln!(cargo,"[package]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:57— `writeln!(cargo,"name = \"{}\"",sanitize_cargo_name(project_name))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:58— `writeln!(cargo,"version = \"{}\"",version)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:59— `writeln!(cargo,"edition = \"{}\"",rust_edition(manifest))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:60— `writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:64— `writeln!(cargo,"[workspace]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:65— `writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:132— `writeln!(cargo,"[dependencies]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:154— `writeln!(cargo)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:155— `writeln!(cargo,"[dev-dependencies]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `generate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:352— `writeln!(wanted,"!{name}")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `ignore_generated_dir` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:852— `writeln!(text,"{GENERATED_CARGO_CONFIG_HEADER}\n\
# Edits are lost on the next build; change [rust].rustflags instead.")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:853— `writeln!(text,"[build]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:856— `writeln!(text,"rustflags = {}",toml::Value::from(flags.to_vec()))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_generated_cargo_config` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:964— `writeln!(cargo,"\n# Driver dependencies (from [hardware], or legacy [drivers])")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:968— `writeln!(cargo,"{} = \"{}\"",crate_name,ver)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:980— `writeln!(cargo,"{} = {{ version = \"{}\", features = [{}] }}",crate_name,ver,features_str)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_driver_deps` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded horus_manager/src/cargo_gen.rs:1013— `writeln!(cargo,"[[{kind}]]")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `write_target_entry` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Repeated repair: horus_core/src/memory/tensor_pool.rs horus_core/src/memory/tensor_pool.rs:1214— horus_core/src/memory/tensor_pool.rs changed 32 times in last 90 days and 19 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 TensorPool::alloc at line 1214), 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(pool): a truncated pool file must error, not SIGBUS the robot (#143)”; “fix(pool): reclaim a tensor pool whose creator died before writing its header”; “fix(shm): stop unmapping a region that sibling Topic clones still point into”; “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/memory/tensor_pool.rs`: 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: horus_sys/src/shm/mod.rs horus_sys/src/shm/mod.rs:1693— horus_sys/src/shm/mod.rs changed 26 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 13 (its worst body is horus_sys::shm::cleanup_stale_namespaces_in at line 1693), 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: fold duplication batches 5-7 (#200, #201, #202) into one CI cycle (#204)”; “fix(bench,sys): read NaN back, and stop asserting Unix on Windows”; “fix(shm): reclaim abandoned regions inside a namespace that is still in use”; “fix(shm): stop unmapping a region that sibling Topic clones still point into”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_sys/src/shm/mod.rs`: 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: horus_net/src/estop.rs horus_net/src/estop.rs:197— horus_net/src/estop.rs changed 13 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 8 (its worst body is horus_net::estop::handle_remote_estop_at at line 197), 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(net): an e-stop that reached nobody was indistinguishable from one that worked”; “fix(net): a diagnostic on a broken stderr killed the replicator thread”; “fix(security): require authentication for remote estop (#71)”; “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/estop.rs`: 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: horus_core/src/actions/server.rs horus_core/src/actions/server.rs:1283— horus_core/src/actions/server.rs changed 11 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 ActionServerNode::tick at line 1283), 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(ci): repair every failing workflow (#84)”; “fix(core,sys,cpp): a print on a broken stream killed the thread printing it”; “fix(services,actions): a panic in user code no longer kills the server”; “fix: goal_timeout bounded nothing, cancel_goal cancelled nothing, and replay wrote to a filename deleted in March”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/actions/server.rs`: 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: horus_core/src/error.rs horus_core/src/error.rs:1236— horus_core/src/error.rs changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is HorusError::severity at line 1236), 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(ci): repair every failing workflow (#84)”; “fix(ci): repair every failing workflow”; “fix(rt,build,sim): stop hiding real-time degradation, cargo warnings, and sim-mode intent”; “fix(errors,manifest): stop printing errors twice; report unknown horus.toml keys”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/error.rs`: 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: REDACTED REDACTED:181— REDACTED changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is horus_manager::commands::github_auth::wait_for_oauth_callback at line 181), 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(registry): stop shipping a registry URL that answers 503 (#175)”; “fix(manager): the CLI printed instructions naming commands it does not have”; “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”; “security: fix a regression in the e-stop framing fix, and close the OAuth state bypass”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- REDACTED`: 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: horus_net/src/peer.rs horus_net/src/peer.rs:224— horus_net/src/peer.rs changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is PeerTable::find_duplicate_publishers at line 224), 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: “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(ci): repair every failing workflow (#84)”; “fix(net): a diagnostic on a broken stderr killed the replicator thread”; “fix: the loss throttle keyed on our own peer id, and log drains compared a node tick to a buffer index”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/peer.rs`: 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: horus_sys/src/shm/linux.rs horus_sys/src/shm/linux.rs:95— horus_sys/src/shm/linux.rs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ShmRegion::new 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(topic): a lost FanoutShm attach no longer strands a subscriber forever”; “fix(shm): stop unmapping a region that sibling Topic clones still point into”; “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(shm): a publisher restart no longer deafens its subscribers”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_sys/src/shm/linux.rs`: 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: horus_core/src/scheduling/scheduler/recording.rs horus_core/src/scheduling/scheduler/recording.rs:117— horus_core/src/scheduling/scheduler/recording.rs changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is Scheduler::replay_from at line 117), 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(rt): throttle the per-tick diagnostics that were destroying the log”; “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”; “fix(ci): repair every failing job on main”; “fix(replay): derive synthetic replay tick period from recorded wall-clock span”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/scheduler/recording.rs`: 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: horus_core/src/scheduling/record_replay.rs horus_core/src/scheduling/record_replay.rs:1214— horus_core/src/scheduling/record_replay.rs 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 11 (its worst body is horus_core::scheduling::record_replay::diff_recordings at line 1214), 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 clippy warnings that fail the strict gate on main”; “fix CI and cross-platform tests”; “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”; “fix(ci): clear all remaining rustdoc and clippy errors”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/scheduling/record_replay.rs`: 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: horus_sys/src/shm/fallback.rs horus_sys/src/shm/fallback.rs:74— horus_sys/src/shm/fallback.rs 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 4 (its worst body is ShmRegion::new at line 74), 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: three more drifted duplications from the audit (#195)”; “fix(shm): stop unmapping a region that sibling Topic clones still point into”; “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(ci): repair every failing workflow (#84)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_sys/src/shm/fallback.rs`: 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: horus_sys/src/shm/macos.rs horus_sys/src/shm/macos.rs:162— horus_sys/src/shm/macos.rs 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 15 (its worst body is ShmRegion::new at line 162), 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(shm): stop unmapping a region that sibling Topic clones still point into”; “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(ci): repair every failing workflow (#84)”; “fix: observe freshness through native shared memory”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_sys/src/shm/macos.rs`: 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: benchmarks/src/bin/iceoryx2_comparison.rs benchmarks/src/bin/iceoryx2_comparison.rs:554— benchmarks/src/bin/iceoryx2_comparison.rs changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is horus_benchmarks::bin::iceoryx2_comparison::bench_cross_process at line 554), 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: “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(ci): repair every failing workflow (#84)”; “fix(ci): repair every failing workflow”; “Fix integration/bench/loom tests for SHM-only backends”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- benchmarks/src/bin/iceoryx2_comparison.rs`: 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: horus_core/src/core/log_buffer.rs horus_core/src/core/log_buffer.rs:687— horus_core/src/core/log_buffer.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is horus_core::core::log_buffer::log_drain_loop at line 687), 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: “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(core,sys,cpp): a print on a broken stream killed the thread printing it”; “fix: the loss throttle keyed on our own peer id, and log drains compared a node tick to a buffer index”; “security: make the SHM tree owner-only and fix the JSON gateway file handling”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/core/log_buffer.rs`: 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: horus_core/src/core/presence.rs horus_core/src/core/presence.rs:521— horus_core/src/core/presence.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is NodePresence::read_all at line 521), 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: three more drifted duplications from the audit (#195)”; “fix(core): reading local presence deleted the fleet's remote host records”; “fix(core,sys,cpp): a print on a broken stream killed the thread printing it”; “fix(scheduler): a node name can no longer forge lines in the runtime's output”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/core/presence.rs`: 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: horus_manager/src/plugins/executor.rs horus_manager/src/plugins/executor.rs:135— horus_manager/src/plugins/executor.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is PluginExecutor::discover_plugin_binary at line 135), 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(manager): the CLI printed instructions naming commands it does not have”; “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”; “fix(ci): repair every failing job on main”; “fix(security): gate plugin execution on out-of-repo trust (SEC2 + SEC3)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/plugins/executor.rs`: 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: horus_core/src/drivers/mod.rs horus_core/src/drivers/mod.rs:152— horus_core/src/drivers/mod.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is horus_core::drivers::load_from at line 152), 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(core,py): deterministic mode was not deterministic, and astype always panicked”; “fix(rt,build,sim): stop hiding real-time degradation, cargo warnings, and sim-mode intent”; “fix(ci): clear all remaining rustdoc and clippy errors”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/drivers/mod.rs`: 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: horus_net/src/shm_writer.rs horus_net/src/shm_writer.rs:77— horus_net/src/shm_writer.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ShmRingWriter::open_path at line 77), 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(horus_net): the SHM import writer ignored the region's layout kind (#190)”; “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(ci): clear all remaining rustdoc and clippy errors”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/shm_writer.rs`: 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: horus_py/src/messages.rs horus_py/src/messages.rs:6564— horus_py/src/messages.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is PyPointField::new at line 6564), 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: “security: "secure" directory creation never repaired an existing mode, and the Rust action server had the C++ duplicate-goal bug too”; “fix(ci): repair every failing job on main”; “fix(security): patch RustSec vulns + migrate pyo3 0.27->0.29 (closes Dependabot #25-#28)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_py/src/messages.rs`: 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: horus_manager/src/commands/deploy.rs horus_manager/src/commands/deploy.rs:355— horus_manager/src/commands/deploy.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is horus_manager::commands::deploy::run_deploy_multi at line 355), 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: “perf+fix: round 3 measurement honesty, security audit remediation, benchmark cleanup”; “fix(deploy): ship the binary, build the right manifest, expand the remote tilde”; “fix(ci): unbreak all eight build workflows after the rust-major bump (#76)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_manager/src/commands/deploy.rs`: 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: horus_core/src/memory/shm_region.rs horus_core/src/memory/shm_region.rs:146— horus_core/src/memory/shm_region.rs 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 2 (its worst body is ShmRegion::grow at line 146), 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(topic): a lost FanoutShm attach no longer strands a subscriber forever”; “fix(shm): stop unmapping a region that sibling Topic clones still point into”; “fix(ci): repair every failing workflow (#84)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/memory/shm_region.rs`: 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: benchmarks/src/stats.rs benchmarks/src/stats.rs:479— benchmarks/src/stats.rs 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 8 (its worst body is NormalityAnalysis::analyze at line 479), 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(bench): run_variance was the null, and Windows has no clock_gettime”; “fix(bench,sys): read NaN back, and stop asserting Unix on Windows”; “fix(ci): repair every failing workflow (#84)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- benchmarks/src/stats.rs`: 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: horus_core/src/memory/rt_allocator.rs horus_core/src/memory/rt_allocator.rs:395— horus_core/src/memory/rt_allocator.rs 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 2 (its worst body is RtAwareAllocator::alloc at line 395), 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(ci): repair every failing workflow (#84)”; “fix(core,sys,cpp): a print on a broken stream killed the thread printing it”; “fix(rt): stop per-tick alloc+leak in .no_alloc() instrumentation; prove hot path”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_core/src/memory/rt_allocator.rs`: 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: horus_net/src/heartbeat.rs horus_net/src/heartbeat.rs:223— horus_net/src/heartbeat.rs 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 7 (its worst body is SafetyHeartbeat::tick at line 223), 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(ci): repair every failing workflow (#84)”; “fix(net): a diagnostic on a broken stderr killed the replicator thread”; “fix(net): a peer was declared link-lost before it could answer”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_net/src/heartbeat.rs`: 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: horus_sys/src/process/mod.rs horus_sys/src/process/mod.rs:130— horus_sys/src/process/mod.rs 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 7 (its worst body is ProcessHandle::signal at line 130), 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(ci): repair every failing workflow (#84)”; “fix(ci): repair every failing workflow”; “fix CI and cross-platform tests”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-30 09:28:58 +00:00' --until='2026-09-28 09:28:58 +00:00' --full-history --no-merges -- horus_sys/src/process/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (9 lines × 2) horus_core/src/communication/topic/dispatch.rs:1671— horus_core/src/communication/topic/dispatch.rs:1671-1679 | horus_core/src/communication/topic/dispatch.rs:1690-1698 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:1671` it begins part-way through the construct above it, so those 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) horus_manager/src/commands/deploy.rs:1747— horus_manager/src/commands/deploy.rs:1747-1755 | horus_manager/src/commands/deploy.rs:1763-1771 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_manager/src/commands/deploy.rs:1761` calls `find_binary_name` and `horus_manager/src/commands/deploy.rs:1744` 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 × 2) horus_manager/src/commands/deps.rs:144— horus_manager/src/commands/deps.rs:144-152 | horus_manager/src/commands/deps.rs:318-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 `horus_manager/src/commands/deps.rs:144` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/doc_extract.rs:507— horus_manager/src/commands/doc_extract.rs:507-515 | horus_manager/src/commands/doc_extract_html.rs:185-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) horus_manager/src/commands/doc_extract_diff.rs:159— horus_manager/src/commands/doc_extract_diff.rs:159-167 | horus_manager/src/commands/doc_extract_diff.rs:172-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_diff.rs:159` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/doc_extract_python.rs:133— horus_manager/src/commands/doc_extract_python.rs:133-141 | horus_manager/src/commands/doc_extract_python.rs:201-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_python.rs:133` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/doctor.rs:1827— horus_manager/src/commands/doctor.rs:1827-1835 | horus_manager/src/commands/run/run_rust.rs:1242-1250 — 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 `horus_manager/src/commands/doctor.rs:1827` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/pkg.rs:36— horus_manager/src/commands/pkg.rs:36-44 | horus_manager/src/commands/pkg.rs:60-68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs: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.
Duplicated block (9 lines × 2) horus_manager/src/commands/run/install.rs:1780— horus_manager/src/commands/run/install.rs:1780-1788 | horus_manager/src/registry/install.rs:2271-2279 — 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 `horus_manager/src/commands/run/install.rs:1780` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/main.rs:2445— horus_manager/src/main.rs:2445-2453 | horus_manager/src/main.rs:2457-2465 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/main.rs:2445` it begins part-way through the construct above it, so those 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, `horus_manager/src/main.rs:2441` calls `extract_exit_code` and `horus_manager/src/main.rs:2453` 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 × 2) horus_manager/src/msgspec/parse.rs:512— horus_manager/src/msgspec/parse.rs:512-520 | horus_manager/src/msgspec/parse.rs:566-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/msgspec/parse.rs:512` it does not close everything it opens, so those exact lines 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) horus_manager/src/registry/helpers.rs:76— horus_manager/src/registry/helpers.rs:76-84 | horus_manager/src/registry/helpers.rs:451-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_manager/src/registry/helpers.rs:462` calls `get`, `is_none`, `table` and `horus_manager/src/registry/helpers.rs:87` 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 × 2) horus_manager/src/system_deps.rs:492— horus_manager/src/system_deps.rs:492-500 | horus_manager/src/system_deps.rs:504-512 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/system_deps.rs:492` it begins part-way through the construct above it, so those exact lines 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) horus_py/src/messages.rs:1466— horus_py/src/messages.rs:1466-1474 | horus_py/src/messages.rs:2488-2496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/messages.rs:1466` 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) horus_manager/src/commands/pkg.rs:426— horus_manager/src/commands/pkg.rs:426-434 | horus_manager/src/registry/helpers.rs:665-673 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) horus_manager/src/commands/action.rs:539— horus_manager/src/commands/action.rs:539-548 | horus_manager/src/commands/action.rs:549-557 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/action.rs:539` 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 (9 lines × 2) horus_manager/src/main.rs:3202— horus_manager/src/main.rs:3202-3211 | horus_manager/src/main.rs:3233-3241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/main.rs:3202` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/upgrade.rs:996— horus_manager/src/commands/upgrade.rs:996-1004 | horus_manager/src/commands/upgrade.rs:1032-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 `horus_manager/src/commands/upgrade.rs:996` it does not close everything it opens, so those exact lines 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) horus_manager/src/registry/install.rs:1634— horus_manager/src/registry/install.rs:1634-1642 | horus_manager/src/registry/install.rs:1914-1922 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:1634` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/registry/helpers.rs:1571— horus_manager/src/registry/helpers.rs:1571-1579 | horus_manager/src/registry/helpers.rs:1638-1646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:1571` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/registry/install.rs:892— horus_manager/src/registry/install.rs:892-900 | horus_manager/src/registry/install.rs:1981-1989 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:892` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/check.rs:908— horus_manager/src/commands/check.rs:908-916 | horus_manager/src/commands/check.rs:935-943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/check.rs:908` 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) horus_core/src/testing/shm_fault.rs:251— horus_core/src/testing/shm_fault.rs:251-259 | horus_core/src/testing/shm_fault.rs:280-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 `horus_core/src/testing/shm_fault.rs:251` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) horus_core/src/scheduling/scheduler/mod.rs:5084— horus_core/src/scheduling/scheduler/mod.rs:5084-5091 | horus_core/src/scheduling/scheduler/mod.rs:5279-5286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/scheduler/mod.rs:5084` it does not close everything it opens, so those exact lines 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) horus_cpp/src/c_api.rs:1479— horus_cpp/src/c_api.rs:1479-1486 | horus_cpp/src/c_api.rs:2056-2063 — both copies are in the same file, so extract the 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) horus_manager/src/commands/msg.rs:397— horus_manager/src/commands/msg.rs:397-404 | horus_manager/src/commands/msg.rs:415-422 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/msg.rs:397` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/pkg.rs:1265— horus_manager/src/commands/pkg.rs:1265-1272 | horus_manager/src/commands/pkg.rs:1375-1382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1265` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) REDACTED:1129— REDACTED:1129-1136 | REDACTED:1230-1237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1129` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/pkg.rs:1991— horus_manager/src/commands/pkg.rs:1991-1998 | horus_manager/src/commands/pkg.rs:2008-2015 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1991` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/deploy.rs:96— horus_manager/src/commands/deploy.rs:96-103 | horus_manager/src/toolchain.rs:27-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. 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) horus_core/src/scheduling/rt_executor.rs:37— horus_core/src/scheduling/rt_executor.rs:37-44 | horus_core/src/scheduling/safety_monitor.rs:210-217 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) horus_manager/src/commands/deploy.rs:105— horus_manager/src/commands/deploy.rs:105-112 | horus_manager/src/toolchain.rs:37-44 — 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) horus_manager/src/commands/deploy.rs:114— horus_manager/src/commands/deploy.rs:114-121 | horus_manager/src/toolchain.rs:47-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) horus_manager/src/commands/msg.rs:973— horus_manager/src/commands/msg.rs:973-980 | horus_manager/src/msgspec/canonical.rs:62-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.
Duplicated block (8 lines × 2) horus_py/src/depth_image.rs:140— horus_py/src/depth_image.rs:140-147 | horus_py/src/pointcloud.rs:105-114 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/pointcloud.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/pointcloud.rs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) REDACTED:1636— REDACTED:1636-1643 | REDACTED:1937-1945 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1636` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) horus_manager/src/main.rs:2580— horus_manager/src/main.rs:2580-2587 | horus_manager/src/main.rs:2714-2721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/main.rs:2580` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) horus_manager/src/commands/doc_extract_python.rs:168— horus_manager/src/commands/doc_extract_python.rs:168-175 | horus_manager/src/commands/doc_extract_python.rs:177-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_python.rs:168` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) horus_manager/src/registry/helpers.rs:843— horus_manager/src/registry/helpers.rs:843-850 | horus_manager/src/registry/helpers.rs:923-930 — both copies are in the same file, so extract the 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) horus_manager/src/registry/install.rs:1874— horus_manager/src/registry/install.rs:1874-1881 | horus_manager/src/registry/install.rs:1930-1937 — both copies are in the same file, so extract the 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) horus_manager/src/registry/publish.rs:1091— horus_manager/src/registry/publish.rs:1091-1098 | horus_manager/src/registry/publish.rs:1145-1152 — both copies are in the same file, so extract the 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) horus_manager/src/commands/pkg.rs:2332— horus_manager/src/commands/pkg.rs:2332-2339 | REDACTED:22-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.
Duplicated block (8 lines × 2) horus_manager/src/manifest.rs:1405— horus_manager/src/manifest.rs:1405-1412 | horus_manager/src/manifest.rs:1745-1752 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/manifest.rs:1405` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) horus_core/fuzz/fuzz_targets/fuzz_shm_header.rs:61— horus_core/fuzz/fuzz_targets/fuzz_shm_header.rs:61-69 | horus_core/fuzz/fuzz_targets/fuzz_shm_header.rs:77-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/fuzz/fuzz_targets/fuzz_shm_header.rs:61` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/test.rs:45— horus_manager/src/commands/test.rs:45-57 | horus_manager/src/commands/test.rs:66-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/test.rs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) horus_core/src/core/presence.rs:523— horus_core/src/core/presence.rs:523-530 | horus_core/src/scheduling/registry.rs:493-499 — 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 `horus_core/src/core/presence.rs:523` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) horus_manager/src/commands/doc.rs:42— horus_manager/src/commands/doc.rs:42-48 | horus_manager/src/commands/fmt.rs:80-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc.rs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) horus_manager/src/commands/doc_extract_rust.rs:546— horus_manager/src/commands/doc_extract_rust.rs:546-552 | horus_manager/src/commands/doc_extract_rust.rs:580-586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_rust.rs:546` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/run/install.rs:496— horus_manager/src/commands/run/install.rs:496-502 | horus_manager/src/commands/run/install.rs:903-909 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/install.rs:496` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/run/run_rust.rs:1125— horus_manager/src/commands/run/run_rust.rs:1125-1131 | horus_manager/src/commands/run/run_rust.rs:1135-1141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_manager/src/commands/topic.rs:405— horus_manager/src/commands/topic.rs:405-411 | horus_manager/src/commands/topic.rs:477-483 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_net/src/optimize/predict.rs:143— horus_net/src/optimize/predict.rs:143-149 | horus_net/src/optimize/predict.rs:155-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_manager/src/commands/pkg.rs:1278— horus_manager/src/commands/pkg.rs:1278-1284 | horus_manager/src/commands/plugin.rs:492-498 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_manager/src/commands/pkg.rs:1278` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/deploy.rs:489— horus_manager/src/commands/deploy.rs:489-495 | horus_manager/src/commands/deploy.rs:1226-1232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/deploy.rs:489` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/doc_extract.rs:1183— horus_manager/src/commands/doc_extract.rs:1183-1189 | horus_manager/src/commands/doc_extract.rs:1191-1197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract.rs:1183` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/run/run_cpp.rs:413— horus_manager/src/commands/run/run_cpp.rs:413-419 | horus_manager/src/commands/run/run_cpp.rs:541-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_manager/src/urdf.rs:44— horus_manager/src/urdf.rs:44-51 | horus_manager/src/urdf.rs:64-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_manager/src/commands/pkg.rs:1521— horus_manager/src/commands/pkg.rs:1521-1528 | horus_manager/src/commands/pkg.rs:1576-1582 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1521` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/cache.rs:271— horus_manager/src/commands/cache.rs:271-278 | horus_manager/src/commands/deploy.rs:492-498 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_manager/src/commands/cache.rs:271` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) horus_manager/src/commands/doc_extract_python.rs:67— horus_manager/src/commands/doc_extract_python.rs:67-73 | horus_manager/src/commands/doc_extract_python.rs:172-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_python.rs:67` it begins part-way through the construct above it, so those exact lines 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) horus_macros/src/node.rs:443— horus_macros/src/node.rs:443-449 | horus_macros/src/node.rs:455-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_macros/src/node.rs:443` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/deploy.rs:1139— horus_manager/src/commands/deploy.rs:1139-1145 | horus_manager/src/commands/deploy.rs:1265-1271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/deploy.rs:1139` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/run/features.rs:172— horus_manager/src/commands/run/features.rs:172-178 | horus_manager/src/commands/run/features.rs:310-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/features.rs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) horus_manager/src/commands/deps.rs:203— horus_manager/src/commands/deps.rs:203-209 | horus_manager/src/commands/deps.rs:345-351 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/deps.rs:203` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/upgrade.rs:1127— horus_manager/src/commands/upgrade.rs:1127-1133 | horus_manager/src/commands/upgrade.rs:1138-1144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) horus_manager/src/commands/doctor.rs:968— horus_manager/src/commands/doctor.rs:968-974 | horus_manager/src/commands/doctor.rs:1867-1873 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doctor.rs:968` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/msg.rs:445— horus_manager/src/commands/msg.rs:445-451 | horus_manager/src/commands/msg.rs:573-579 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/msg.rs:445` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Scheduler::check_timing_violations (cognitive 100) horus_core/src/scheduling/scheduler/mod.rs:5905— Scheduler::check_timing_violations has cognitive complexity 100 (threshold 15). Drivers by points: if/else 26 (89 pts), match/switch 2 (8 pts), boolean chains 3 (nesting depth added 69). 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.
Scheduler::run_with_filter (cognitive 92) horus_core/src/scheduling/scheduler/mod.rs:3212— Scheduler::run_with_filter has cognitive complexity 92 (threshold 15). Drivers by points: if/else 32 (59 pts), loops 9 (21 pts), match/switch 4 (10 pts), boolean chains 2 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::check_safety_monitors (cognitive 71) horus_core/src/scheduling/scheduler/mod.rs:4213— Scheduler::check_safety_monitors has cognitive complexity 71 (threshold 15). Drivers by points: if/else 18 (59 pts), loops 3 (7 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 48). 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.
Scheduler::execute_single_tick (cognitive 46) horus_core/src/scheduling/scheduler/mod.rs:2849— Scheduler::execute_single_tick has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (35 pts), loops 4 (9 pts), boolean chains 2 (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.
Scheduler::advance_tick (cognitive 46) horus_core/src/scheduling/scheduler/mod.rs:4632— Scheduler::advance_tick has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (33 pts), match/switch 2 (7 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::process_tick_result (cognitive 46) horus_core/src/scheduling/scheduler/mod.rs:5683— Scheduler::process_tick_result has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 5 (12 pts), loops 1 (3 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.
Scheduler::finalize_config (cognitive 40) horus_core/src/scheduling/scheduler/mod.rs:3076— Scheduler::finalize_config has cognitive complexity 40 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 4 (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.
Scheduler::initialize_filtered_nodes (cognitive 38) horus_core/src/scheduling/scheduler/mod.rs:3996— Scheduler::initialize_filtered_nodes has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (23 pts), match/switch 3 (13 pts), boolean chains 1, loops 1 (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.
Scheduler::should_tick_node (cognitive 31) horus_core/src/scheduling/scheduler/mod.rs:5357— Scheduler::should_tick_node has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::execute_nodes (cognitive 30) horus_core/src/scheduling/scheduler/mod.rs:6328— Scheduler::execute_nodes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 3 (9 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::apply_rt_optimizations (cognitive 28) horus_core/src/scheduling/scheduler/mod.rs:1827— Scheduler::apply_rt_optimizations has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (6 pts), loops 1 (3 pts), boolean chains 2 (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.
Scheduler::reinit_pending_nodes (cognitive 28) horus_core/src/scheduling/scheduler/mod.rs:4144— Scheduler::reinit_pending_nodes has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 2 (8 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::node_health_status_lines (cognitive 25) horus_core/src/scheduling/scheduler/mod.rs:1492— Scheduler::node_health_status_lines has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 13). 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.
Scheduler::prepare_node_tick (cognitive 24) horus_core/src/scheduling/scheduler/mod.rs:5474— Scheduler::prepare_node_tick has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (7 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.
Scheduler::process_control_commands (cognitive 23) horus_core/src/scheduling/scheduler/mod.rs:5147— Scheduler::process_control_commands has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (5 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::apply_config (cognitive 20) horus_core/src/scheduling/scheduler/mod.rs:1573— Scheduler::apply_config has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Scheduler::apply_safety_config (cognitive 20) horus_core/src/scheduling/scheduler/mod.rs:1694— Scheduler::apply_safety_config has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3, 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.
Scheduler::periodic_monitoring (cognitive 20) horus_core/src/scheduling/scheduler/mod.rs:4512— Scheduler::periodic_monitoring has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 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.
Scheduler::shutdown_filtered_nodes (cognitive 20) horus_core/src/scheduling/scheduler/mod.rs:4811— Scheduler::shutdown_filtered_nodes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 2 (8 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::print_timing_report (cognitive 18) horus_core/src/scheduling/scheduler/mod.rs:4943— Scheduler::print_timing_report has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduler::apply_degradation_action (cognitive 18) horus_core/src/scheduling/scheduler/mod.rs:6116— Scheduler::apply_degradation_action has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IC1 · Incompleteness & stubs· Empty method body · ×21
Empty method body — does nothing with its inputs horus_core/src/communication/topic/dispatch.rs:843— `warn_abandoned_claim` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/communication/topic/header.rs:206— `decrement_to_floor` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/communication/topic/header.rs:2437— `mark_thread_live` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/core/log_bridge.rs:127— `try_init_log_bridge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/blackbox.rs:16— `set_blackbox_hook` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:88— `set_scheduler_name` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:89— `counter` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:90— `gauge` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:91— `counter_with_labels` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:98— `gauge_with_labels` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:217— `record` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:223— `record_prestamped` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:263— `set_blackbox_hook` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/mod.rs:266— `record_external_event` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_core/src/scheduling/scheduler/mod.rs:38— `set_network_auto_wire` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_cpp/src/pool_ffi.rs:179— `pointcloud_destroy` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_manager/src/cargo_gen.rs:875— `remove_generated_build_configs` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_manager/src/cli_output.rs:23— `error` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_manager/src/cli_output.rs:28— `warn` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_manager/src/commands/deps.rs:375— `suggest_install` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs horus_manager/src/commands/doc_extract_html.rs:48— `write_head` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Configuration option is read nowhere horus_core/src/actions/types.rs:348— `ActionServerConfig.result_history_size` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_core/src/scheduling/record_replay.rs:397— `NodeTickSnapshot.duration_ns` is offered as a builder setter option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_core/src/scheduling/rt.rs:344— `RuntimeCapabilities.is_linux` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_core/src/types/pointcloud_descriptor.rs:49— `PointCloudDescriptor.field_count` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_core/src/types/pointcloud_descriptor.rs:51— `PointCloudDescriptor.is_dense` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/lockfile.rs:92— `ToolchainPins.cmake` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/manifest.rs:923— `DriverTableConfig.topic_state` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/manifest.rs:926— `DriverTableConfig.topic_command` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/manifest.rs:941— `DriverTableConfig.simulated` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/plugins/registry.rs:20— `PluginRegistry.schema_version` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/plugins/registry.rs:27— `PluginRegistry.project_name` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/plugins/registry.rs:30— `PluginRegistry.horus_version` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_manager/src/version.rs:134— `InstallManifest.installed_at` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:64— `Clock._pad` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:415— `SimSync.sim_time_ns` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:421— `SimSync._pad` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:480— `RateRequest.desired_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:482— `RateRequest.min_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:484— `RateRequest.max_hz` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere horus_types/src/time.rs:486— `RateRequest.requester_id` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. A test asserts that it parses, which proves the key is read from the input, not that it does anything. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
MethodTooLong: RegistryClient.publish horus_manager/src/registry/publish.rs:258— MethodTooLong — publish runs 399 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 299 over it, 3.99× 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: RegistryClient.install_from_registry horus_manager/src/registry/install.rs:399— MethodTooLong — install_from_registry runs 340 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 240 over it, 3.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Scheduler.run_with_filter horus_core/src/scheduling/scheduler/mod.rs:3212— MethodTooLong — run_with_filter runs 318 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 218 over it, 3.18× 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: RegistryClient.install_binary_artifact horus_manager/src/registry/install.rs:956— MethodTooLong — install_binary_artifact runs 251 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× 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: PyTopic.backend_type horus_py/src/topic.rs:1485— MethodTooLong — backend_type runs 245 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× 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: RtExecutor.rt_thread_main horus_core/src/scheduling/rt_executor.rs:1933— MethodTooLong — rt_thread_main runs 215 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RtExecutor.tick_node horus_core/src/scheduling/rt_executor.rs:1417— MethodTooLong — tick_node runs 209 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× 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: PyTopic.send horus_py/src/topic.rs:806— MethodTooLong — send runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RegistryClient.install_from_cratesio horus_manager/src/registry/install.rs:1725— MethodTooLong — install_from_cratesio runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RtReport.generate horus_core/src/scheduling/rt_report.rs:84— MethodTooLong — generate runs 159 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× 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: RegistryClient.install_from_pypi horus_manager/src/registry/install.rs:1495— MethodTooLong — install_from_pypi runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: PyTopic.recv horus_py/src/topic.rs:1267— MethodTooLong — recv runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NodeRegistration.validate horus_core/src/scheduling/node_builder.rs:559— MethodTooLong — validate runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Scheduler.check_timing_violations horus_core/src/scheduling/scheduler/mod.rs:5905— MethodTooLong — check_timing_violations runs 113 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: Scheduler.advance_tick horus_core/src/scheduling/scheduler/mod.rs:4632— MethodTooLong — advance_tick runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: EventExecutor.watcher_thread horus_core/src/scheduling/event_executor.rs:284— MethodTooLong — watcher_thread runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RtReport.print horus_core/src/scheduling/rt_report.rs:334— MethodTooLong — print runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Replicator.handle_timer horus_net/src/replicator.rs:955— MethodTooLong — handle_timer runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ShmRegion.new horus_sys/src/shm/macos.rs:162— MethodTooLong — new runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (6 lines × 2) horus_core/src/communication/topic/dispatch.rs:1388— horus_core/src/communication/topic/dispatch.rs:1388-1393 | horus_core/src/communication/topic/dispatch.rs:1621-1626 — both copies are in the same file, so extract the 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) horus_manager/src/commands/doc_extract_rust.rs:177— horus_manager/src/commands/doc_extract_rust.rs:177-182 | horus_manager/src/commands/doc_extract_rust.rs:265-270 — both copies are in the same file, so extract the 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) horus_manager/src/commands/pkg.rs:1772— horus_manager/src/commands/pkg.rs:1772-1777 | horus_manager/src/commands/pkg.rs:1814-1819 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1772` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/pkg.rs:1845— horus_manager/src/commands/pkg.rs:1845-1850 | horus_manager/src/commands/pkg.rs:1873-1878 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1845` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/run/run_cpp.rs:444— horus_manager/src/commands/run/run_cpp.rs:444-449 | horus_manager/src/commands/run/run_cpp.rs:574-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/run_cpp.rs:444` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:1782— REDACTED:1782-1787 | REDACTED:2273-2278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1782` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/topic.rs:380— horus_manager/src/commands/topic.rs:380-385 | horus_manager/src/commands/topic.rs:428-433 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) horus_sys/src/discover/linux.rs:97— horus_sys/src/discover/linux.rs:97-102 | horus_sys/src/discover/windows.rs:226-231 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_sys/src/discover/linux.rs:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) horus_sys/src/discover/macos.rs:310— horus_sys/src/discover/macos.rs:310-315 | horus_sys/src/discover/windows.rs:222-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/discover/macos.rs:310` it does not close everything it opens, so those exact lines 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) horus_core/src/communication/topic/mod.rs:447— horus_core/src/communication/topic/mod.rs:447-452 | horus_core/src/communication/topic/mod.rs:467-472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/mod.rs:447` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:445— REDACTED:445-450 | horus_manager/src/commands/pkg.rs:2091-2096 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) horus_py/src/depth_image.rs:84— horus_py/src/depth_image.rs:84-89 | horus_py/src/image.rs:128-133 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) horus_py/src/perception.rs:407— horus_py/src/perception.rs:407-412 | horus_types/src/math.rs:221-226 — 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 `other` to `&PyPointXYZ` in one and `&Point3` 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) horus_cpp_macros/src/cpp_gen.rs:22— horus_cpp_macros/src/cpp_gen.rs:22-27 | horus_cpp_macros/src/cxx_gen.rs:39-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.
Duplicated block (6 lines × 2) horus_manager/src/commands/run/install.rs:436— horus_manager/src/commands/run/install.rs:436-442 | horus_manager/src/commands/run/install.rs:885-890 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/install.rs:436` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/doc_extract_diff.rs:89— horus_manager/src/commands/doc_extract_diff.rs:89-94 | horus_manager/src/commands/doc_extract_diff.rs:107-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_diff.rs:89` it begins part-way through the construct above it, so those exact lines 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) horus_types/src/generic.rs:308— horus_types/src/generic.rs:308-313 | horus_types/src/generic.rs:319-324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_types/src/generic.rs:308` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/doc_extract_rust.rs:406— horus_manager/src/commands/doc_extract_rust.rs:406-411 | horus_manager/src/commands/doc_extract_rust.rs:445-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_rust.rs:406` it begins part-way through the construct above it, so those exact lines 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) horus_core/src/scheduling/rt.rs:190— horus_core/src/scheduling/rt.rs:190-195 | horus_core/src/scheduling/rt.rs:227-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/rt.rs:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) horus_core/src/core/log_buffer.rs:395— horus_core/src/core/log_buffer.rs:395-399 | horus_core/src/core/log_buffer.rs:860-864 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/core/log_buffer.rs:395` it does not close everything it opens, so those exact lines 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) horus_core/src/drivers/mod.rs:253— horus_core/src/drivers/mod.rs:253-258 | horus_core/src/drivers/mod.rs:429-433 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/drivers/mod.rs:253` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) horus_manager/src/commands/pkg.rs:1078— horus_manager/src/commands/pkg.rs:1078-1082 | horus_manager/src/commands/pkg.rs:2410-2414 — both copies are in the same file, so extract the 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) horus_manager/src/commands/topic.rs:382— horus_manager/src/commands/topic.rs:382-386 | horus_manager/src/commands/topic.rs:407-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/topic.rs:382` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/registry/install.rs:1658— horus_manager/src/registry/install.rs:1658-1662 | horus_manager/src/registry/install.rs:1926-1930 — both copies are in the same file, so extract the 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) horus_py/src/topic.rs:1130— horus_py/src/topic.rs:1130-1134 | horus_py/src/topic.rs:1218-1223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/topic.rs:1130` it does not close everything it opens, so those 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 × 2) horus_py/src/depth_image.rs:285— horus_py/src/depth_image.rs:285-289 | horus_py/src/pointcloud.rs:259-263 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/pointcloud.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/depth_image.rs:285` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) horus_py/src/depth_image.rs:297— horus_py/src/depth_image.rs:297-301 | horus_py/src/pointcloud.rs:271-275 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/pointcloud.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/depth_image.rs: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 (5 lines × 2) horus_py/src/perception.rs:561— horus_py/src/perception.rs:561-565 | horus_types/src/math.rs:113-117 — 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 `other` to `&PyLandmark` in one and `&Pose2D` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) horus_manager/src/commands/doc_extract.rs:519— horus_manager/src/commands/doc_extract.rs:519-523 | horus_manager/src/commands/doc_extract.rs:593-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract.rs:593` it does not close everything it opens, so those 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 × 2) horus_manager/src/commands/node.rs:140— horus_manager/src/commands/node.rs:140-144 | horus_manager/src/commands/node.rs:354-358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) horus_manager/src/commands/plugin.rs:362— horus_manager/src/commands/plugin.rs:362-366 | horus_manager/src/commands/plugin.rs:389-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/plugin.rs:362` it does not close everything it opens, so those exact lines 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) REDACTED:2040— REDACTED:2040-2044 | REDACTED:2047-2051 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) horus_manager/src/plugins/discovery.rs:220— horus_manager/src/plugins/discovery.rs:220-224 | horus_manager/src/registry/helpers.rs:697-701 — 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 `horus_manager/src/plugins/discovery.rs:220` it does not close everything it opens, so those exact lines 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) horus_manager/src/registry/helpers.rs:96— horus_manager/src/registry/helpers.rs:96-100 | horus_manager/src/registry/helpers.rs:160-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:96` it does not close everything it opens, so those exact lines 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) horus_py/src/params.rs:52— horus_py/src/params.rs:52-56 | horus_py/src/params.rs:63-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/params.rs: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.
Duplicated block (5 lines × 2) horus_sys/src/discover/linux.rs:113— horus_sys/src/discover/linux.rs:113-117 | horus_sys/src/discover/windows.rs:240-244 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
TooManyMethods: Scheduler horus_core/src/scheduling/scheduler/mod.rs:350— TooManyMethods — 112 methods, declared across 2 files: scheduler/mod.rs (100), scheduler/recording.rs (12). The bar is 30 methods; this is 82 over it, 3.73× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: RingTopic horus_core/src/communication/topic/mod.rs:789— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyTensorHandle horus_py/src/tensor.rs:174— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TensorPool horus_core/src/memory/tensor_pool.rs:357— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.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: Topic horus_core/src/communication/topic/mod.rs:3988— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyScheduler horus_py/src/scheduler.rs:691— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RegistryClient horus_manager/src/registry/mod.rs:273— TooManyMethods — 43 methods, declared across 4 files: registry/install.rs (19), registry/publish.rs (18), registry/mod.rs (5), registry/helpers.rs (1). The bar is 30 methods; this is 13 over it, 1.43× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: OccupancyGrid horus_core/src/memory/occupancy_grid.rs:39— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyTransformFrame horus_py/src/transform_frame.rs:257— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CostMap horus_core/src/memory/costmap.rs:40— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Scheduler horus_py/horus/__init__.py:1124— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyImage horus_py/src/image.rs:86— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PyImu horus_py/src/messages.rs:284— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NodePresence horus_core/src/core/presence.rs:36— 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: DepthImage horus_core/src/memory/depth_image.rs:38— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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: ReplayDebugger horus_core/src/scheduling/record_replay.rs:1623— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (10 lines × 2) horus_cpp/src/c_api.rs:2103— horus_cpp/src/c_api.rs:2103-2112 | horus_cpp/src/c_api.rs:2144-2153 — both copies are in the same file, so extract the 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) horus_manager/src/commands/doc_extract_rust.rs:289— horus_manager/src/commands/doc_extract_rust.rs:289-298 | horus_manager/src/commands/doc_extract_rust.rs:301-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) horus_manager/src/commands/msg.rs:3096— horus_manager/src/commands/msg.rs:3096-3105 | horus_manager/src/commands/msg.rs:3140-3149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/msg.rs:3096` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) horus_manager/src/commands/run/install.rs:1419— horus_manager/src/commands/run/install.rs:1419-1428 | horus_manager/src/registry/install.rs:2542-2551 — 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) REDACTED:1164— REDACTED:1164-1173 | REDACTED:1189-1198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1164` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:1199` calls `insert` and `REDACTED:1174` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) REDACTED:1829— REDACTED:1829-1838 | REDACTED:1839-1848 — both copies are in the same file, so extract the 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) horus_manager/src/registry/install.rs:2292— horus_manager/src/registry/install.rs:2292-2301 | horus_manager/src/registry/install.rs:2306-2315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:2292` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/run_with_prefix.rs:93— horus_manager/src/run_with_prefix.rs:93-102 | horus_manager/src/run_with_prefix.rs:155-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) horus_sys/src/platform/mod.rs:210— horus_sys/src/platform/mod.rs:210-219 | horus_sys/src/platform/mod.rs:270-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/platform/mod.rs:210` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) horus_manager/src/commands/launch.rs:625— horus_manager/src/commands/launch.rs:625-634 | horus_manager/src/commands/launch.rs:648-657 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/launch.rs:625` it does not close everything it opens, so those 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, `horus_manager/src/commands/launch.rs:646` calls `Some`, `iter_mut`, `find` and `horus_manager/src/commands/launch.rs:623` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) horus_py/src/image.rs:146— horus_py/src/image.rs:146-155 | horus_py/src/pointcloud.rs:71-80 — before extracting anything, compare `horus_py/src/image.rs` and `horus_py/src/pointcloud.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 `horus_py/src/image.rs:146` 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) horus_manager/src/cmake_gen.rs:388— horus_manager/src/cmake_gen.rs:388-400 | horus_manager/src/cmake_gen.rs:465-474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/cmake_gen.rs:388` it begins part-way through the construct above it, so those exact lines 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) horus_sys/src/shm/macos.rs:211— horus_sys/src/shm/macos.rs:211-220 | horus_sys/src/shm/macos.rs:267-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/shm/macos.rs:211` it begins part-way through the construct above it, so those 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) horus_manager/src/commands/run/run_cpp.rs:302— horus_manager/src/commands/run/run_cpp.rs:302-311 | horus_manager/src/commands/run/run_cpp.rs:336-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/run_cpp.rs:302` it begins part-way through the construct above it, so those exact lines 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) horus_sys/src/fs/mod.rs:119— horus_sys/src/fs/mod.rs:119-128 | horus_sys/src/fs/mod.rs:158-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/fs/mod.rs:119` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) horus_manager/src/registry/publish.rs:1100— horus_manager/src/registry/publish.rs:1100-1109 | horus_manager/src/registry/publish.rs:1154-1163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/publish.rs:1100` it begins part-way through the construct above it, so those 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.
RegistryClient::publish (cognitive 156) horus_manager/src/registry/publish.rs:258— RegistryClient::publish has cognitive complexity 156 (threshold 15). Drivers by points: if/else 62 (125 pts), loops 7 (20 pts), match/switch 6 (8 pts), boolean chains 3 (nesting depth added 78). 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.
RegistryClient::install_from_registry (cognitive 93) horus_manager/src/registry/install.rs:399— RegistryClient::install_from_registry has cognitive complexity 93 (threshold 15). Drivers by points: if/else 46 (78 pts), loops 3 (6 pts), match/switch 3 (5 pts), boolean chains 4 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegistryClient::update_packages (cognitive 68) horus_manager/src/registry/helpers.rs:1872— RegistryClient::update_packages has cognitive complexity 68 (threshold 15). Drivers by points: if/else 21 (57 pts), loops 4 (5 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 40). 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.
RegistryClient::install_binary_artifact (cognitive 67) horus_manager/src/registry/install.rs:956— RegistryClient::install_binary_artifact has cognitive complexity 67 (threshold 15). Drivers by points: if/else 33 (53 pts), loops 3 (6 pts), boolean chains 4, match/switch 2 (4 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.
RegistryClient::apply_driver_requirements (cognitive 52) horus_manager/src/registry/install.rs:1342— RegistryClient::apply_driver_requirements has cognitive complexity 52 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 4 (12 pts), match/switch 2 (5 pts) (nesting depth added 30). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RegistryClient::install_from_cratesio (cognitive 49) horus_manager/src/registry/install.rs:1725— RegistryClient::install_from_cratesio has cognitive complexity 49 (threshold 15). Drivers by points: if/else 27 (43 pts), match/switch 4 (5 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegistryClient::detect_system_python_package (cognitive 38) horus_manager/src/registry/install.rs:2266— RegistryClient::detect_system_python_package has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 5 (11 pts), boolean chains 2 (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.
RegistryClient::install_from_pypi (cognitive 37) horus_manager/src/registry/install.rs:1495— RegistryClient::install_from_pypi has cognitive complexity 37 (threshold 15). Drivers by points: if/else 21 (31 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegistryClient::get_available_versions (cognitive 35) horus_manager/src/registry/helpers.rs:1676— RegistryClient::get_available_versions has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 21). 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.
RegistryClient::install_dependencies (cognitive 26) horus_manager/src/registry/install.rs:1997— RegistryClient::install_dependencies has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 4 (7 pts), loops 2 (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.
RegistryClient::get_dependencies (cognitive 22) horus_manager/src/registry/helpers.rs:1761— RegistryClient::get_dependencies has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 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.
RegistryClient::install_dependency_spec (cognitive 18) horus_manager/src/registry/install.rs:306— RegistryClient::install_dependency_spec has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (8 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RegistryClient::query_driver_features (cognitive 16) horus_manager/src/registry/publish.rs:237— RegistryClient::query_driver_features has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (4 pts) (nesting depth added 10). 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.
horus_core::services::server::run_server_loop (cognitive 94) horus_core/src/services/server.rs:184— horus_core::services::server::run_server_loop has cognitive complexity 94 (threshold 15). Drivers by points: if/else 20 (66 pts), match/switch 3 (13 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 63). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::communication::write_topic_slot_bytes (cognitive 40) horus_core/src/communication/mod.rs:179— horus_core::communication::write_topic_slot_bytes has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (37 pts), boolean chains 2, match/switch 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::communication::topic::header::read_slot_from_region (cognitive 36) horus_core/src/communication/topic/header.rs:1828— horus_core::communication::topic::header::read_slot_from_region has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (28 pts), boolean chains 8 (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.
horus_core::communication::topic::dispatch::send_fanout_shm (cognitive 30) horus_core/src/communication/topic/dispatch.rs:1169— horus_core::communication::topic::dispatch::send_fanout_shm has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 4 (7 pts), loops 1 (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.
horus_core::scheduling::rt_executor::check_core_collisions (cognitive 30) horus_core/src/scheduling/rt_executor.rs:1148— horus_core::scheduling::rt_executor::check_core_collisions has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 4, loops 3 (4 pts), match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::communication::topic::dispatch::send_shm_mp_serde (cognitive 29) horus_core/src/communication/topic/dispatch.rs:1742— horus_core::communication::topic::dispatch::send_shm_mp_serde has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (24 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::core::rt_config::get_rt_recommended_cpus (cognitive 25) horus_core/src/core/rt_config.rs:574— horus_core::core::rt_config::get_rt_recommended_cpus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 4, 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.
horus_core::scheduling::primitives::apply_degradation_action (cognitive 25) horus_core/src/scheduling/primitives.rs:320— horus_core::scheduling::primitives::apply_degradation_action has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 1, match/switch 1 (nesting depth added 12). 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.
horus_core::scheduling::record_replay::diff_recordings (cognitive 24) horus_core/src/scheduling/record_replay.rs:1214— horus_core::scheduling::record_replay::diff_recordings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (7 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::core::log_buffer::log_drain_loop (cognitive 22) horus_core/src/core/log_buffer.rs:687— horus_core::core::log_buffer::log_drain_loop has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 3 (7 pts), loops 3 (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.
horus_core::drivers::load_from (cognitive 19) horus_core/src/drivers/mod.rs:152— horus_core::drivers::load_from has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (7 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_core::communication::topic::notify_topic_lifecycle (cognitive 18) horus_core/src/communication/topic/mod.rs:275— horus_core::communication::topic::notify_topic_lifecycle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 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.
horus_core::communication::topic::dispatch::recv_shm_pod_broadcast (cognitive 18) horus_core/src/communication/topic/dispatch.rs:2188— horus_core::communication::topic::dispatch::recv_shm_pod_broadcast has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×12
Duplicated block (8 lines × 3) horus_core/src/actions/client.rs:217— horus_core/src/actions/client.rs:217-224 | horus_core/src/actions/client.rs:870-877 | horus_core/src/actions/client.rs:930-937 — 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 `horus_core/src/actions/client.rs:217` it does not close everything it opens, so those exact lines 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 × 3) horus_core/src/communication/topic/mod.rs:4900— horus_core/src/communication/topic/mod.rs:4900-4907 | horus_core/src/communication/topic/mod.rs:4967-4974 | horus_core/src/communication/topic/mod.rs:5034-5041 — 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 `horus_core/src/communication/topic/mod.rs:4900` it does not close everything it opens, so those exact lines 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 × 3) horus_cpp/src/c_api.rs:1281— horus_cpp/src/c_api.rs:1281-1288 | horus_cpp/src/c_api.rs:1326-1333 | horus_cpp/src/c_api.rs:1371-1378 — 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 (8 lines × 3) horus_cpp/src/c_api.rs:1305— horus_cpp/src/c_api.rs:1305-1312 | horus_cpp/src/c_api.rs:1350-1357 | horus_cpp/src/c_api.rs:1395-1402 — 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 (8 lines × 3) horus_cpp/src/c_api.rs:1904— horus_cpp/src/c_api.rs:1904-1911 | horus_cpp/src/c_api.rs:1921-1928 | horus_cpp/src/c_api.rs:1938-1945 — 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 (8 lines × 3) horus_manager/src/registry/install.rs:691— horus_manager/src/registry/install.rs:691-698 | horus_manager/src/registry/install.rs:1530-1537 | horus_manager/src/registry/install.rs:1767-1774 — 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 `horus_manager/src/registry/install.rs:691` it does not close everything it opens, so those 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, `horus_manager/src/registry/install.rs:688` calls `package_name_to_path` and `horus_manager/src/registry/install.rs:1527` 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) horus_py/src/topic.rs:1279— horus_py/src/topic.rs:1279-1286 | horus_py/src/topic.rs:1299-1306 | horus_py/src/topic.rs:1319-1326 — 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 `horus_py/src/topic.rs:1279` it does not close everything it opens, so those exact lines 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 × 3) horus_cpp/src/c_api.rs:127— horus_cpp/src/c_api.rs:127-134 | horus_cpp/src/c_api.rs:242-249 | horus_cpp/src/c_api.rs:1558-1565 — 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 `horus_cpp/src/c_api.rs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) horus_manager/src/commands/pkg.rs:1263— horus_manager/src/commands/pkg.rs:1263-1270 | horus_manager/src/commands/pkg.rs:1373-1380 | horus_manager/src/commands/plugin.rs:471-478 — 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.
Duplicated block (8 lines × 3) horus_core/src/memory/costmap.rs:317— horus_core/src/memory/costmap.rs:317-324 | horus_core/src/memory/costmap.rs:340-347 | horus_core/src/memory/occupancy_grid.rs:168-175 — before extracting anything, compare `horus_core/src/memory/costmap.rs` and `horus_core/src/memory/occupancy_grid.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) horus_manager/src/registry/publish.rs:1099— horus_manager/src/registry/publish.rs:1099-1106 | horus_manager/src/registry/publish.rs:1153-1160 | horus_manager/src/registry/publish.rs:1175-1182 — 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 `horus_manager/src/registry/publish.rs:1099` it begins part-way through the construct above it, so those 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 × 3) horus_core/src/drivers/mod.rs:268— horus_core/src/drivers/mod.rs:268-275 | horus_manager/src/commands/migrate.rs:237-244 | horus_manager/src/commands/migrate.rs:284-291 — 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 `horus_core/src/drivers/mod.rs:268` it begins part-way through the construct above it, so those exact lines 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) horus_core/src/error.rs:1383— horus_core/src/error.rs:1383-1396 | horus_core/src/services/client.rs:233-245 — 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 `horus_core/src/error.rs:1383` 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) horus_core/src/memory/tensor_pool.rs:1520— horus_core/src/memory/tensor_pool.rs:1520-1533 | horus_core/src/memory/tensor_pool.rs:1706-1718 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/memory/tensor_pool.rs:1520` it does not close everything it opens, so those exact lines 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) horus_core/src/scheduling/scheduler/mod.rs:1658— horus_core/src/scheduling/scheduler/mod.rs:1658-1670 | horus_core/src/scheduling/scheduler/mod.rs:3154-3166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/scheduler/mod.rs:1658` it does not close everything it opens, so those 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, `horus_core/src/scheduling/scheduler/mod.rs:1671` calls `print_line` and `horus_core/src/scheduling/scheduler/mod.rs:3167` 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) horus_core/src/scheduling/scheduler/mod.rs:4002— horus_core/src/scheduling/scheduler/mod.rs:4002-4014 | horus_core/src/scheduling/scheduler/mod.rs:4148-4160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/scheduler/mod.rs:4002` it does not close everything it opens, so those exact lines 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) horus_cpp_macros/src/cxx_gen.rs:292— horus_cpp_macros/src/cxx_gen.rs:292-304 | horus_manager/src/commands/service.rs:334-346 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) horus_manager/src/commands/doctor.rs:1330— horus_manager/src/commands/doctor.rs:1330-1342 | horus_manager/src/commands/doctor.rs:1352-1364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doctor.rs:1330` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/doctor.rs:1655— horus_manager/src/commands/doctor.rs:1655-1667 | horus_manager/src/commands/upgrade.rs:753-765 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) horus_manager/src/commands/run/run_python.rs:47— horus_manager/src/commands/run/run_python.rs:47-59 | horus_manager/src/commands/run/run_python.rs:71-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/run_python.rs:47` it does not close everything it opens, so those 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, `horus_manager/src/commands/run/run_python.rs:46` calls `env` and `horus_manager/src/commands/run/run_python.rs:70` 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 lines × 2) horus_net/src/log_replication.rs:157— horus_net/src/log_replication.rs:157-169 | horus_net/src/presence.rs:149-161 — before extracting anything, compare `horus_net/src/log_replication.rs` and `horus_net/src/presence.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) horus_py/src/transform_frame.rs:766— horus_py/src/transform_frame.rs:766-778 | horus_py/src/transform_frame.rs:794-806 — both copies are in the same file, so extract the 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) horus_manager/src/registry/install.rs:1603— horus_manager/src/registry/install.rs:1603-1615 | horus_manager/src/registry/install.rs:1791-1803 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:1603` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Scheduler::run_with_filter (cyclomatic 48) horus_core/src/scheduling/scheduler/mod.rs:3212— Scheduler::run_with_filter has cyclomatic complexity 48 (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.
Scheduler::check_timing_violations (cyclomatic 34) horus_core/src/scheduling/scheduler/mod.rs:5905— Scheduler::check_timing_violations has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Scheduler::finalize_config (cyclomatic 25) horus_core/src/scheduling/scheduler/mod.rs:3076— Scheduler::finalize_config 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.
Scheduler::check_safety_monitors (cyclomatic 25) horus_core/src/scheduling/scheduler/mod.rs:4213— Scheduler::check_safety_monitors 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.
Scheduler::process_tick_result (cyclomatic 25) horus_core/src/scheduling/scheduler/mod.rs:5683— Scheduler::process_tick_result 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.
Scheduler::execute_single_tick (cyclomatic 23) horus_core/src/scheduling/scheduler/mod.rs:2849— Scheduler::execute_single_tick 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.
Scheduler::advance_tick (cyclomatic 20) horus_core/src/scheduling/scheduler/mod.rs:4632— Scheduler::advance_tick 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.
Scheduler::apply_config (cyclomatic 17) horus_core/src/scheduling/scheduler/mod.rs:1573— Scheduler::apply_config 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.
Scheduler::apply_rt_optimizations (cyclomatic 17) horus_core/src/scheduling/scheduler/mod.rs:1827— Scheduler::apply_rt_optimizations 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.
Scheduler::should_tick_node (cyclomatic 16) horus_core/src/scheduling/scheduler/mod.rs:5357— Scheduler::should_tick_node 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.
ClassTooLong: Scheduler horus_core/src/scheduling/scheduler/mod.rs:350— ClassTooLong — 2794 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 112 methods, 3 blocks, lines 350-6550. The bar is 400 significant lines; this is 2394 over it, 6.99× 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: RingTopic horus_core/src/communication/topic/mod.rs:789— ClassTooLong — 1089 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 63 methods, 5 blocks, lines 789-3942. The bar is 400 significant lines; this is 689 over it, 2.72× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TensorPool horus_core/src/memory/tensor_pool.rs:357— ClassTooLong — 1041 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 50 methods, 3 blocks, lines 357-2726. The bar is 400 significant lines; this is 641 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PyTopic horus_py/src/topic.rs:628— ClassTooLong — 960 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 2 blocks, lines 628-2123. The bar is 400 significant lines; this is 560 over it, 2.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Replicator horus_net/src/replicator.rs:67— ClassTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 2 blocks, lines 67-1368. The bar is 400 significant lines; this is 200 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PyTensorHandle horus_py/src/tensor.rs:174— ClassTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 56 methods, 3 blocks, lines 174-1221. The bar is 400 significant lines; this is 109 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RtExecutor horus_core/src/scheduling/rt_executor.rs:1251— ClassTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 1251-2428. The bar is 400 significant lines; this is 101 over it, 1.25× 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: ActionServerNode horus_core/src/actions/server.rs:435— ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 4 blocks, lines 435-1397. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Commands horus_manager/src/main.rs:134— ClassTooLong — 466 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 0 methods. The bar is 400 significant lines; this is 66 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×9
Edited copy of a member (14 corresponding lines) horus_core/src/memory/image.rs:129— horus_core/src/memory/image.rs:129-142 | horus_core/src/memory/image.rs:148-163 — 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) horus_core/src/core/presence.rs:410— horus_core/src/core/presence.rs:410-423 | horus_core/src/core/presence.rs:431-444 — 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) horus_core/src/scheduling/rt.rs:188— horus_core/src/scheduling/rt.rs:188-201 | horus_core/src/scheduling/rt.rs:225-238 — 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) horus_core/src/actions/client.rs:463— horus_core/src/actions/client.rs:463-499 | horus_core/src/actions/client.rs:502-515 — 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) horus_core/src/memory/grid_transform.rs:34— horus_core/src/memory/grid_transform.rs:34-47 | horus_core/src/memory/grid_transform.rs:62-75 — 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) horus_sys/src/shm/mod.rs:1878— horus_sys/src/shm/mod.rs:1878-1893 | horus_sys/src/shm/mod.rs:1896-1909 — 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) horus_macros/src/node.rs:611— horus_macros/src/node.rs:611-629 | horus_manager/src/msgspec/emit_ffi.rs:26-39 — 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) horus_core/src/communication/topic/mod.rs:4106— horus_core/src/communication/topic/mod.rs:4106-4119 | horus_core/src/communication/topic/mod.rs:4175-4188 — 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) horus_sys/src/rt/linux.rs:1419— horus_sys/src/rt/linux.rs:1419-1440 | horus_sys/src/rt/linux.rs:1462-1475 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×9
Edited copy of a member (12 corresponding lines) horus_sys/src/sync/cpp.rs:81— horus_sys/src/sync/cpp.rs:81-92 | horus_sys/src/sync/python.rs:38-52 — 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) horus_cpp/src/transform_ffi.rs:67— horus_cpp/src/transform_ffi.rs:67-78 | horus_cpp/src/transform_ffi.rs:86-100 — 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) horus_net/src/wire.rs:352— horus_net/src/wire.rs:352-363 | horus_net/src/wire.rs:379-390 — 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) horus_py/src/messages.rs:1463— horus_py/src/messages.rs:1463-1474 | horus_py/src/messages.rs:2485-2496 — 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) horus_core/src/core/log_buffer.rs:797— horus_core/src/core/log_buffer.rs:797-814 | horus_core/src/core/log_buffer.rs:820-831 — 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) horus_types/src/generic.rs:198— horus_types/src/generic.rs:198-209 | horus_types/src/generic.rs:226-237 — 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) horus_core/src/actions/server.rs:1382— horus_core/src/actions/server.rs:1382-1396 | horus_cpp/src/action_ffi.rs:571-582 — 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) horus_sys/src/sync/python.rs:25— horus_sys/src/sync/python.rs:25-36 | horus_sys/src/sync/rust.rs:25-37 — 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) horus_core/src/scheduling/async_executor.rs:447— horus_core/src/scheduling/async_executor.rs:447-458 | horus_core/src/scheduling/compute_executor.rs:910-921 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) horus_core/src/communication/topic/header.rs:2151— horus_core/src/communication/topic/header.rs:2151-2163 | horus_core/src/communication/topic/header.rs:2183-2194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/header.rs:2151` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/action.rs:152— horus_manager/src/commands/action.rs:152-163 | horus_manager/src/commands/action.rs:165-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/action.rs:152` it begins part-way through the construct above it, so those 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, `horus_manager/src/commands/action.rs:149` calls `Ok`, `discover_nodes` and `horus_manager/src/commands/action.rs:163` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) horus_manager/src/commands/action.rs:361— horus_manager/src/commands/action.rs:361-372 | horus_manager/src/commands/service.rs:212-223 — before extracting anything, compare `horus_manager/src/commands/action.rs` and `horus_manager/src/commands/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_manager/src/commands/action.rs:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) horus_manager/src/commands/deps.rs:66— horus_manager/src/commands/deps.rs:66-77 | horus_manager/src/commands/deps.rs:167-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/deps.rs:66` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/run/install.rs:317— horus_manager/src/commands/run/install.rs:317-328 | horus_manager/src/commands/run/install.rs:819-830 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/install.rs:317` 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) horus_manager/src/commands/service.rs:64— horus_manager/src/commands/service.rs:64-75 | horus_manager/src/commands/service.rs:93-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/service.rs:64` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/topic.rs:1048— horus_manager/src/commands/topic.rs:1048-1059 | horus_manager/src/commands/topic.rs:1204-1215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/topic.rs:1048` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_manager/src/commands/topic.rs:1063` calls `read_topic_messages_total`, `unwrap_or` and `horus_manager/src/commands/topic.rs:1218` 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 × 2) horus_core/src/core/presence.rs:412— horus_core/src/core/presence.rs:412-423 | horus_core/src/core/presence.rs:433-444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/core/presence.rs:412` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) horus_py/src/scheduler.rs:242— horus_py/src/scheduler.rs:242-253 | horus_py/src/scheduler.rs:391-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/scheduler.rs:242` 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.
RegistryClient::publish (cyclomatic 76) horus_manager/src/registry/publish.rs:258— RegistryClient::publish has cyclomatic complexity 76 (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.
RegistryClient::install_from_registry (cyclomatic 52) horus_manager/src/registry/install.rs:399— RegistryClient::install_from_registry has cyclomatic complexity 52 (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.
RegistryClient::install_binary_artifact (cyclomatic 39) horus_manager/src/registry/install.rs:956— RegistryClient::install_binary_artifact 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.
RegistryClient::update_packages (cyclomatic 27) horus_manager/src/registry/helpers.rs:1872— RegistryClient::update_packages 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.
RegistryClient::install_from_cratesio (cyclomatic 25) horus_manager/src/registry/install.rs:1725— RegistryClient::install_from_cratesio 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.
RegistryClient::install_from_pypi (cyclomatic 23) horus_manager/src/registry/install.rs:1495— RegistryClient::install_from_pypi 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.
RegistryClient::apply_driver_requirements (cyclomatic 22) horus_manager/src/registry/install.rs:1342— RegistryClient::apply_driver_requirements 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.
RegistryClient::detect_system_python_package (cyclomatic 18) horus_manager/src/registry/install.rs:2266— RegistryClient::detect_system_python_package 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×8
Edited copy of a member (13 corresponding lines) horus_core/src/core/hlog_rt.rs:104— horus_core/src/core/hlog_rt.rs:104-116 | horus_core/src/scheduling/blackbox_ring.rs:132-147 — 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) horus_core/src/scheduling/record_replay.rs:879— horus_core/src/scheduling/record_replay.rs:879-893 | horus_core/src/scheduling/record_replay.rs:896-908 — 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) horus_core/src/communication/topic/mod.rs:486— horus_core/src/communication/topic/mod.rs:486-498 | horus_core/src/communication/topic/mod.rs:501-513 — 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) horus_core/src/communication/topic/dispatch.rs:1100— horus_core/src/communication/topic/dispatch.rs:1100-1132 | horus_core/src/communication/topic/dispatch.rs:1145-1157 — 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) horus_core/src/core/rt_config.rs:507— horus_core/src/core/rt_config.rs:507-534 | horus_sys/src/rt/mod.rs:1261-1273 — 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) horus_types/src/time.rs:167— horus_types/src/time.rs:167-179 | horus_types/src/time.rs:493-507 — 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) horus_core/src/scheduling/scheduler/mod.rs:2016— horus_core/src/scheduling/scheduler/mod.rs:2016-2028 | horus_core/src/scheduling/scheduler/mod.rs:2052-2064 — 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) horus_manager/src/commands/doctor.rs:543— horus_manager/src/commands/doctor.rs:543-555 | horus_sys/src/fs/mod.rs:258-272 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (14 lines × 2) horus_core/src/communication/topic/dispatch.rs:1601— horus_core/src/communication/topic/dispatch.rs:1601-1616 | horus_core/src/communication/topic/dispatch.rs:1746-1759 — both copies are in the same file, so extract the 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) horus_core/src/memory/tensor_pool.rs:2598— horus_core/src/memory/tensor_pool.rs:2598-2611 | horus_core/src/memory/tensor_pool.rs:2633-2646 — both copies are in the same file, so extract the 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) horus_manager/src/commands/fmt.rs:46— horus_manager/src/commands/fmt.rs:46-59 | horus_manager/src/commands/lint.rs:31-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 `horus_manager/src/commands/fmt.rs:46` it begins part-way through the construct above it, so those exact lines 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) REDACTED:626— REDACTED:626-639 | REDACTED:705-718 — both copies are in the same file, so extract the 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) horus_manager/src/commands/proxy.rs:1028— horus_manager/src/commands/proxy.rs:1028-1041 | horus_manager/src/commands/proxy.rs:1096-1109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/proxy.rs:1028` it does not close everything it opens, so those 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) horus_manager/src/commands/run/run_rust.rs:677— horus_manager/src/commands/run/run_rust.rs:677-690 | horus_manager/src/commands/run/run_rust.rs:829-842 — both copies are in the same file, so extract the 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) horus_manager/src/commands/service.rs:283— horus_manager/src/commands/service.rs:283-296 | horus_manager/src/commands/service.rs:299-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) horus_py/src/node.rs:192— horus_py/src/node.rs:192-205 | horus_py/src/node.rs:219-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/node.rs:192` it does not close everything it opens, so those exact lines 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) horus_core/src/memory/tensor_handle.rs:230— horus_core/src/memory/tensor_handle.rs:230-240 | horus_core/src/memory/tensor_handle.rs:258-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) horus_net/src/discovery.rs:171— horus_net/src/discovery.rs:171-181 | horus_net/src/wire.rs:70-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) horus_manager/src/cmake_gen.rs:515— horus_manager/src/cmake_gen.rs:515-525 | horus_sys/src/shm/mod.rs:37-47 — 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) horus_core/src/types/dtype.rs:82— horus_core/src/types/dtype.rs:82-92 | horus_core/src/types/image_encoding.rs:67-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) horus_py/src/tensor.rs:648— horus_py/src/tensor.rs:648-660 | horus_py/src/tensor.rs:765-775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/tensor.rs:648` it begins part-way through the construct above it, so those exact lines 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) horus_sys/src/shm/macos.rs:226— horus_sys/src/shm/macos.rs:226-237 | horus_sys/src/shm/macos.rs:253-263 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/shm/macos.rs: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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) horus_py/src/image.rs:187— horus_py/src/image.rs:187-197 | horus_py/src/pointcloud.rs:81-91 — before extracting anything, compare `horus_py/src/image.rs` and `horus_py/src/pointcloud.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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 `horus_py/src/image.rs:187` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) REDACTED:459— REDACTED:459-469 | horus_manager/src/commands/topic.rs:100-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:459` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_manager/src/commands/topic.rs:97` calls `dimmed` and `REDACTED:457` 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.
TodoComment horus_manager/src/commands/doc_extract_cpp.rs:694— // ─── TODO Scanner ─────────────────────────────────────────────────────────── — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment horus_manager/src/commands/doc_extract_rust.rs:1107— // ─── TODO Scanner ─────────────────────────────────────────────────────────── — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment horus_manager/src/commands/doc_extract_cpp.rs:1154— // TODO: add calibration support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment horus_manager/src/commands/doc_extract_cpp.rs:1180— // TODO captured — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment horus_manager/src/commands/doc_extract_python.rs:593— // TODO captured — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment horus_manager/src/commands/doc_extract_rust.rs:1738— // TODO: refactor this module later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment benchmarks/src/output.rs:394— /// # TODO: what would let the tail be gated directly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×7
Edited copy of a member (17 corresponding lines) horus_py/src/scheduler.rs:1187— horus_py/src/scheduler.rs:1187-1203 | horus_py/src/scheduler.rs:1254-1271 — 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) horus_core/src/memory/tensor_handle.rs:227— horus_core/src/memory/tensor_handle.rs:227-243 | horus_core/src/memory/tensor_handle.rs:255-271 — 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) horus_core/src/communication/topic/header.rs:2150— horus_core/src/communication/topic/header.rs:2150-2167 | horus_core/src/communication/topic/header.rs:2182-2198 — 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) horus_core/src/types/dtype.rs:198— horus_core/src/types/dtype.rs:198-215 | horus_py/src/tensor_convert.rs:38-54 — 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) horus_core/src/communication/topic/shm_fanout.rs:1005— horus_core/src/communication/topic/shm_fanout.rs:1005-1021 | horus_core/src/communication/topic/shm_fanout.rs:1064-1084 — 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) horus_py/src/tensor.rs:670— horus_py/src/tensor.rs:670-686 | horus_py/src/tensor.rs:692-710 — 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) horus_core/src/communication/topic/dispatch.rs:1889— horus_core/src/communication/topic/dispatch.rs:1889-1905 | horus_core/src/communication/topic/dispatch.rs:2623-2647 — 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 (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) horus_manager/src/commands/deploy.rs:95— horus_manager/src/commands/deploy.rs:95-103 | horus_manager/src/toolchain.rs:26-34 — 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) horus_py/src/params.rs:51— horus_py/src/params.rs:51-59 | horus_py/src/params.rs:62-70 — 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) horus_core/src/core/log_buffer.rs:196— horus_core/src/core/log_buffer.rs:196-205 | horus_core/src/core/log_buffer.rs:209-217 — 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) horus_manager/src/plugins/resolver.rs:228— horus_manager/src/plugins/resolver.rs:228-239 | horus_manager/src/plugins/resolver.rs:247-255 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) horus_manager/src/commands/run/run_cpp.rs:847— horus_manager/src/commands/run/run_cpp.rs:847-855 | horus_manager/src/dispatch.rs:630-638 — 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) horus_manager/src/fingerprint.rs:43— horus_manager/src/fingerprint.rs:43-51 | horus_manager/src/plugins/registry.rs:272-281 — 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) horus_core/src/core/hlog.rs:252— horus_core/src/core/hlog.rs:252-260 | horus_core/src/core/tick_context.rs:236-244 — 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 (15 lines × 2) horus_core/src/actions/client.rs:209— horus_core/src/actions/client.rs:209-223 | horus_core/src/actions/client.rs:922-936 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/actions/client.rs:209` it does not close everything it opens, so those exact lines 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) horus_core/src/scheduling/record_replay.rs:85— horus_core/src/scheduling/record_replay.rs:85-100 | horus_core/src/scheduling/record_replay.rs:161-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/record_replay.rs: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 (15 lines × 2) horus_manager/src/commands/new.rs:571— horus_manager/src/commands/new.rs:571-585 | horus_manager/src/commands/new.rs:616-630 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/new.rs:571` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/pkg.rs:1601— horus_manager/src/commands/pkg.rs:1601-1615 | horus_manager/src/commands/pkg.rs:1630-1644 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1601` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/pod_decode.rs:62— horus_manager/src/commands/pod_decode.rs:62-76 | horus_manager/src/msgspec/mod.rs:103-117 — 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 (15 lines × 2) horus_manager/src/commands/run/deps.rs:529— horus_manager/src/commands/run/deps.rs:529-543 | horus_manager/src/commands/run/deps.rs:546-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/deps.rs:529` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) horus_manager/src/registry/helpers.rs:1285— horus_manager/src/registry/helpers.rs:1285-1299 | horus_manager/src/registry/helpers.rs:1302-1316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:1285` it does not close everything it opens, so those 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, `horus_manager/src/registry/helpers.rs:1283` calls `create_dir_all` and `horus_manager/src/registry/helpers.rs:1301` 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.
horus_core::services::server::run_server_loop (cyclomatic 33) horus_core/src/services/server.rs:184— horus_core::services::server::run_server_loop has cyclomatic complexity 33 (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.
horus_core::communication::topic::header::read_slot_from_region (cyclomatic 24) horus_core/src/communication/topic/header.rs:1828— horus_core::communication::topic::header::read_slot_from_region 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.
horus_core::communication::write_topic_slot_bytes (cyclomatic 21) horus_core/src/communication/mod.rs:179— horus_core::communication::write_topic_slot_bytes 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.
horus_core::scheduling::primitives::apply_degradation_action (cyclomatic 19) horus_core/src/scheduling/primitives.rs:320— horus_core::scheduling::primitives::apply_degradation_action 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.
horus_core::scheduling::rt_executor::check_core_collisions (cyclomatic 17) horus_core/src/scheduling/rt_executor.rs:1148— horus_core::scheduling::rt_executor::check_core_collisions 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.
horus_core::communication::topic::dispatch::send_shm_mp_serde (cyclomatic 16) horus_core/src/communication/topic/dispatch.rs:1742— horus_core::communication::topic::dispatch::send_shm_mp_serde 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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×6
Edited copy of a member (10 corresponding lines) horus_manager/src/commands/param.rs:317— horus_manager/src/commands/param.rs:317-326 | horus_manager/src/commands/param.rs:328-343 — 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) REDACTED:169— REDACTED:169-178 | horus_net/src/mac.rs:227-237 — 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) horus_py/src/depth_image.rs:187— horus_py/src/depth_image.rs:187-198 | horus_py/src/image.rs:274-283 — 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) horus_cpp/src/c_api.rs:1495— horus_cpp/src/c_api.rs:1495-1505 | horus_cpp/src/c_api.rs:1887-1896 — 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) horus_manager/src/commands/run/mod.rs:2166— horus_manager/src/commands/run/mod.rs:2166-2175 | horus_manager/src/commands/run/run_cpp.rs:476-485 — 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) horus_core/src/communication/topic/header.rs:2238— horus_core/src/communication/topic/header.rs:2238-2248 | horus_types/src/generic.rs:259-268 — 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.
horus_sys::discover::find_topics (cognitive 79) horus_sys/src/discover/mod.rs:317— horus_sys::discover::find_topics has cognitive complexity 79 (threshold 15). Drivers by points: if/else 17 (67 pts), loops 6 (11 pts), boolean chains 1 (nesting depth added 55). 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.
horus_sys::discover::linux::calculate_cpu_usage (cognitive 29) horus_sys/src/discover/linux.rs:86— horus_sys::discover::linux::calculate_cpu_usage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (28 pts), match/switch 1 (nesting depth added 19). 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.
horus_sys::discover::macos::get_cmdline (cognitive 22) horus_sys/src/discover/macos.rs:65— horus_sys::discover::macos::get_cmdline has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_sys::shm::reap_dir (cognitive 18) horus_sys/src/shm/mod.rs:1554— horus_sys::shm::reap_dir has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 4 (7 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_sys::shm::cleanup_stale_namespaces_in (cognitive 18) horus_sys/src/shm/mod.rs:1693— horus_sys::shm::cleanup_stale_namespaces_in has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (5 pts), 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.
Replicator::handle_export (cognitive 45) horus_net/src/replicator.rs:775— Replicator::handle_export has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 8 (15 pts), match/switch 2 (8 pts), boolean chains 1 (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.
Replicator::process_packet (cognitive 31) horus_net/src/replicator.rs:367— Replicator::process_packet has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 2, match/switch 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Replicator::process_incoming_message (cognitive 31) horus_net/src/replicator.rs:571— Replicator::process_incoming_message has cognitive complexity 31 (threshold 15). Drivers by points: if/else 20 (29 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.
Replicator::handle_timer (cognitive 27) horus_net/src/replicator.rs:955— Replicator::handle_timer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 4 (7 pts), match/switch 2 (4 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.
Replicator::run (cognitive 17) horus_net/src/replicator.rs:220— Replicator::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 3 (6 pts), loops 2 (3 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.
RingTopic::check_migration (cognitive 33) horus_core/src/communication/topic/mod.rs:1858— RingTopic::check_migration has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 3 (8 pts), match/switch 1 (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.
RingTopic::negotiate_shm_header (cognitive 21) horus_core/src/communication/topic/mod.rs:1179— RingTopic::negotiate_shm_header has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, loops 1 (2 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.
RingTopic::with_capacity_and_kind (cognitive 17) horus_core/src/communication/topic/mod.rs:1020— RingTopic::with_capacity_and_kind has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RingTopic::ensure_role (cognitive 16) horus_core/src/communication/topic/mod.rs:1763— RingTopic::ensure_role has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RingTopic::send_lossy_retry (cognitive 16) horus_core/src/communication/topic/mod.rs:3176— RingTopic::send_lossy_retry has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 4, boolean chains 2, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×5
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×5
Edited copy of a member (24 corresponding lines) horus_manager/src/commands/env.rs:325— horus_manager/src/commands/env.rs:325-349 | horus_manager/src/commands/setup_rt.rs:187-210 — 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) horus_core/src/communication/topic/shm_fanout.rs:1030— horus_core/src/communication/topic/shm_fanout.rs:1030-1056 | horus_core/src/communication/topic/shm_fanout.rs:1092-1115 — 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) horus_net/src/discovery.rs:170— horus_net/src/discovery.rs:170-206 | horus_net/src/wire.rs:69-92 — 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) horus_core/src/communication/topic/mod.rs:3080— horus_core/src/communication/topic/mod.rs:3080-3104 | horus_core/src/communication/topic/mod.rs:3563-3586 — 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) horus_core/src/scheduling/fault_tolerance/failure_policy.rs:188— horus_core/src/scheduling/fault_tolerance/failure_policy.rs:188-212 | horus_core/src/scheduling/fault_tolerance/failure_policy.rs:416-439 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×5
Edited copies of one member (3 members, 10+ corresponding lines) horus_manager/src/lockfile.rs:226— horus_manager/src/lockfile.rs:226-241 | horus_manager/src/manifest.rs:1400-1412 | horus_manager/src/manifest.rs:1743-1752 — 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) horus_core/src/memory/pointcloud.rs:76— horus_core/src/memory/pointcloud.rs:76-87 | horus_core/src/memory/pointcloud.rs:100-112 | horus_core/src/memory/pointcloud.rs:117-126 — 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) horus_py/src/scheduler.rs:1118— horus_py/src/scheduler.rs:1118-1127 | horus_py/src/scheduler.rs:1130-1139 | horus_py/src/scheduler.rs:1142-1155 — 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) horus_py/src/scheduler.rs:1296— horus_py/src/scheduler.rs:1296-1305 | horus_py/src/scheduler.rs:1318-1327 | horus_py/src/scheduler.rs:1330-1339 — 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) horus_cpp/src/c_api.rs:1084— horus_cpp/src/c_api.rs:1084-1094 | horus_cpp/src/c_api.rs:1151-1160 | horus_cpp/src/c_api.rs:1208-1217 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) horus_net/src/discovery.rs:159— horus_net/src/discovery.rs:159-168 | horus_net/src/wire.rs:59-66 — 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) horus_manager/src/commands/pkg.rs:2218— horus_manager/src/commands/pkg.rs:2218-2225 | horus_manager/src/commands/pkg.rs:2227-2238 — 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) horus_core/src/actions/server.rs:222— horus_core/src/actions/server.rs:222-230 | horus_core/src/actions/client.rs:265-272 — 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) horus_cpp_macros/src/cpp_gen.rs:294— horus_cpp_macros/src/cpp_gen.rs:294-301 | horus_cpp_macros/src/cxx_gen.rs:266-273 — 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) horus_core/src/scheduling/record_replay.rs:1398— horus_core/src/scheduling/record_replay.rs:1398-1407 | horus_manager/src/lockfile.rs:178-185 — 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 (15 corresponding lines) · ×5
Edited copy of a member (15 corresponding lines) horus_cpp/src/c_api.rs:1710— horus_cpp/src/c_api.rs:1710-1724 | horus_cpp/src/c_api.rs:1736-1750 — 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) horus_core/src/types/image_encoding.rs:138— horus_core/src/types/image_encoding.rs:138-153 | horus_py/src/image.rs:44-58 — 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) horus_core/src/communication/mod.rs:144— horus_core/src/communication/mod.rs:144-159 | horus_core/src/communication/topic/header.rs:1631-1645 — 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) horus_core/src/scheduling/record_replay.rs:507— horus_core/src/scheduling/record_replay.rs:507-524 | horus_core/src/scheduling/record_replay.rs:602-616 — 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) horus_sys/src/sync/cpp.rs:7— horus_sys/src/sync/cpp.rs:7-21 | horus_sys/src/sync/python.rs:7-22 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12–13 lines × 2) horus_core/src/communication/topic/dispatch.rs:1655— horus_core/src/communication/topic/dispatch.rs:1655-1667 | horus_core/src/communication/topic/dispatch.rs:1710-1721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:1655` it begins part-way through the construct above it, so those 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) horus_core/src/scheduling/async_executor.rs:211— horus_core/src/scheduling/async_executor.rs:211-222 | horus_core/src/scheduling/compute_executor.rs:678-690 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:211` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) horus_manager/src/commands/doc_extract_cpp.rs:244— horus_manager/src/commands/doc_extract_cpp.rs:244-256 | horus_manager/src/commands/doc_extract_cpp.rs:343-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 (12–13 lines × 2) horus_manager/src/commands/topic.rs:1131— horus_manager/src/commands/topic.rs:1131-1143 | horus_manager/src/commands/topic.rs:1303-1314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/topic.rs:1131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) horus_manager/src/registry/install.rs:275— horus_manager/src/registry/install.rs:275-286 | horus_manager/src/registry/install.rs:2357-2369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:275` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) horus_core/src/communication/topic/dispatch.rs:2038— horus_core/src/communication/topic/dispatch.rs:2038-2046 | horus_core/src/communication/topic/dispatch.rs:2408-2416 | horus_core/src/communication/topic/dispatch.rs:2458-2466 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) horus_macros/src/node.rs:213— horus_macros/src/node.rs:213-221 | horus_macros/src/node.rs:245-253 | horus_macros/src/node.rs:277-285 — 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 `horus_macros/src/node.rs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) horus_py/src/depth_image.rs:270— horus_py/src/depth_image.rs:270-278 | horus_py/src/image.rs:399-407 | horus_py/src/pointcloud.rs:244-252 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) horus_manager/src/registry/publish.rs:882— horus_manager/src/registry/publish.rs:882-893 | horus_manager/src/registry/publish.rs:969-977 | horus_manager/src/registry/publish.rs:992-1002 — 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 `horus_manager/src/registry/publish.rs:882` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) horus_py/src/depth_image.rs:139— horus_py/src/depth_image.rs:139-147 | horus_py/src/image.rs:211-219 | horus_py/src/pointcloud.rs:104-112 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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–9 lines × 2) horus_cpp/src/node_ffi.rs:114— horus_cpp/src/node_ffi.rs:114-121 | horus_cpp/src/node_ffi.rs:163-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_cpp/src/node_ffi.rs:114` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/pkg.rs:1280— horus_manager/src/commands/pkg.rs:1280-1288 | horus_manager/src/commands/pkg.rs:1389-1396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1280` it begins part-way through the construct above it, so those 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–9 lines × 2) horus_manager/src/commands/pkg.rs:1817— horus_manager/src/commands/pkg.rs:1817-1825 | horus_manager/src/commands/pkg.rs:1849-1856 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1817` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/registry/helpers.rs:1506— horus_manager/src/registry/helpers.rs:1506-1513 | horus_manager/src/registry/helpers.rs:1523-1531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:1506` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/pkg.rs:1482— horus_manager/src/commands/pkg.rs:1482-1489 | horus_manager/src/commands/pkg.rs:1505-1513 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) horus_manager/src/commands/topic.rs:405— horus_manager/src/commands/topic.rs:405-410 | horus_manager/src/commands/topic.rs:460-465 | horus_manager/src/commands/topic.rs:477-482 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_manager/src/commands/topic.rs:458` calls `from_le_bytes`, `try_into`, `unwrap_or` and `horus_manager/src/commands/topic.rs:404` 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) horus_py/src/depth_image.rs:112— horus_py/src/depth_image.rs:112-117 | horus_py/src/image.rs:152-157 | horus_py/src/pointcloud.rs:77-82 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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 `horus_py/src/depth_image.rs:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) horus_py/src/messages.rs:1958— horus_py/src/messages.rs:1958-1963 | horus_py/src/messages.rs:2103-2108 | horus_py/src/messages.rs:2265-2270 — 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 `horus_py/src/messages.rs:1958` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) horus_manager/src/commands/launch.rs:197— horus_manager/src/commands/launch.rs:197-202 | horus_types/src/math.rs:25-30 | horus_types/src/time.rs:10-15 — 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 (6 lines × 3) horus_manager/src/commands/blackbox.rs:440— horus_manager/src/commands/blackbox.rs:440-445 | horus_manager/src/commands/cache.rs:271-277 | horus_manager/src/commands/deploy.rs:492-497 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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.
Hollow method — returns a constant without doing the work horus_core/src/scheduling/mod.rs:108— `export` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work horus_core/src/scheduling/mod.rs:240— `load` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work horus_manager/src/node_detector.rs:130— `nodes_to_features` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work horus_py/src/custom_messages/mod.rs:19— `register_custom_messages` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work horus_sys/src/rt/macos.rs:114— `set_best_effort_class` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Test failure does not fail the CI gate · ×5
Test failure does not fail the CI gate REDACTED:255— `continue-on-error: true` lets the step or job that runs `cargo test -p horus_manager --lib source_resolver -- --ignored` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Test failure does not fail the CI gate .github/workflows/coverage.yml:33— `continue-on-error: true` lets the step or job that runs `cargo llvm-cov --workspace --exclude horus_benchmarks --exclude horus --exclude horus_library --exclude horus_py --lcov --…` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Test failure does not fail the CI gate .github/workflows/integration-tests.yml:246— `continue-on-error: true` lets the step or job that runs `cargo test -p horus_core --release --test "$suite" -- --ignored --test-threads=1 --nocapture || {` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Test failure does not fail the CI gate .github/workflows/integration-tests.yml:258— `cargo test -p horus_core --release --test "$suite" -- --ignored --test-threads=1 --nocapture || {` runs the tests, and `|| {` discards their exit status — a failing suite leaves the check green. Let the test command's failure fail the step (re-raise it after logging).
Test failure does not fail the CI gate .github/workflows/integration-tests.yml:291— `continue-on-error: true` lets the step or job that runs `cargo test -p horus_core --release --test multi_scheduler_matrix -- --ignored --test-threads=1 --nocapture` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Replicator::process_packet (cyclomatic 20) horus_net/src/replicator.rs:367— Replicator::process_packet 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.
Replicator::process_incoming_message (cyclomatic 19) horus_net/src/replicator.rs:571— Replicator::process_incoming_message 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.
Replicator::handle_export (cyclomatic 19) horus_net/src/replicator.rs:775— Replicator::handle_export 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.
Replicator::handle_timer (cyclomatic 18) horus_net/src/replicator.rs:955— Replicator::handle_timer 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.
TooManyFields: Scheduler horus_core/src/scheduling/scheduler/mod.rs:350— TooManyFields — 35 stored fields beside 112 methods. The bar is 30 stored fields; this is 5 over it, 1.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: TopicHeader horus_core/src/communication/topic/header.rs:286— TooManyFields — 35 stored fields beside 28 methods. The bar is 30 stored fields; this is 5 over it, 1.17× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: Replicator horus_net/src/replicator.rs:67— TooManyFields — 33 stored fields beside 16 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: NodeStatus horus_manager/src/discovery/mod.rs:46— TooManyFields — 32 stored fields. The bar is 30 stored fields; this is 2 over it, 1.07× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×4
Edited copy of a member (37 corresponding lines) horus_manager/src/commands/pkg.rs:399— horus_manager/src/commands/pkg.rs:399-437 | horus_manager/src/registry/helpers.rs:654-690 — 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) horus_manager/src/commands/new.rs:556— horus_manager/src/commands/new.rs:556-592 | horus_manager/src/commands/new.rs:595-641 — 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) horus_core/src/actions/client.rs:361— horus_core/src/actions/client.rs:361-397 | horus_core/src/actions/server.rs:1240-1281 — 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) horus_sys/src/rt/macos.rs:7— horus_sys/src/rt/macos.rs:7-50 | horus_sys/src/rt/windows.rs:7-43 — 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 (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) horus_py/src/transform_frame.rs:760— horus_py/src/transform_frame.rs:760-781 | horus_py/src/transform_frame.rs:788-811 — 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) horus_cpp/src/c_api.rs:1434— horus_cpp/src/c_api.rs:1434-1466 | horus_cpp/src/c_api.rs:1547-1568 — 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) horus_manager/src/registry/publish.rs:1062— horus_manager/src/registry/publish.rs:1062-1088 | horus_manager/src/registry/publish.rs:1189-1210 — 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) horus_core/src/scheduling/scheduler/mod.rs:1066— horus_core/src/scheduling/scheduler/mod.rs:1066-1087 | horus_core/src/scheduling/scheduler/mod.rs:1968-1991 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×4
Edited copy of a member (21 corresponding lines) horus_py/src/tensor.rs:1159— horus_py/src/tensor.rs:1159-1179 | horus_py/src/tensor_convert.rs:13-35 — 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) horus_core/src/error.rs:1375— horus_core/src/error.rs:1375-1396 | horus_core/src/services/client.rs:225-245 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) horus_manager/src/commands/run/features.rs:169— horus_manager/src/commands/run/features.rs:169-190 | horus_manager/src/commands/run/features.rs:307-327 — 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) horus_core/src/scheduling/async_executor.rs:54— horus_core/src/scheduling/async_executor.rs:54-74 | horus_core/src/scheduling/compute_executor.rs:509-529 — 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 (16 corresponding lines) · ×4
Edited copy of a member (16 corresponding lines) horus_manager/src/commands/pkg.rs:2122— horus_manager/src/commands/pkg.rs:2122-2142 | horus_manager/src/commands/pkg.rs:2163-2178 — 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) horus_sys/src/sync/cpp.rs:64— horus_sys/src/sync/cpp.rs:64-79 | horus_sys/src/sync/rust.rs:39-54 — 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) horus_core/src/communication/topic/mod.rs:673— horus_core/src/communication/topic/mod.rs:673-688 | horus_core/src/communication/topic/mod.rs:718-734 — 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) horus_core/src/scheduling/safety_monitor.rs:1040— horus_core/src/scheduling/safety_monitor.rs:1040-1055 | horus_core/src/scheduling/safety_monitor.rs:1647-1668 — 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 (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) horus_manager/src/plugins/registry.rs:223— horus_manager/src/plugins/registry.rs:223-229 | horus_manager/src/plugins/trust.rs:93-102 — 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) horus_core/src/memory/image.rs:244— horus_core/src/memory/image.rs:244-250 | horus_core/src/memory/occupancy_grid.rs:314-320 — 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) horus_core/src/communication/mod.rs:90— horus_core/src/communication/mod.rs:90-96 | horus_core/src/communication/topic/header.rs:1565-1571 — 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) horus_core/src/core/hlog.rs:243— horus_core/src/core/hlog.rs:243-249 | horus_core/src/core/tick_context.rs:182-189 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) horus_core/src/memory/costmap.rs:422— horus_core/src/memory/costmap.rs:422-440 | horus_core/src/memory/occupancy_grid.rs:236-254 — before extracting anything, compare `horus_core/src/memory/costmap.rs` and `horus_core/src/memory/occupancy_grid.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 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 (19 lines × 2) horus_core/src/scheduling/async_executor.rs:183— horus_core/src/scheduling/async_executor.rs:183-201 | horus_core/src/scheduling/compute_executor.rs:627-645 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs: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.
Duplicated block (19 lines × 2) horus_manager/src/registry/install.rs:2470— horus_manager/src/registry/install.rs:2470-2488 | horus_manager/src/registry/install.rs:2529-2547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:2470` it does not close everything it opens, so those exact lines 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) horus_macros/src/node.rs:218— horus_macros/src/node.rs:218-236 | horus_macros/src/node.rs:250-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) horus_core/src/core/hlog_rt.rs:188— horus_core/src/core/hlog_rt.rs:188-204 | horus_core/src/scheduling/rt_executor.rs:197-213 — 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 `horus_core/src/core/hlog_rt.rs:188` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) horus_manager/src/commands/doc_extract_rust.rs:156— horus_manager/src/commands/doc_extract_rust.rs:156-172 | horus_manager/src/commands/doc_extract_rust.rs:201-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_rust.rs:156` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_manager/src/commands/doc_extract_rust.rs:174` calls `extract_derives` and `horus_manager/src/commands/doc_extract_rust.rs:218` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) horus_core/src/scheduling/rt_executor.rs:644— horus_core/src/scheduling/rt_executor.rs:644-677 | horus_core/src/scheduling/safety_monitor.rs:184-200 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) horus_manager/src/commands/check.rs:582— horus_manager/src/commands/check.rs:582-598 | horus_manager/src/commands/check.rs:668-684 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/check.rs:582` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) horus_core/src/scheduling/scheduler/mod.rs:5094— horus_core/src/scheduling/scheduler/mod.rs:5094-5109 | horus_core/src/scheduling/scheduler/mod.rs:5310-5324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/scheduler/mod.rs:5094` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) horus_manager/src/commands/launch.rs:379— horus_manager/src/commands/launch.rs:379-394 | horus_manager/src/commands/launch.rs:1319-1333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) horus_net/src/event_loop/epoll.rs:131— horus_net/src/event_loop/epoll.rs:131-146 | horus_net/src/event_loop/kqueue.rs:190-204 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_net/src/event_loop/epoll.rs:131` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15–16 lines × 2) REDACTED:522— REDACTED:522-537 | REDACTED:631-645 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:522` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap horus_manager/src/msgspec/canonical.rs:23— `render_rust` is public and takes `t: &Type` from its caller, and it calls itself at line 23 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `render_rust` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap horus_manager/src/msgspec/canonical.rs:35— `render_cpp` is public and takes `t: &Type` from its caller, and it calls itself at line 35 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `render_cpp` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap horus_manager/src/msgspec/layout.rs:43— `size_align` is public and takes `t: &Type` from its caller, and it calls itself at line 43 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `size_align` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap horus_core/src/memory/shm_region.rs:113— `as_slice_mut` is public and takes a `ShmRegion` as its receiver from its caller, and it calls itself at line 113 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `as_slice_mut` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Parser::parse_type (cognitive 28) horus_manager/src/msgspec/parse.rs:392— Parser::parse_type has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 3 (7 pts), loops 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser::parse_message (cognitive 26) horus_manager/src/msgspec/parse.rs:504— Parser::parse_message has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (23 pts), match/switch 2, 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.
Parser::parse_attrs (cognitive 21) horus_manager/src/msgspec/parse.rs:343— Parser::parse_attrs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_net::guard::glob_match (cognitive 20) horus_net/src/guard.rs:150— horus_net::guard::glob_match has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (3 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.
horus_net::discovery::find_matches (cognitive 17) horus_net/src/discovery.rs:313— horus_net::discovery::find_matches has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 5, loops 2 (3 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.
horus_net::log_replication::handle_remote_logs (cognitive 16) horus_net/src/log_replication.rs:154— horus_net::log_replication::handle_remote_logs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (2 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×3
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) horus_core/src/scheduling/async_executor.rs:335— horus_core/src/scheduling/async_executor.rs:335-443 | horus_core/src/scheduling/compute_executor.rs:798-906 | horus_core/src/scheduling/event_executor.rs:290-572 | horus_core/src/scheduling/rt_executor.rs:1428-1927 — 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) horus_manager/src/commands/blackbox.rs:420— horus_manager/src/commands/blackbox.rs:420-464 | horus_manager/src/commands/cache.rs:246-290 | horus_manager/src/commands/deploy.rs:355-568 | horus_manager/src/commands/deploy.rs:1203-1282 — 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) horus_manager/src/commands/upgrade.rs:933— horus_manager/src/commands/upgrade.rs:933-953 | horus_manager/src/source_resolver.rs:912-932 | horus_manager/src/source_resolver.rs:935-954 | horus_manager/src/source_resolver.rs:957-981 — 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 (33 corresponding lines) · ×3
Edited copy of a member (33 corresponding lines) horus_net/src/wire.rs:442— horus_net/src/wire.rs:442-474 | horus_net/src/wire.rs:492-527 — 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.
Edited copy of a member (33 corresponding lines) horus_core/src/core/hlog.rs:420— horus_core/src/core/hlog.rs:420-465 | horus_core/src/core/hlog.rs:476-508 — 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.
Edited copy of a member (33 corresponding lines) horus_core/src/scheduling/async_executor.rs:77— horus_core/src/scheduling/async_executor.rs:77-109 | horus_core/src/scheduling/compute_executor.rs:532-564 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) horus_core/src/communication/topic/mod.rs:446— horus_core/src/communication/topic/mod.rs:446-463 | horus_core/src/communication/topic/mod.rs:466-483 — 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) horus_manager/src/commands/deps.rs:141— horus_manager/src/commands/deps.rs:141-158 | horus_manager/src/commands/deps.rs:315-336 — 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) horus_manager/src/discovery/mod.rs:242— horus_manager/src/discovery/mod.rs:242-259 | horus_manager/src/discovery/mod.rs:261-278 — 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 copies of one member (3 members, 12+ corresponding lines) · ×3
Edited copies of one member (3 members, 12+ corresponding lines) horus_py/src/messages.rs:1951— horus_py/src/messages.rs:1951-1963 | horus_py/src/messages.rs:2096-2108 | horus_py/src/messages.rs:2259-2270 — 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) horus_py/src/messages.rs:7472— horus_py/src/messages.rs:7472-7483 | horus_py/src/messages.rs:7883-7894 | horus_py/src/messages.rs:8034-8045 — 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) horus_py/src/depth_image.rs:56— horus_py/src/depth_image.rs:56-67 | horus_py/src/image.rs:95-106 | horus_py/src/pointcloud.rs:30-41 — 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, 11+ corresponding lines) · ×3
Edited copies of one member (3 members, 11+ corresponding lines) horus_cpp/src/c_api.rs:1903— horus_cpp/src/c_api.rs:1903-1913 | horus_cpp/src/c_api.rs:1920-1930 | horus_cpp/src/c_api.rs:1937-1947 — 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) horus_core/src/memory/costmap.rs:327— horus_core/src/memory/costmap.rs:327-337 | horus_core/src/memory/costmap.rs:350-360 | horus_core/src/memory/occupancy_grid.rs:181-191 — 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) horus_core/src/error.rs:203— horus_core/src/error.rs:203-213 | horus_core/src/error.rs:219-229 | horus_core/src/error.rs:235-245 — 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, 4+ corresponding lines) · ×3
Edited copies of one member (3 members, 4+ corresponding lines) horus_sys/src/discover/linux.rs:9— horus_sys/src/discover/linux.rs:9-12 | horus_sys/src/discover/macos.rs:9-12 | horus_sys/src/discover/windows.rs:9-12 — 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.
Edited copies of one member (3 members, 4+ corresponding lines) horus_core/src/services/client.rs:65— horus_core/src/services/client.rs:65-73 | horus_cpp/src/action_ffi.rs:45-48 | horus_cpp/src/service_ffi.rs:41-44 — 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.
Edited copies of one member (3 members, 4+ corresponding lines) horus_py/src/depth_image.rs:130— horus_py/src/depth_image.rs:130-133 | horus_py/src/image.rs:202-205 | horus_py/src/pointcloud.rs:95-98 — 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 copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) horus_core/src/core/presence.rs:514— horus_core/src/core/presence.rs:514-518 | horus_manager/src/commands/launch.rs:277-281 — 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) horus_manager/src/fingerprint.rs:83— horus_manager/src/fingerprint.rs:83-87 | horus_manager/src/lockfile.rs:731-736 — 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) horus_py/src/depth_image.rs:180— horus_py/src/depth_image.rs:180-184 | horus_py/src/image.rs:267-272 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25 lines × 2) horus_core/src/communication/topic/dispatch.rs:2397— horus_core/src/communication/topic/dispatch.rs:2397-2421 | horus_core/src/communication/topic/dispatch.rs:2447-2471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:2397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) horus_core/src/scheduling/scheduler/mod.rs:2818— horus_core/src/scheduling/scheduler/mod.rs:2818-2842 | horus_core/src/scheduling/scheduler/mod.rs:3232-3256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) horus_py/src/tensor.rs:364— horus_py/src/tensor.rs:364-388 | horus_py/src/tensor.rs:434-458 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/tensor.rs:364` it begins part-way through the construct above it, so those exact lines 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) horus_net/src/estop.rs:134— horus_net/src/estop.rs:134-143 | horus_net/src/presence.rs:194-203 | horus_net/src/presence.rs:260-269 — 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.
Duplicated block (10 lines × 3) horus_net/src/log_replication.rs:180— horus_net/src/log_replication.rs:180-189 | horus_net/src/log_replication.rs:199-208 | horus_net/src/presence.rs:241-250 — before extracting anything, compare `horus_net/src/log_replication.rs` and `horus_net/src/presence.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) horus_sys/src/platform/mod.rs:210— horus_sys/src/platform/mod.rs:210-219 | horus_sys/src/platform/mod.rs:245-254 | horus_sys/src/platform/mod.rs:270-279 — 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 `horus_sys/src/platform/mod.rs:210` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) horus_core/src/communication/topic/dispatch.rs:1489— horus_core/src/communication/topic/dispatch.rs:1489-1495 | horus_core/src/communication/topic/dispatch.rs:1764-1770 | horus_core/src/communication/topic/dispatch.rs:1823-1829 — 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 (7 lines × 3) horus_cpp/src/c_api.rs:1989— horus_cpp/src/c_api.rs:1989-1995 | horus_cpp/src/c_api.rs:2025-2031 | horus_cpp/src/c_api.rs:2053-2059 — 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 `horus_cpp/src/c_api.rs:1989` it begins part-way through the construct above it, so those exact lines 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) REDACTED:2155— REDACTED:2155-2161 | REDACTED:2167-2173 | REDACTED:2179-2185 — 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 `REDACTED:2155` it does not close everything it opens, so those exact lines 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) horus_py/src/depth_image.rs:168— horus_py/src/depth_image.rs:168-172 | horus_py/src/image.rs:256-260 | horus_py/src/pointcloud.rs:140-144 | horus_py/src/tensor.rs:397-403 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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, `horus_py/src/tensor.rs:411` calls `clone`, `drop`, `borrow_mut` and `horus_py/src/depth_image.rs:174` 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 × 4) horus_core/src/scheduling/async_executor.rs:372— horus_core/src/scheduling/async_executor.rs:372-376 | horus_core/src/scheduling/compute_executor.rs:835-839 | horus_core/src/scheduling/event_executor.rs:484-488 | horus_core/src/scheduling/rt_executor.rs:1832-1837 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:372` it does not close everything it opens, so those exact lines 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) horus_py/src/image.rs:440— horus_py/src/image.rs:440-444 | horus_py/src/image.rs:452-456 | horus_py/src/image.rs:464-468 | horus_py/src/image.rs:476-480 — 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. 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.
RtExecutor::tick_node (cyclomatic 61) horus_core/src/scheduling/rt_executor.rs:1417— RtExecutor::tick_node has cyclomatic complexity 61 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RtExecutor::rt_thread_main (cyclomatic 44) horus_core/src/scheduling/rt_executor.rs:1933— RtExecutor::rt_thread_main has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComputeExecutor::compute_thread_main (cyclomatic 29) horus_core/src/scheduling/compute_executor.rs:567— ComputeExecutor::compute_thread_main 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.
ComputeExecutor::process_node_result (cyclomatic 18) horus_core/src/scheduling/compute_executor.rs:793— ComputeExecutor::process_node_result 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.
horus_sys::discover::find_topics (cyclomatic 25) horus_sys/src/discover/mod.rs:317— horus_sys::discover::find_topics 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.
horus_sys::discover::macos::get_cmdline (cyclomatic 17) horus_sys/src/discover/macos.rs:65— horus_sys::discover::macos::get_cmdline 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.
AsyncExecutor::async_thread_main (cyclomatic 24) horus_core/src/scheduling/async_executor.rs:114— AsyncExecutor::async_thread_main 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.
AsyncExecutor::process_node_result (cyclomatic 18) horus_core/src/scheduling/async_executor.rs:330— AsyncExecutor::process_node_result 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.
PyTopic::recv (cyclomatic 20) horus_py/src/topic.rs:1267— PyTopic::recv 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 is NOT this file's highest cyclomatic complexity: PyTopic::backend_type (cyclomatic 81) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
PyTopic::try_send (cyclomatic 16) horus_py/src/topic.rs:1064— PyTopic::try_send 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 is NOT this file's highest cyclomatic complexity: PyTopic::backend_type (cyclomatic 81) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
Parser::parse_message (cyclomatic 19) horus_manager/src/msgspec/parse.rs:504— Parser::parse_message 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.
Parser::parse_type (cyclomatic 16) horus_manager/src/msgspec/parse.rs:392— Parser::parse_type 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.
horus_cpp::node_ffi::node_builder_build (cyclomatic 18) horus_cpp/src/node_ffi.rs:306— horus_cpp::node_ffi::node_builder_build has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
horus_cpp::action_ffi::action_server_process (cyclomatic 16) horus_cpp/src/action_ffi.rs:419— horus_cpp::action_ffi::action_server_process 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.
RtExecutor::tick_node (cognitive 136) horus_core/src/scheduling/rt_executor.rs:1417— RtExecutor::tick_node has cognitive complexity 136 (threshold 15). Drivers by points: if/else 50 (119 pts), match/switch 6 (14 pts), boolean chains 3 (nesting depth added 77). 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.
RtExecutor::rt_thread_main (cognitive 101) horus_core/src/scheduling/rt_executor.rs:1933— RtExecutor::rt_thread_main has cognitive complexity 101 (threshold 15). Drivers by points: if/else 32 (75 pts), match/switch 7 (18 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 56). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ComputeExecutor::compute_thread_main (cognitive 70) horus_core/src/scheduling/compute_executor.rs:567— ComputeExecutor::compute_thread_main has cognitive complexity 70 (threshold 15). Drivers by points: if/else 19 (54 pts), loops 7 (13 pts), boolean chains 3 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComputeExecutor::process_node_result (cognitive 29) horus_core/src/scheduling/compute_executor.rs:793— ComputeExecutor::process_node_result has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 1, match/switch 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.
AsyncExecutor::async_thread_main (cognitive 51) horus_core/src/scheduling/async_executor.rs:114— AsyncExecutor::async_thread_main has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 8 (15 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsyncExecutor::process_node_result (cognitive 29) horus_core/src/scheduling/async_executor.rs:330— AsyncExecutor::process_node_result has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 1, match/switch 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.
PyTopic::recv (cognitive 38) horus_py/src/topic.rs:1267— PyTopic::recv has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (37 pts), match/switch 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PyTopic::send (cognitive 16) horus_py/src/topic.rs:806— PyTopic::send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeRegistration::validate (cognitive 35) horus_core/src/scheduling/node_builder.rs:559— NodeRegistration::validate has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 7, match/switch 3 (5 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.
NodeRegistration::finalize (cognitive 17) horus_core/src/scheduling/node_builder.rs:502— NodeRegistration::finalize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4 (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.
TransformFrameReader::process_pending_transforms (cognitive 35) REDACTED:116— TransformFrameReader::process_pending_transforms has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 5 (8 pts), boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransformFrameReader::read_from_shm (cognitive 28) REDACTED:67— TransformFrameReader::read_from_shm has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 16). 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.
ActionServerNode::tick (cognitive 28) horus_core/src/actions/server.rs:1283— ActionServerNode::tick has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 2, match/switch 1 (nesting depth added 15). 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.
ActionServerNode::admit_goal (cognitive 17) horus_core/src/actions/server.rs:599— ActionServerNode::admit_goal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_cpp::action_ffi::action_server_process (cognitive 28) horus_cpp/src/action_ffi.rs:419— horus_cpp::action_ffi::action_server_process has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 6 (10 pts), loops 3 (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.
horus_cpp::service_ffi::service_server_process (cognitive 16) horus_cpp/src/service_ffi.rs:213— horus_cpp::service_ffi::service_server_process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (5 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TopicHeader::register_role (cognitive 25) horus_core/src/communication/topic/header.rs:858— TopicHeader::register_role has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (21 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.
TopicHeader::reap_dead_participants_now (cognitive 16) horus_core/src/communication/topic/header.rs:1240— TopicHeader::reap_dead_participants_now has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, 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.
PluginDiscovery::discover_local (cognitive 21) horus_manager/src/plugins/discovery.rs:216— PluginDiscovery::discover_local has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 1 (2 pts) (nesting depth added 15). 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.
PluginDiscovery::detect_category (cognitive 19) horus_manager/src/plugins/discovery.rs:282— PluginDiscovery::detect_category has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 7. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) horus_manager/src/commands/deps.rs:105— horus_manager/src/commands/deps.rs:105-138 | horus_manager/src/commands/deps.rs:246-312 — 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) horus_core/src/utils.rs:32— horus_core/src/utils.rs:32-59 | horus_manager/src/manifest_lint.rs:492-514 — 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) horus_manager/src/commands/action.rs:237— horus_manager/src/commands/action.rs:237-353 | horus_manager/src/commands/msg.rs:39-151 | horus_manager/src/commands/node.rs:64-333 | horus_manager/src/commands/service.rs:120-204 | horus_manager/src/commands/topic.rs:15-129 — 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) horus_py/src/depth_image.rs:138— horus_py/src/depth_image.rs:138-175 | horus_py/src/image.rs:210-263 | horus_py/src/pointcloud.rs:103-147 | horus_py/src/tensor.rs:354-416 | horus_py/src/tensor.rs:424-486 — 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 (35 corresponding lines) · ×2
Edited copy of a member (35 corresponding lines) horus_py/src/tensor.rs:251— horus_py/src/tensor.rs:251-301 | horus_py/src/tensor.rs:1186-1220 — 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) horus_cpp/src/c_api.rs:2102— horus_cpp/src/c_api.rs:2102-2136 | horus_cpp/src/c_api.rs:2143-2186 — 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 (57 corresponding lines) · ×2
Edited copy of a member (57 corresponding lines) horus_manager/src/commands/action.rs:358— horus_manager/src/commands/action.rs:358-434 | horus_manager/src/commands/service.rs:209-265 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (57 corresponding lines) horus_core/src/memory/tensor_pool.rs:1547— horus_core/src/memory/tensor_pool.rs:1547-1624 | horus_core/src/memory/tensor_pool.rs:1736-1792 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (45 corresponding lines) · ×2
Edited copy of a member (45 corresponding lines) horus_manager/src/commands/doc_extract_rust.rs:144— horus_manager/src/commands/doc_extract_rust.rs:144-189 | horus_manager/src/commands/doc_extract_rust.rs:191-235 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (45 corresponding lines) horus_core/src/scheduling/compute_executor.rs:292— horus_core/src/scheduling/compute_executor.rs:292-340 | horus_core/src/scheduling/scheduler/dispatch.rs:149-193 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) horus_core/src/actions/client.rs:857— horus_core/src/actions/client.rs:857-895 | horus_core/src/actions/client.rs:906-955 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) horus_py/src/scheduler.rs:204— horus_py/src/scheduler.rs:204-253 | horus_py/src/scheduler.rs:364-402 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) horus_core/src/types/action_chunk.rs:398— horus_core/src/types/action_chunk.rs:398-420 | horus_core/src/types/action_chunk.rs:428-447 — 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) horus_core/src/types/costmap_descriptor.rs:91— horus_core/src/types/costmap_descriptor.rs:91-110 | horus_core/src/types/costmap_descriptor.rs:137-156 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) horus_core/src/testing/shm_fault.rs:243— horus_core/src/testing/shm_fault.rs:243-267 | horus_core/src/testing/shm_fault.rs:272-296 — 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) horus_py/src/node.rs:190— horus_py/src/node.rs:190-214 | horus_py/src/node.rs:217-241 — 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 (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) horus_manager/src/dependency_resolver.rs:118— horus_manager/src/dependency_resolver.rs:118-149 | horus_manager/src/dependency_resolver.rs:152-184 — 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) horus_core/src/memory/tensor_pool.rs:1509— horus_core/src/memory/tensor_pool.rs:1509-1540 | horus_core/src/memory/tensor_pool.rs:1695-1728 — 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 (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) horus_cpp/src/c_api.rs:119— horus_cpp/src/c_api.rs:119-134 | horus_cpp/src/c_api.rs:239-249 — 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) horus_manager/src/commands/doctor.rs:1805— horus_manager/src/commands/doctor.rs:1805-1817 | horus_manager/src/commands/run/run_python.rs:144-154 — 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 copies of one member (4 members, 14+ corresponding lines) · ×2
Edited copies of one member (4 members, 14+ corresponding lines) horus_types/src/diagnostics.rs:58— horus_types/src/diagnostics.rs:58-75 | horus_types/src/diagnostics.rs:142-157 | horus_types/src/diagnostics.rs:234-249 | horus_types/src/diagnostics.rs:433-446 — 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.
Edited copies of one member (4 members, 14+ corresponding lines) horus_py/src/tensor.rs:628— horus_py/src/tensor.rs:628-642 | horus_py/src/tensor.rs:645-660 | horus_py/src/tensor.rs:761-775 | horus_py/src/tensor.rs:778-791 — 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 copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) horus_manager/src/discovery/nodes.rs:286— horus_manager/src/discovery/nodes.rs:286-291 | horus_manager/src/urdf.rs:91-96 — 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) horus_core/src/types/costmap_descriptor.rs:281— horus_core/src/types/costmap_descriptor.rs:281-286 | horus_py/src/messages.rs:1285-1290 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) horus_core/src/types/costmap_descriptor.rs:275— horus_core/src/types/costmap_descriptor.rs:275-278 | horus_types/src/time.rs:182-185 — 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) horus_py/src/messages.rs:7443— horus_py/src/messages.rs:7443-7451 | horus_types/src/diagnostics.rs:195-198 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (36 lines × 2) horus_core/src/memory/costmap.rs:383— horus_core/src/memory/costmap.rs:383-418 | horus_core/src/memory/occupancy_grid.rs:197-232 — before extracting anything, compare `horus_core/src/memory/costmap.rs` and `horus_core/src/memory/occupancy_grid.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 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 (36 lines × 2) horus_core/src/scheduling/async_executor.rs:337— horus_core/src/scheduling/async_executor.rs:337-372 | horus_core/src/scheduling/compute_executor.rs:800-835 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:337` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) horus_manager/src/commands/pkg.rs:190— horus_manager/src/commands/pkg.rs:190-220 | horus_manager/src/commands/pkg.rs:290-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) horus_core/src/memory/tensor_pool.rs:485— horus_core/src/memory/tensor_pool.rs:485-515 | horus_core/src/memory/tensor_pool.rs:772-802 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/memory/tensor_pool.rs:485` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) horus_manager/src/commands/doc_extract_rust.rs:785— horus_manager/src/commands/doc_extract_rust.rs:785-814 | horus_manager/src/commands/doc_extract_rust.rs:828-857 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_rust.rs:785` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) horus_manager/src/registry/install.rs:1517— horus_manager/src/registry/install.rs:1517-1546 | horus_manager/src/registry/install.rs:1754-1783 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:1517` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23–28 lines × 2) horus_manager/src/registry/install.rs:695— horus_manager/src/registry/install.rs:695-722 | horus_manager/src/registry/install.rs:1128-1150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:695` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23–28 lines × 2) horus_manager/src/registry/install.rs:851— horus_manager/src/registry/install.rs:851-878 | horus_manager/src/registry/install.rs:1266-1288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:851` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (24 lines × 2) horus_core/src/actions/client.rs:872— horus_core/src/actions/client.rs:872-895 | horus_core/src/actions/client.rs:932-955 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/actions/client.rs:872` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) horus_manager/src/commands/run/install.rs:1374— horus_manager/src/commands/run/install.rs:1374-1397 | horus_manager/src/commands/run/install.rs:1816-1839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/install.rs:1374` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) horus_manager/src/commands/pkg.rs:1291— horus_manager/src/commands/pkg.rs:1291-1313 | horus_manager/src/commands/pkg.rs:1398-1420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1398` it begins part-way through the construct above it, so those exact lines 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) horus_net/src/wire.rs:448— horus_net/src/wire.rs:448-470 | horus_net/src/wire.rs:498-520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_net/src/wire.rs:448` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_net/src/wire.rs:521` calls `encode` and `horus_net/src/wire.rs:471` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) horus_core/src/scheduling/fault_tolerance/failure_policy.rs:190— horus_core/src/scheduling/fault_tolerance/failure_policy.rs:190-210 | horus_core/src/scheduling/fault_tolerance/failure_policy.rs:418-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (21 lines × 2) horus_manager/src/commands/run/run_rust.rs:385— horus_manager/src/commands/run/run_rust.rs:385-405 | horus_manager/src/commands/run/run_rust.rs:986-1006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/run_rust.rs:385` it does not close everything it opens, so those exact lines 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 × 3) horus_manager/src/commands/topic.rs:797— horus_manager/src/commands/topic.rs:797-815 | horus_manager/src/commands/topic.rs:1009-1027 | horus_manager/src/commands/topic.rs:1166-1183 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18–19 lines × 3) horus_py/src/depth_image.rs:158— horus_py/src/depth_image.rs:158-175 | horus_py/src/image.rs:245-263 | horus_py/src/pointcloud.rs:130-147 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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 `horus_py/src/depth_image.rs:158` it begins part-way through the construct above it, so those exact lines 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) horus_sys/src/fs/mod.rs:357— horus_sys/src/fs/mod.rs:357-377 | horus_sys/src/shm/mod.rs:420-435 — 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 `horus_sys/src/fs/mod.rs:357` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) horus_core/src/memory/tensor_pool.rs:1568— horus_core/src/memory/tensor_pool.rs:1568-1584 | horus_core/src/memory/tensor_pool.rs:1757-1772 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/memory/tensor_pool.rs:1568` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) horus_manager/src/commands/deps.rs:113— horus_manager/src/commands/deps.rs:113-127 | horus_manager/src/commands/deps.rs:255-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/deps.rs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) horus_manager/src/commands/upgrade.rs:937— horus_manager/src/commands/upgrade.rs:937-951 | horus_manager/src/source_resolver.rs:965-978 — 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 `horus_manager/src/commands/upgrade.rs:937` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_manager/src/source_resolver.rs:964` calls `user_agent` and `horus_manager/src/commands/upgrade.rs:936` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–14 lines × 2) horus_core/src/types/dtype.rs:200— horus_core/src/types/dtype.rs:200-212 | horus_py/src/tensor_convert.rs:40-53 — 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 `horus_py/src/tensor_convert.rs:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) horus_manager/src/registry/publish.rs:876— horus_manager/src/registry/publish.rs:876-888 | horus_manager/src/registry/publish.rs:1118-1131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/publish.rs:876` 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 (10–12 lines × 2) horus_core/src/memory/tensor_pool.rs:417— horus_core/src/memory/tensor_pool.rs:417-428 | horus_core/src/memory/tensor_pool.rs:720-729 — both copies are in the same file, so extract the 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–12 lines × 2) horus_core/src/scheduling/async_executor.rs:305— horus_core/src/scheduling/async_executor.rs:305-314 | horus_core/src/scheduling/compute_executor.rs:718-729 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:305` it begins part-way through the construct above it, so those exact lines 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) horus_core/src/scheduling/scheduler/mod.rs:2971— horus_core/src/scheduling/scheduler/mod.rs:2971-2981 | horus_core/src/scheduling/scheduler/mod.rs:4743-4754 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/scheduling/scheduler/mod.rs:2971` it does not close everything it opens, so those exact lines 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) horus_core/src/types/image_encoding.rs:140— horus_core/src/types/image_encoding.rs:140-150 | horus_py/src/image.rs:46-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/image.rs:46` it begins part-way through the construct above it, so those 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–12 lines × 2) horus_manager/src/commands/check.rs:376— horus_manager/src/commands/check.rs:376-387 | horus_manager/src/commands/check.rs:431-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/check.rs:376` it does not close everything it opens, so those 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–12 lines × 2) horus_manager/src/commands/record.rs:809— horus_manager/src/commands/record.rs:809-820 | horus_manager/src/commands/record.rs:932-939 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/record.rs:809` it does not close everything it opens, so those 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, `horus_manager/src/commands/record.rs:942` calls `Err` and `horus_manager/src/commands/record.rs:821` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) horus_core/src/communication/topic/header.rs:1833— horus_core/src/communication/topic/header.rs:1833-1853 | horus_core/src/communication/topic/header.rs:2152-2163 | horus_core/src/communication/topic/header.rs:2184-2194 — 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 `horus_core/src/communication/topic/header.rs:1833` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) horus_manager/src/registry/install.rs:2198— horus_manager/src/registry/install.rs:2198-2208 | horus_manager/src/registry/install.rs:2471-2481 | horus_manager/src/registry/install.rs:2530-2540 — 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. 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–8 lines × 2) horus_manager/src/commands/doc_extract_rust.rs:397— horus_manager/src/commands/doc_extract_rust.rs:397-404 | horus_manager/src/commands/doc_extract_rust.rs:437-443 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc_extract_rust.rs:397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) horus_sys/src/discover/mod.rs:214— horus_sys/src/discover/mod.rs:214-221 | horus_sys/src/shm/mod.rs:1163-1169 — 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 `horus_sys/src/discover/mod.rs:214` it does not close everything it opens, so those exact lines 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) horus_manager/src/commands/doc_extract_rust.rs:348— horus_manager/src/commands/doc_extract_rust.rs:348-352 | horus_manager/src/commands/doc_extract_rust.rs:393-397 | horus_manager/src/commands/doc_extract_rust.rs:433-437 — 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 `horus_manager/src/commands/doc_extract_rust.rs:348` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/pkg.rs:1280— horus_manager/src/commands/pkg.rs:1280-1284 | horus_manager/src/commands/pkg.rs:1389-1393 | horus_manager/src/commands/plugin.rs:494-498 — 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 `horus_manager/src/commands/pkg.rs:1280` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: NodeRegistration (LCOM4 6) horus_core/src/scheduling/node_builder.rs:103— NodeRegistration's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PyNodeInfo (LCOM4 4) horus_py/src/node.rs:90— PyNodeInfo's methods fall into 4 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 4 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.
Unfinished stub — panics or fails with a "not implemented" message horus_sys/src/rt/macos.rs:56— `set_realtime_priority`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it.
Unfinished stub — panics or fails with a "not implemented" message horus_sys/src/rt/macos.rs:75— `lock_memory`'s whole body panics or returns an error whose message says it isn't finished — generated scaffolding that was never completed. Implement it or remove it.
Unfinished stub — panics or fails with a "not implemented" message horus_sys/src/rt/macos.rs:56— `set_realtime_priority`'s whole body panics or returns an error whose message says it isn't finished — a not-implemented stub in ordinary clothes. Implement it or remove it.
Unfinished stub — panics or fails with a "not implemented" message horus_sys/src/rt/macos.rs:75— `lock_memory`'s whole body panics or returns an error whose message says it isn't finished — a not-implemented stub in ordinary clothes. Implement it or remove it.
CI formatting step cannot fail REDACTED:124— `for tool in cargo python3 cmake g++ clang-format clang-tidy; do` invokes clang-format in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--dry-run --Werror` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
CI formatting step cannot fail REDACTED:184— `for tool in cargo rustfmt cargo-clippy python3 cmake g++ clang-format; do` invokes clang-format in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--dry-run --Werror` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
NodeRegistration::validate (cyclomatic 35) horus_core/src/scheduling/node_builder.rs:559— NodeRegistration::validate 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.
EventExecutor::watcher_thread (cyclomatic 30) horus_core/src/scheduling/event_executor.rs:284— EventExecutor::watcher_thread 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.
Lexer::tokenize (cyclomatic 27) horus_manager/src/msgspec/parse.rs:89— Lexer::tokenize 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.
RuntimeParams::validate_value (cyclomatic 24) horus_core/src/params.rs:448— RuntimeParams::validate_value 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.
RtReport::generate (cyclomatic 24) horus_core/src/scheduling/rt_report.rs:84— RtReport::generate has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RtConfig::apply (cyclomatic 23) horus_core/src/core/rt_config.rs:221— RtConfig::apply 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.
HorusManifest::validate_issues (cyclomatic 21) horus_manager/src/manifest.rs:1442— HorusManifest::validate_issues 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.
ReadyDispatch::run (cyclomatic 20) horus_core/src/scheduling/scheduler/dispatch.rs:366— ReadyDispatch::run 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.
NodeDef::parse (cyclomatic 20) horus_macros/src/node.rs:89— NodeDef::parse 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.
horus_macros::node::impl_node_macro (cyclomatic 20) horus_macros/src/node.rs:388— horus_macros::node::impl_node_macro 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.
generator._generate_rust_code (cyclomatic 20) horus_py/horus/msggen/generator.py:167— generator._generate_rust_code 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.
PluginDiscovery::detect_category (cyclomatic 19) horus_manager/src/plugins/discovery.rs:282— PluginDiscovery::detect_category 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.
PresenceReceiver::handle_broadcast (cyclomatic 18) horus_net/src/presence.rs:147— PresenceReceiver::handle_broadcast 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.
TopicHeader::register_role (cyclomatic 17) horus_core/src/communication/topic/header.rs:858— TopicHeader::register_role 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.
builder.build_messages (cyclomatic 17) REDACTED:99— builder.build_messages 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.
Extractor._build_function (cyclomatic 17) horus_manager/src/commands/python_extractor.py:132— Extractor._build_function 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.
RingTopic::negotiate_shm_header (cyclomatic 16) horus_core/src/communication/topic/mod.rs:1179— RingTopic::negotiate_shm_header 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.
ShmFanoutRing::validate_meta (cyclomatic 16) horus_core/src/communication/topic/shm_fanout.rs:680— ShmFanoutRing::validate_meta 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.
DependencyGraph::build (cyclomatic 16) horus_core/src/scheduling/dependency_graph.rs:53— DependencyGraph::build 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.
Node._parse_topics (cyclomatic 16) horus_py/horus/__init__.py:640— Node._parse_topics 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.
autopilot_triage.main (cyclomatic 16) .github/scripts/autopilot_triage.py:268— autopilot_triage.main 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.
Extractor.visit_ClassDef (cyclomatic 16) horus_manager/src/commands/python_extractor.py:53— Extractor.visit_ClassDef 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.
EventExecutor::watcher_thread (cognitive 78) horus_core/src/scheduling/event_executor.rs:284— EventExecutor::watcher_thread has cognitive complexity 78 (threshold 15). Drivers by points: if/else 23 (68 pts), boolean chains 4, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lexer::tokenize (cognitive 66) horus_manager/src/msgspec/parse.rs:89— Lexer::tokenize has cognitive complexity 66 (threshold 15). Drivers by points: if/else 17 (42 pts), loops 7 (18 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeParams::validate_value (cognitive 47) horus_core/src/params.rs:448— RuntimeParams::validate_value has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 2 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RtConfig::apply (cognitive 42) horus_core/src/core/rt_config.rs:221— RtConfig::apply has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 2 (5 pts), boolean chains 3 (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.
ReadyDispatch::run (cognitive 41) horus_core/src/scheduling/scheduler/dispatch.rs:366— ReadyDispatch::run has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 6 (11 pts), match/switch 3 (9 pts), boolean chains 2 (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.
NodeDef::parse (cognitive 39) horus_macros/src/node.rs:89— NodeDef::parse has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (35 pts), match/switch 1 (3 pts), loops 1 (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.
ShmRegion::new (cognitive 38) horus_sys/src/shm/macos.rs:162— ShmRegion::new has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (37 pts), loops 1 (nesting depth added 20). 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.
horus_macros::node::impl_node_macro (cognitive 34) horus_macros/src/node.rs:388— horus_macros::node::impl_node_macro has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (22 pts), loops 6 (12 pts) (nesting depth added 8). 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.
NodePresence::read_all (cognitive 32) horus_core/src/core/presence.rs:521— NodePresence::read_all has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (21 pts), match/switch 2 (9 pts), loops 1 (2 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.
Extractor.visit_ClassDef (cognitive 30) horus_manager/src/commands/python_extractor.py:53— Extractor.visit_ClassDef has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 4 (8 pts), loops 4 (8 pts), boolean chains 2 (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.
DependencyGraph::build (cognitive 29) horus_core/src/scheduling/dependency_graph.rs:53— DependencyGraph::build has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 8 (14 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeCapabilities::detect_numa_topology (cognitive 29) horus_core/src/scheduling/rt.rs:579— RuntimeCapabilities::detect_numa_topology has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (26 pts), loops 1 (3 pts) (nesting depth added 21). 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.
Scheduler.run (cognitive 29) horus_py/horus/__init__.py:1283— Scheduler.run has cognitive complexity 29 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 6 (9 pts), loops 4 (9 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RtReport::generate (cognitive 25) horus_core/src/scheduling/rt_report.rs:84— RtReport::generate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 4, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HorusManifest::validate_issues (cognitive 25) horus_manager/src/manifest.rs:1442— HorusManifest::validate_issues has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
DriverConfig::from_manifest (cognitive 24) horus_manager/src/commands/run/features.rs:123— DriverConfig::from_manifest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (9 pts), match/switch 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.
generator._generate_rust_code (cognitive 24) horus_py/horus/msggen/generator.py:167— generator._generate_rust_code has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 6, boolean chains 5, 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.
LaunchSession::read_all (cognitive 23) horus_manager/src/commands/launch.rs:284— LaunchSession::read_all has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 1 (2 pts) (nesting depth added 15). 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.
Extractor.visit_Module (cognitive 23) horus_manager/src/commands/python_extractor.py:24— Extractor.visit_Module has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 15). 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.
SharedLogBuffer::get_since (cognitive 22) horus_core/src/core/log_buffer.rs:440— SharedLogBuffer::get_since has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DepthImage::depth_statistics (cognitive 22) horus_core/src/memory/depth_image.rs:203— DepthImage::depth_statistics has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PresenceReceiver::handle_broadcast (cognitive 22) horus_net/src/presence.rs:147— PresenceReceiver::handle_broadcast has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 1, 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.
Extractor._build_function (cognitive 22) horus_manager/src/commands/python_extractor.py:132— Extractor._build_function has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 6 (7 pts), loops 3, 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.
RecordingManager::list_sessions (cognitive 21) horus_core/src/scheduling/record_replay.rs:1108— RecordingManager::list_sessions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 2 (4 pts) (nesting depth added 15). 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.
CargoPackage::from_string (cognitive 21) horus_manager/src/commands/run/deps.rs:73— CargoPackage::from_string has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (21 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.
Node._parse_topics (cognitive 21) horus_py/horus/__init__.py:640— Node._parse_topics has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (4 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.
builder.build_messages (cognitive 21) REDACTED:99— builder.build_messages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 2 (3 pts), boolean chains 1, error handling 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.
autopilot_triage.main (cognitive 21) .github/scripts/autopilot_triage.py:268— autopilot_triage.main has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 6 (10 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.
ReplayDebugger::step_internal (cognitive 20) horus_core/src/scheduling/record_replay.rs:1931— ReplayDebugger::step_internal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (3 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DependencyResolver::resolve (cognitive 20) horus_manager/src/dependency_resolver.rs:213— DependencyResolver::resolve has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 5 (9 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.
PinContext::load (cognitive 18) horus_manager/src/commands/run/install.rs:46— PinContext::load has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 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.
DependencySpec::parse (cognitive 18) horus_manager/src/dependency_resolver.rs:55— DependencySpec::parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3 (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.
EstopBroadcaster::tick (cognitive 18) horus_net/src/estop.rs:541— EstopBroadcaster::tick has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (4 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.
python_extractor._extract_examples (cognitive 18) horus_manager/src/commands/python_extractor.py:225— python_extractor._extract_examples has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, 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.
NodeRecorder::end_tick (cognitive 17) horus_core/src/scheduling/record_replay.rs:765— NodeRecorder::end_tick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 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.
Reassembler::feed (cognitive 17) horus_net/src/fragment.rs:197— Reassembler::feed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
horus_py::tensor::parse_shape_args (cognitive 17) horus_py/src/tensor.rs:1118— horus_py::tensor::parse_shape_args has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), 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.
GenericMessage::log_summary (cognitive 17) horus_types/src/generic.rs:271— GenericMessage::log_summary has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (17 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.
Node.send (cognitive 17) horus_py/horus/__init__.py:902— Node.send has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
horus_cpp_macros::cpp_gen::generate_method_decl (cognitive 16) horus_cpp_macros/src/cpp_gen.rs:171— horus_cpp_macros::cpp_gen::generate_method_decl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ShmRingWriter::open_path (cognitive 16) horus_net/src/shm_writer.rs:77— ShmRingWriter::open_path has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 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.
Near-duplicate member pair (212 shared lines) horus_manager/src/registry/install.rs:404— horus_manager/src/registry/install.rs:404-952 | horus_manager/src/registry/install.rs:964-1339 — These two members are variants of one another: 212 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 (95 shared lines) horus_manager/src/registry/install.rs:1500— horus_manager/src/registry/install.rs:1500-1723 | horus_manager/src/registry/install.rs:1730-1994 — These two members are variants of one another: 95 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 (72 shared lines) horus_core/src/memory/tensor_pool.rs:416— horus_core/src/memory/tensor_pool.rs:416-515 | horus_core/src/memory/tensor_pool.rs:719-802 — These two members are variants of one another: 72 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 (66 shared lines) horus_core/src/drivers/mod.rs:152— horus_core/src/drivers/mod.rs:152-306 | horus_core/src/drivers/mod.rs:352-446 — These two members are variants of one another: 66 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 (64 shared lines) horus_core/src/communication/topic/dispatch.rs:2028— horus_core/src/communication/topic/dispatch.rs:2028-2111 | horus_core/src/communication/topic/dispatch.rs:2446-2536 — These two members are variants of one another: 64 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 (16 shared lines) horus_py/src/depth_image.rs:71— horus_py/src/depth_image.rs:71-126 | horus_py/src/image.rs:115-170 — These two members are variants of one another: 16 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 (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) horus_manager/src/commands/action.rs:447— horus_manager/src/commands/action.rs:447-629 | horus_manager/src/commands/blackbox.rs:349-417 | horus_manager/src/commands/launch.rs:375-919 | horus_manager/src/commands/log.rs:292-345 | horus_manager/src/commands/service.rs:361-539 | horus_manager/src/commands/topic.rs:160-304 | horus_manager/src/commands/topic.rs:1006-1158 | horus_manager/src/commands/topic.rs:1163-1316 | horus_manager/src/commands/topic.rs:1324-1418 — 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) horus_manager/src/commands/run/run_cpp.rs:407— horus_manager/src/commands/run/run_cpp.rs:407-460 | horus_manager/src/commands/run/run_cpp.rs:530-614 — 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) horus_manager/src/commands/run/install.rs:1402— horus_manager/src/commands/run/install.rs:1402-1467 | horus_manager/src/registry/install.rs:2514-2587 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (84 corresponding lines) · ×1
Edited copy of a member (84 corresponding lines) horus_core/src/memory/tensor_pool.rs:1947— horus_core/src/memory/tensor_pool.rs:1947-2032 | horus_core/src/memory/tensor_pool.rs:2042-2125 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) horus_manager/src/commands/proxy.rs:1021— horus_manager/src/commands/proxy.rs:1021-1071 | horus_manager/src/commands/proxy.rs:1089-1138 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) horus_core/src/params.rs:265— horus_core/src/params.rs:265-314 | horus_core/src/params.rs:372-412 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 38+ corresponding lines) · ×1
Edited copies of one member (3 members, 38+ corresponding lines) horus_manager/src/commands/doc_extract_rust.rs:345— horus_manager/src/commands/doc_extract_rust.rs:345-387 | horus_manager/src/commands/doc_extract_rust.rs:390-427 | horus_manager/src/commands/doc_extract_rust.rs:430-467 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 38 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 (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) horus_sys/src/shm/fallback.rs:194— horus_sys/src/shm/fallback.rs:194-248 | horus_sys/src/shm/linux.rs:285-339 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) horus_sys/src/shm/fallback.rs:30— horus_sys/src/shm/fallback.rs:30-71 | horus_sys/src/shm/linux.rs:48-92 — 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 copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) horus_cpp_macros/src/cxx_gen.rs:154— horus_cpp_macros/src/cxx_gen.rs:154-191 | horus_cpp_macros/src/cxx_gen.rs:198-233 — 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) horus_manager/src/commands/doc_extract_rust.rs:544— horus_manager/src/commands/doc_extract_rust.rs:544-572 | horus_manager/src/commands/doc_extract_rust.rs:577-607 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) horus_manager/src/commands/deps.rs:59— horus_manager/src/commands/deps.rs:59-102 | horus_manager/src/commands/deps.rs:160-194 | horus_manager/src/commands/deps.rs:338-373 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) horus_sys/src/fs/mod.rs:113— horus_sys/src/fs/mod.rs:113-149 | horus_sys/src/fs/mod.rs:152-188 | horus_sys/src/fs/mod.rs:192-229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) horus_core/src/core/hlog_rt.rs:186— horus_core/src/core/hlog_rt.rs:186-216 | horus_core/src/scheduling/rt_executor.rs:195-225 — 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 copies of one member (3 members, 36+ corresponding lines) · ×1
Edited copies of one member (3 members, 36+ corresponding lines) horus_manager/src/commands/run/install.rs:1362— horus_manager/src/commands/run/install.rs:1362-1397 | horus_manager/src/commands/run/install.rs:1804-1839 | horus_manager/src/registry/install.rs:2342-2378 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) horus_macros/src/node.rs:212— horus_macros/src/node.rs:212-242 | horus_macros/src/node.rs:244-274 | horus_macros/src/node.rs:276-311 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 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 (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) horus_manager/src/commands/doc_extract_cpp.rs:696— horus_manager/src/commands/doc_extract_cpp.rs:696-722 | horus_manager/src/commands/doc_extract_rust.rs:1110-1137 — 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) horus_manager/src/commands/fmt.rs:32— horus_manager/src/commands/fmt.rs:32-59 | horus_manager/src/commands/lint.rs:17-44 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) horus_sys/src/fs/mod.rs:352— horus_sys/src/fs/mod.rs:352-382 | horus_sys/src/shm/mod.rs:413-445 | horus_sys/src/shm/mod.rs:452-480 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 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, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) horus_cpp/src/c_api.rs:1474— horus_cpp/src/c_api.rs:1474-1491 | horus_cpp/src/c_api.rs:1987-2008 | horus_cpp/src/c_api.rs:2051-2073 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) horus_sys/src/platform/mod.rs:208— horus_sys/src/platform/mod.rs:208-228 | horus_sys/src/platform/mod.rs:243-262 | horus_sys/src/platform/mod.rs:268-287 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 19+ corresponding lines) · ×1
Edited copies of one member (6 members, 19+ corresponding lines) horus_manager/src/registry/publish.rs:980— horus_manager/src/registry/publish.rs:980-1003 | horus_manager/src/registry/publish.rs:1035-1058 | horus_manager/src/registry/publish.rs:1113-1136 | horus_manager/src/registry/publish.rs:1144-1165 | horus_manager/src/registry/publish.rs:1212-1230 | horus_manager/src/registry/publish.rs:1232-1250 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) horus_core/src/communication/topic/mod.rs:4892— horus_core/src/communication/topic/mod.rs:4892-4910 | horus_core/src/communication/topic/mod.rs:4959-4977 | horus_core/src/communication/topic/mod.rs:5026-5044 — 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 (4 members, 1+ corresponding lines) · ×1
Edited copies of one member (4 members, 1+ corresponding lines) horus_core/src/memory/depth_image.rs:44— horus_core/src/memory/depth_image.rs:44-44 | horus_core/src/memory/image.rs:50-50 | horus_core/src/memory/occupancy_grid.rs:45-45 | horus_core/src/memory/pointcloud.rs:50-50 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) horus_manager/src/commands/node.rs:584— horus_manager/src/commands/node.rs:584-616 | horus_manager/src/commands/node.rs:619-644 | horus_manager/src/commands/node.rs:647-667 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 14+ corresponding lines) · ×1
Edited copies of one member (6 members, 14+ corresponding lines) horus_cpp/src/c_api.rs:1280— horus_cpp/src/c_api.rs:1280-1296 | horus_cpp/src/c_api.rs:1304-1317 | horus_cpp/src/c_api.rs:1325-1341 | horus_cpp/src/c_api.rs:1349-1362 | horus_cpp/src/c_api.rs:1370-1386 | horus_cpp/src/c_api.rs:1394-1407 — These 6 members are one piece of code written 6 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 6 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) horus_cpp/src/c_api.rs:540— horus_cpp/src/c_api.rs:540-552 | horus_cpp/src/c_api.rs:588-600 | horus_cpp/src/c_api.rs:922-934 | horus_cpp/src/c_api.rs:967-979 — 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 copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) horus_py/src/scheduler.rs:501— horus_py/src/scheduler.rs:501-520 | horus_py/src/scheduler.rs:526-544 — 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 copies of one member (8 members, 18+ corresponding lines) · ×1
Edited copies of one member (8 members, 18+ corresponding lines) horus_sys/src/discover/mod.rs:43— horus_sys/src/discover/mod.rs:43-61 | horus_sys/src/discover/mod.rs:99-116 | horus_sys/src/process/mod.rs:270-288 | horus_sys/src/rt/mod.rs:686-703 | horus_sys/src/rt/mod.rs:706-723 | horus_sys/src/rt/mod.rs:734-752 | horus_sys/src/rt/mod.rs:759-776 | horus_sys/src/shm/mod.rs:1377-1397 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) horus_sys/src/shm/fallback.rs:252— horus_sys/src/shm/fallback.rs:252-281 | horus_sys/src/shm/linux.rs:343-390 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) horus_py/src/image.rs:439— horus_py/src/image.rs:439-444 | horus_py/src/image.rs:451-456 | horus_py/src/image.rs:463-468 | horus_py/src/image.rs:475-480 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 5+ corresponding lines) · ×1
Edited copies of one member (4 members, 5+ corresponding lines) horus_py/src/messages.rs:240— horus_py/src/messages.rs:240-244 | horus_py/src/messages.rs:1582-1586 | horus_py/src/messages.rs:1661-1665 | horus_py/src/messages.rs:1763-1768 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) horus_py/src/scheduler.rs:1396— horus_py/src/scheduler.rs:1396-1403 | horus_py/src/scheduler.rs:1411-1418 | horus_py/src/scheduler.rs:1451-1458 — 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 (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) horus_core/src/communication/topic/mod.rs:4913— horus_core/src/communication/topic/mod.rs:4913-4934 | horus_core/src/communication/topic/mod.rs:4980-5001 | horus_core/src/communication/topic/mod.rs:5047-5068 — 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, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) horus_manager/src/registry/helpers.rs:4— horus_manager/src/registry/helpers.rs:4-14 | horus_manager/src/registry/helpers.rs:16-26 | horus_manager/src/system_deps.rs:490-500 | horus_manager/src/system_deps.rs:502-512 — 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 copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) horus_py/src/perception.rs:402— horus_py/src/perception.rs:402-404 | horus_types/src/math.rs:249-251 — 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 (70–77 lines × 2) horus_manager/src/registry/install.rs:728— horus_manager/src/registry/install.rs:728-804 | horus_manager/src/registry/install.rs:1154-1223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:728` 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 (45–46 lines × 2) horus_manager/src/registry/install.rs:536— horus_manager/src/registry/install.rs:536-581 | horus_manager/src/registry/install.rs:1012-1056 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:536` 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 (44–46 lines × 2) horus_sys/src/shm/fallback.rs:205— horus_sys/src/shm/fallback.rs:205-248 | horus_sys/src/shm/linux.rs:294-339 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_sys/src/shm/fallback.rs:205` 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–45 lines × 2) horus_py/src/tensor.rs:257— horus_py/src/tensor.rs:257-301 | horus_py/src/tensor.rs:1189-1220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_py/src/tensor.rs:257` 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 (41–42 lines × 2) horus_manager/src/registry/helpers.rs:108— horus_manager/src/registry/helpers.rs:108-149 | horus_manager/src/registry/helpers.rs:171-211 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:108` 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 (37–41 lines × 2) horus_manager/src/registry/install.rs:806— horus_manager/src/registry/install.rs:806-846 | horus_manager/src/registry/install.rs:1225-1261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:806` it begins part-way through the construct above it, so those exact lines 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–40 lines × 3) horus_core/src/communication/topic/mod.rs:4496— horus_core/src/communication/topic/mod.rs:4496-4535 | horus_core/src/communication/topic/mod.rs:4575-4612 | horus_core/src/communication/topic/mod.rs:4622-4657 — 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 `horus_core/src/communication/topic/mod.rs:4496` 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 (39–40 lines × 2) horus_manager/src/commands/run/run_rust.rs:326— horus_manager/src/commands/run/run_rust.rs:326-365 | horus_manager/src/commands/run/run_rust.rs:417-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (38–39 lines × 2) horus_core/src/drivers/mod.rs:207— horus_core/src/drivers/mod.rs:207-245 | horus_core/src/drivers/mod.rs:390-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/drivers/mod.rs:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (37–38 lines × 2) horus_manager/src/commands/topic.rs:1009— horus_manager/src/commands/topic.rs:1009-1046 | horus_manager/src/commands/topic.rs:1166-1202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/topic.rs:1009` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (47 lines × 2) horus_core/src/memory/tensor_pool.rs:1982— horus_core/src/memory/tensor_pool.rs:1982-2028 | horus_core/src/memory/tensor_pool.rs:2075-2121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/memory/tensor_pool.rs:1982` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28–35 lines × 3) horus_core/src/communication/topic/dispatch.rs:1985— horus_core/src/communication/topic/dispatch.rs:1985-2019 | horus_core/src/communication/topic/dispatch.rs:2084-2111 | horus_core/src/communication/topic/dispatch.rs:2502-2536 — 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 `horus_core/src/communication/topic/dispatch.rs:1985` 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 (27–35 lines × 2) horus_core/src/communication/topic/dispatch.rs:1487— horus_core/src/communication/topic/dispatch.rs:1487-1521 | horus_core/src/communication/topic/dispatch.rs:1821-1847 — both copies are in the same file, so extract the 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 (29–34 lines × 4) horus_core/src/scheduling/async_executor.rs:382— horus_core/src/scheduling/async_executor.rs:382-410 | horus_core/src/scheduling/compute_executor.rs:845-873 | horus_core/src/scheduling/event_executor.rs:494-527 | horus_core/src/scheduling/rt_executor.rs:1843-1873 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:382` it begins part-way through the construct above it, so those 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 (31–32 lines × 2) horus_core/src/memory/tensor_pool.rs:436— horus_core/src/memory/tensor_pool.rs:436-467 | horus_core/src/memory/tensor_pool.rs:740-770 — both copies are in the same file, so extract the 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 (29–30 lines × 2) horus_core/src/communication/topic/dispatch.rs:2237— horus_core/src/communication/topic/dispatch.rs:2237-2266 | horus_core/src/communication/topic/dispatch.rs:2320-2348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:2237` it begins part-way through the construct above it, so those 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 (45 lines × 2) horus_manager/src/commands/migrate.rs:235— horus_manager/src/commands/migrate.rs:235-279 | horus_manager/src/commands/migrate.rs:282-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `t` to `&toml_edit::InlineTable` in one and `&toml_edit::Table` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11–29 lines × 2) horus_core/src/communication/topic/dispatch.rs:1101— horus_core/src/communication/topic/dispatch.rs:1101-1129 | horus_core/src/communication/topic/dispatch.rs:1146-1156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_core/src/communication/topic/dispatch.rs:1129` calls `release` and `horus_core/src/communication/topic/dispatch.rs:1156` 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–29 lines × 2) horus_core/src/communication/topic/dispatch.rs:2052— horus_core/src/communication/topic/dispatch.rs:2052-2080 | horus_core/src/communication/topic/dispatch.rs:2475-2494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:2052` it begins part-way through the construct above it, so those exact lines 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–27 lines × 3) horus_core/src/communication/topic/dispatch.rs:712— horus_core/src/communication/topic/dispatch.rs:712-724 | horus_core/src/communication/topic/dispatch.rs:2237-2256 | horus_core/src/communication/topic/dispatch.rs:2320-2346 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_core/src/communication/topic/dispatch.rs:2210` calls `wrapping_sub` and `horus_core/src/communication/topic/dispatch.rs:711` 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 (27 lines × 3) horus_manager/src/registry/install.rs:1675— horus_manager/src/registry/install.rs:1675-1701 | horus_manager/src/registry/install.rs:1944-1970 | horus_manager/src/registry/install.rs:2210-2236 — 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 (27 lines × 2) horus_manager/src/commands/run/run_rust.rs:927— horus_manager/src/commands/run/run_rust.rs:927-953 | horus_manager/src/commands/run/run_rust.rs:1029-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.
Duplicated block (24–26 lines × 2) horus_core/src/memory/tensor_pool.rs:1952— horus_core/src/memory/tensor_pool.rs:1952-1977 | horus_core/src/memory/tensor_pool.rs:2047-2070 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/memory/tensor_pool.rs:1952` 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 (26 lines × 2) horus_sys/src/discover/macos.rs:236— horus_sys/src/discover/macos.rs:236-261 | horus_sys/src/discover/macos.rs:280-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/discover/macos.rs:236` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–26 lines × 3) horus_sys/src/discover/windows.rs:189— horus_sys/src/discover/windows.rs:189-214 | horus_sys/src/discover/windows.rs:251-276 | horus_sys/src/process/mod.rs:435-438 — 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 `horus_sys/src/discover/windows.rs:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `horus_sys/src/process/mod.rs:438` calls `GetProcessTimes`, `CloseHandle` and `horus_sys/src/discover/windows.rs:214` 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 (18–25 lines × 2) horus_core/src/communication/topic/header.rs:978— horus_core/src/communication/topic/header.rs:978-1002 | horus_core/src/communication/topic/header.rs:1257-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/header.rs:978` it begins part-way through the construct above it, so those exact lines 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–25 lines × 3) horus_core/src/drivers/mod.rs:157— horus_core/src/drivers/mod.rs:157-181 | horus_core/src/drivers/mod.rs:322-324 | horus_core/src/drivers/mod.rs:357-379 — 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. 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, `horus_core/src/drivers/mod.rs:155` calls `map_err`, `Other`, `display` and `horus_core/src/drivers/mod.rs:322` 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–24 lines × 2) horus_sys/src/shm/fallback.rs:48— horus_sys/src/shm/fallback.rs:48-67 | horus_sys/src/shm/linux.rs:64-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/shm/fallback.rs:48` it begins part-way through the construct above it, so those 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, `horus_sys/src/shm/linux.rs:88` calls `to_string` and `horus_sys/src/shm/fallback.rs:68` 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–23 lines × 2) horus_manager/src/commands/new.rs:174— horus_manager/src/commands/new.rs:174-196 | horus_manager/src/commands/new.rs:1068-1088 — both copies are in the same file, so extract the 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 (22 lines × 2) horus_macros/src/node.rs:523— horus_macros/src/node.rs:523-544 | horus_macros/src/node.rs:548-569 — both copies are in the same file, so extract the 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 (20–22 lines × 2) horus_sys/src/discover/mod.rs:345— horus_sys/src/discover/mod.rs:345-366 | horus_sys/src/discover/mod.rs:402-421 — both copies are in the same file, so extract the 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–21 lines × 2) horus_sys/src/shm/macos.rs:92— horus_sys/src/shm/macos.rs:92-104 | horus_sys/src/shm/macos.rs:163-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 2) horus_manager/src/commands/doc_extract_cpp.rs:703— horus_manager/src/commands/doc_extract_cpp.rs:703-722 | horus_manager/src/commands/doc_extract_rust.rs:1118-1137 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_manager/src/commands/doc_extract_cpp.rs:703` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–19 lines × 2) horus_core/src/types/action_chunk.rs:402— horus_core/src/types/action_chunk.rs:402-420 | horus_core/src/types/action_chunk.rs:432-447 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/types/action_chunk.rs:402` 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 `actions` to `&[f32]` in one and `&[f64]` 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 (15–18 lines × 2) horus_core/src/communication/topic/shm_fanout.rs:1031— horus_core/src/communication/topic/shm_fanout.rs:1031-1048 | horus_core/src/communication/topic/shm_fanout.rs:1093-1107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/shm_fanout.rs:1031` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) horus_core/src/memory/tensor_pool.rs:1548— horus_core/src/memory/tensor_pool.rs:1548-1565 | horus_core/src/memory/tensor_pool.rs:1737-1754 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 3) horus_core/src/scheduling/async_executor.rs:360— horus_core/src/scheduling/async_executor.rs:360-376 | horus_core/src/scheduling/compute_executor.rs:823-839 | horus_core/src/scheduling/event_executor.rs:472-488 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:360` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `horus_core/src/scheduling/event_executor.rs:470` calls `Ok` and `horus_core/src/scheduling/async_executor.rs:359` 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–17 lines × 2) horus_core/src/memory/tensor_pool.rs:467— horus_core/src/memory/tensor_pool.rs:467-483 | horus_core/src/memory/tensor_pool.rs:663-676 — both copies are in the same file, so extract the 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 (16–17 lines × 2) horus_manager/src/commands/pkg.rs:1778— horus_manager/src/commands/pkg.rs:1778-1794 | horus_manager/src/commands/pkg.rs:1880-1895 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/pkg.rs:1778` it does not close everything it opens, so those exact lines 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) horus_manager/src/registry/install.rs:505— horus_manager/src/registry/install.rs:505-520 | horus_manager/src/registry/install.rs:984-997 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/install.rs:505` it does not close everything it opens, so those 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 (3–16 lines × 5) horus_py/src/depth_image.rs:165— horus_py/src/depth_image.rs:165-167 | horus_py/src/image.rs:253-255 | horus_py/src/pointcloud.rs:137-139 | horus_py/src/tensor.rs:385-396 | horus_py/src/tensor.rs:455-470 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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 (15 lines × 5) horus_manager/src/commands/action.rs:251— horus_manager/src/commands/action.rs:251-265 | horus_manager/src/commands/msg.rs:68-82 | horus_manager/src/commands/node.rs:112-126 | horus_manager/src/commands/service.rs:132-146 | horus_manager/src/commands/topic.rs:34-48 — before extracting anything, compare `horus_manager/src/commands/action.rs` and `horus_manager/src/commands/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_manager/src/commands/action.rs:251` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 4) horus_py/src/topic.rs:1079— horus_py/src/topic.rs:1079-1092 | horus_py/src/topic.rs:1097-1110 | horus_py/src/topic.rs:1115-1129 | horus_py/src/topic.rs:1134-1147 — 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 `horus_py/src/topic.rs:1079` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) horus_manager/src/registry/install.rs:873— horus_manager/src/registry/install.rs:873-887 | horus_manager/src/registry/install.rs:1698-1712 | horus_manager/src/registry/install.rs:1967-1981 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_manager/src/registry/install.rs:1982` calls `dimmed`, `display` and `horus_manager/src/registry/install.rs:888` 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–15 lines × 2) horus_manager/src/commands/record.rs:765— horus_manager/src/commands/record.rs:765-779 | horus_manager/src/commands/record.rs:917-924 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/record.rs:765` it does not close everything it opens, so those exact lines 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–15 lines × 2) horus_manager/src/commands/run/run_rust.rs:164— horus_manager/src/commands/run/run_rust.rs:164-176 | horus_manager/src/commands/run/run_rust.rs:689-703 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/run/run_rust.rs:164` it begins part-way through the construct above it, so those 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, `horus_manager/src/commands/run/run_rust.rs:177` calls `finish_error` and `horus_manager/src/commands/run/run_rust.rs:704` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–14 lines × 4) horus_core/src/scheduling/async_executor.rs:337— horus_core/src/scheduling/async_executor.rs:337-350 | horus_core/src/scheduling/compute_executor.rs:800-813 | horus_core/src/scheduling/event_executor.rs:453-462 | horus_core/src/scheduling/rt_executor.rs:1499-1512 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (14 lines × 3) horus_core/src/scheduling/async_executor.rs:404— horus_core/src/scheduling/async_executor.rs:404-429 | horus_core/src/scheduling/compute_executor.rs:867-892 | horus_core/src/scheduling/rt_executor.rs:1894-1907 — before extracting anything, compare `horus_core/src/scheduling/async_executor.rs` and `horus_core/src/scheduling/compute_executor.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 177 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `horus_core/src/scheduling/async_executor.rs:404` it begins part-way through the construct above it, so those 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, `horus_core/src/scheduling/rt_executor.rs:1894` calls `Some` and `horus_core/src/scheduling/async_executor.rs:404` 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–14 lines × 2) horus_core/src/params.rs:266— horus_core/src/params.rs:266-279 | horus_core/src/params.rs:373-384 — both copies are in the same file, so extract the 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–14 lines × 2) horus_sys/src/shm/linux.rs:62— horus_sys/src/shm/linux.rs:62-69 | horus_sys/src/shm/linux.rs:172-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_sys/src/shm/linux.rs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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–13 lines × 4) horus_manager/src/registry/publish.rs:986— horus_manager/src/registry/publish.rs:986-998 | horus_manager/src/registry/publish.rs:1041-1053 | horus_manager/src/registry/publish.rs:1217-1226 | horus_manager/src/registry/publish.rs:1237-1246 — 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 `horus_manager/src/registry/publish.rs:986` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) horus_py/src/topic.rs:819— horus_py/src/topic.rs:819-831 | horus_py/src/topic.rs:841-853 | horus_py/src/topic.rs:863-875 — 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 `horus_py/src/topic.rs:819` it does not close everything it opens, so those exact lines 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–13 lines × 2) horus_manager/src/registry/helpers.rs:853— horus_manager/src/registry/helpers.rs:853-865 | horus_manager/src/registry/helpers.rs:933-943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/helpers.rs:853` it begins part-way through the construct above it, so those 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–12 lines × 3) horus_manager/src/commands/run/run_rust.rs:575— horus_manager/src/commands/run/run_rust.rs:575-584 | horus_manager/src/commands/run/run_rust.rs:966-977 | horus_manager/src/commands/run/run_rust.rs:1067-1078 — 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 (11 lines × 4) horus_manager/src/commands/run/run_rust.rs:163— horus_manager/src/commands/run/run_rust.rs:163-173 | horus_manager/src/commands/run/run_rust.rs:330-342 | horus_manager/src/commands/run/run_rust.rs:421-432 | horus_manager/src/commands/run/run_rust.rs:688-700 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_manager/src/commands/run/run_rust.rs:177` calls `finish_error` and `horus_manager/src/commands/run/run_rust.rs:704` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 3) horus_manager/src/commands/doc.rs:52— horus_manager/src/commands/doc.rs:52-61 | horus_manager/src/commands/fmt.rs:117-127 | horus_manager/src/commands/lint.rs:128-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/commands/doc.rs:52` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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–11 lines × 3) horus_net/src/log_replication.rs:159— horus_net/src/log_replication.rs:159-169 | horus_net/src/presence.rs:151-161 | horus_net/src/presence.rs:170-178 — before extracting anything, compare `horus_net/src/log_replication.rs` and `horus_net/src/presence.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `horus_net/src/log_replication.rs:159` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 2) horus_cpp/src/transform_ffi.rs:69— horus_cpp/src/transform_ffi.rs:69-78 | horus_cpp/src/transform_ffi.rs:90-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_cpp/src/transform_ffi.rs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–11 lines × 2) horus_manager/src/registry/publish.rs:1067— horus_manager/src/registry/publish.rs:1067-1077 | horus_manager/src/registry/publish.rs:1193-1200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_manager/src/registry/publish.rs:1067` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–10 lines × 3) horus_manager/src/commands/run/run_rust.rs:352— horus_manager/src/commands/run/run_rust.rs:352-361 | horus_manager/src/commands/run/run_rust.rs:442-451 | horus_manager/src/commands/run/run_rust.rs:550-557 — 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 `horus_manager/src/commands/run/run_rust.rs:352` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) horus_cpp/src/c_api.rs:523— horus_cpp/src/c_api.rs:523-532 | horus_cpp/src/c_api.rs:1445-1453 — both copies are in the same file, so extract the 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–10 lines × 2) horus_manager/src/commands/run/mod.rs:550— horus_manager/src/commands/run/mod.rs:550-559 | horus_manager/src/commands/run/run_rust.rs:757-764 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_manager/src/commands/run/mod.rs:550` it begins part-way through the construct above it, so those 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, `horus_manager/src/commands/run/run_rust.rs:757` calls `iter`, `enumerate` and `horus_manager/src/commands/run/mod.rs:550` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–9 lines × 3) horus_manager/src/dependency_resolver.rs:89— horus_manager/src/dependency_resolver.rs:89-97 | horus_manager/src/dependency_resolver.rs:119-125 | horus_manager/src/dependency_resolver.rs:160-165 — 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 `horus_manager/src/dependency_resolver.rs:89` it does not close everything it opens, so those 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–9 lines × 2) horus_core/src/communication/topic/dispatch.rs:1719— horus_core/src/communication/topic/dispatch.rs:1719-1727 | horus_core/src/communication/topic/dispatch.rs:1863-1868 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `horus_core/src/communication/topic/dispatch.rs:1719` it begins part-way through the construct above it, so those exact lines 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) horus_manager/src/commands/env.rs:326— horus_manager/src/commands/env.rs:326-334 | horus_manager/src/commands/setup_rt.rs:190-196 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `horus_manager/src/commands/env.rs:326` it does not close everything it opens, so those 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, `horus_manager/src/commands/setup_rt.rs:196` calls `stdin`, `is_terminal`, `cyan` and `horus_manager/src/commands/env.rs:334` 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 lines × 5) horus_manager/src/registry/publish.rs:881— horus_manager/src/registry/publish.rs:881-888 | horus_manager/src/registry/publish.rs:991-998 | horus_manager/src/registry/publish.rs:1046-1053 | horus_manager/src/registry/publish.rs:1070-1077 | horus_manager/src/registry/publish.rs:1124-1131 — 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 `horus_manager/src/registry/publish.rs:881` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6–8 lines × 3) horus_macros/src/node.rs:405— horus_macros/src/node.rs:405-412 | horus_macros/src/node.rs:416-423 | horus_macros/src/node.rs:426-431 — 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 `horus_macros/src/node.rs:405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 4) horus_cpp/src/c_api.rs:1306— horus_cpp/src/c_api.rs:1306-1312 | horus_cpp/src/c_api.rs:1351-1357 | horus_cpp/src/c_api.rs:1396-1402 | horus_cpp/src/c_api.rs:1476-1482 — 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 `horus_cpp/src/c_api.rs:1306` it begins part-way through the construct above it, so those exact lines 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–7 lines × 3) horus_core/src/memory/pointcloud.rs:78— horus_core/src/memory/pointcloud.rs:78-84 | horus_core/src/memory/pointcloud.rs:102-108 | horus_core/src/memory/pointcloud.rs:118-120 — 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 `horus_core/src/memory/pointcloud.rs:78` it does not close everything it opens, so those 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 × 4) horus_manager/src/commands/upgrade.rs:943— horus_manager/src/commands/upgrade.rs:943-948 | horus_manager/src/source_resolver.rs:920-925 | horus_manager/src/source_resolver.rs:943-948 | horus_manager/src/source_resolver.rs:970-975 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (4–6 lines × 3) horus_py/src/depth_image.rs:73— horus_py/src/depth_image.rs:73-78 | horus_py/src/image.rs:116-119 | horus_py/src/pointcloud.rs:47-52 — before extracting anything, compare `horus_py/src/depth_image.rs` and `horus_py/src/image.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 78 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 `horus_py/src/depth_image.rs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `horus_py/src/image.rs:119` calls `getattr`, `extract` and `horus_py/src/depth_image.rs:78` 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 (5 lines × 9) horus_manager/src/commands/action.rs:532— horus_manager/src/commands/action.rs:532-536 | horus_manager/src/commands/blackbox.rs:371-375 | horus_manager/src/commands/launch.rs:593-598 | horus_manager/src/commands/log.rs:294-298 | horus_manager/src/commands/service.rs:488-492 | horus_manager/src/commands/topic.rs:237-241 | horus_manager/src/commands/topic.rs:1055-1059 | horus_manager/src/commands/topic.rs:1211-1215 | horus_manager/src/commands/topic.rs:1371-1375 — before extracting anything, compare `horus_manager/src/commands/action.rs` and `horus_manager/src/commands/service.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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, `horus_manager/src/commands/topic.rs:1063` calls `read_topic_messages_total`, `unwrap_or` and `horus_manager/src/commands/topic.rs:1218` 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) horus_manager/src/registry/publish.rs:1022— horus_manager/src/registry/publish.rs:1022-1033 | horus_manager/src/registry/publish.rs:1047-1058 | horus_manager/src/registry/publish.rs:1100-1111 | horus_manager/src/registry/publish.rs:1125-1136 — 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 `horus_manager/src/registry/publish.rs:1022` it begins part-way through the construct above it, so those 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, `horus_manager/src/registry/publish.rs:1021` calls `json` and `horus_manager/src/registry/publish.rs:1046` 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.
Off the main sequence: horus_sys — horus_sys: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Skeleton type — most members are unfinished horus_core/src/scheduling/mod.rs:84— `impl TelemetryManager` has 6 unfinished methods out of 8 — a scaffolded type that was never implemented.
Unfinished branch — a todo!() / unimplemented!() arm in a real function REDACTED:277— `wait_for_oauth_callback` does real work, but one of its branches is `Err` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
X18 · Disposal-pattern correctness· Owned value's release suppressed and never restored · ×1
Owned value's release suppressed and never restored horus_core/src/communication/topic/mod.rs:687— `mem::forget(msg)` (line 687) takes `msg` out of Rust's ownership: its `Drop` never runs, so whatever it holds — a descriptor, a socket, a buffer, a lock — is never given back, and nothing can give it back later because the value is gone. Let it drop (or call its explicit close) where its work ends; if the handle must outlive this function, turn it into a raw handle with `into_raw`/`into_raw_fd` and reclaim it with the matching `from_raw` when the owner is done.
No direct assertions: page loads with correct title horus_manager/tests/web_e2e/basic.test.js:25— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: no console errors on page load horus_manager/tests/web_e2e/basic.test.js:32— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: status bar is visible horus_manager/tests/web_e2e/basic.test.js:44— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: monitor tab exists horus_manager/tests/web_e2e/basic.test.js:52— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: API /api/status responds with JSON horus_manager/tests/web_e2e/basic.test.js:59— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: API /api/nodes responds with valid JSON horus_manager/tests/web_e2e/basic.test.js:72— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: API /api/topics responds with valid JSON horus_manager/tests/web_e2e/basic.test.js:86— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: API /api/graph responds with nodes and edges horus_manager/tests/web_e2e/basic.test.js:99— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: JavaScript functions loaded horus_manager/tests/web_e2e/basic.test.js:112— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: page renders within 5 seconds horus_manager/tests/web_e2e/basic.test.js:126— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Monitor tab is active by default horus_manager/tests/web_e2e/tabs.test.js:30— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: switch to Parameters tab horus_manager/tests/web_e2e/tabs.test.js:40— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: switch to Packages tab horus_manager/tests/web_e2e/tabs.test.js:57— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: switch to API Docs tab horus_manager/tests/web_e2e/tabs.test.js:73— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: switch back to Monitor tab horus_manager/tests/web_e2e/tabs.test.js:89— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: graph canvas exists and has dimensions horus_manager/tests/web_e2e/tabs.test.js:107— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: status bar shows node and topic counts horus_manager/tests/web_e2e/tabs.test.js:122— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: empty state shows placeholder text horus_manager/tests/web_e2e/tabs.test.js:135— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: /api/status has required fields horus_manager/tests/web_e2e/tabs.test.js:149— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: /api/graph has nodes[] and edges[] horus_manager/tests/web_e2e/tabs.test.js:162— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: /api/params responds horus_manager/tests/web_e2e/tabs.test.js:175— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Parameters tab renders param content horus_manager/tests/web_e2e/tabs.test.js:187— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: Packages tab renders content horus_manager/tests/web_e2e/tabs.test.js:202— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: WebSocket connection attempt made horus_manager/tests/web_e2e/tabs.test.js:216— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: updateAll function exists and is callable horus_manager/tests/web_e2e/tabs.test.js:230— No conventional assertion call was detected, and 43 of 43 tests in `horus_manager/tests/web_e2e` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Duplicated predicate horus_core/src/communication/mod.rs:237— `!capacity.is_power_of_two() || cap_mask != capacity - 1` appears character-identically in 2 files — horus_core/src/communication/mod.rs, horus_net/src/shm_writer.rs. 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 horus_manager/src/commands/check.rs:438— `!name.starts_with('.') && name != "target" && name != "node_modules"` appears character-identically in 2 files — horus_manager/src/commands/check.rs, horus_manager/src/commands/test.rs. 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 horus_core/src/scheduling/async_executor.rs:184— `!node.initialized || node.is_stopped || node.is_paused || monitors.node_controls.is_paused(node.name.as_ref()) || !node.failure_policy_allow…` appears character-identically in 3 files — horus_core/src/scheduling/async_executor.rs, horus_core/src/scheduling/compute_executor.rs, horus_core/src/scheduling/event_executor.rs. 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 horus_core/src/types/costmap_descriptor.rs:119— `!self.resolution.is_finite() || self.resolution <= 0.0` appears character-identically in 2 files — horus_core/src/types/costmap_descriptor.rs, horus_core/src/types/occupancy_grid_descriptor.rs. 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 horus_core/src/memory/costmap.rs:705— `(wx - ex).abs() < 1e-6 && (wy - ey).abs() < 1e-6` appears character-identically in 2 files — horus_core/src/memory/costmap.rs, horus_core/src/memory/occupancy_grid.rs. 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 horus_manager/src/commands/fmt.rs:227— `candidate.is_file() || candidate.with_extension("exe").is_file()` appears character-identically in 2 files — horus_manager/src/commands/fmt.rs, horus_manager/src/commands/run/mod.rs. 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 horus_core/src/communication/topic/mod.rs:1395— `capacity == 0 || !capacity.is_power_of_two()` appears character-identically in 2 files — horus_core/src/communication/topic/mod.rs, horus_core/src/communication/topic/shm_fanout.rs. 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 horus_manager/src/commands/bench.rs:33— `ctx.has_horus_toml && !ctx.root.join("Cargo.toml").exists() && horus_manifest.exists()` appears character-identically in 4 files — horus_manager/src/commands/bench.rs, horus_manager/src/commands/doc.rs, horus_manager/src/commands/fmt.rs, horus_manager/src/commands/lint.rs. 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 horus_core/src/memory/costmap.rs:318— `grid_x < self.width() && grid_y < self.height()` appears character-identically in 2 files — horus_core/src/memory/costmap.rs, horus_core/src/memory/occupancy_grid.rs. 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 horus_core/src/memory/costmap.rs:409— `grid_x >= 0 && grid_x < self.width() as i32 && grid_y >= 0 && grid_y < self.height() as i32` appears character-identically in 2 files — horus_core/src/memory/costmap.rs, horus_core/src/memory/occupancy_grid.rs. 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 horus_manager/src/commands/check.rs:1266— `horus_dir.exists() && horus_dir.is_dir()` appears character-identically in 2 files — horus_manager/src/commands/check.rs, horus_manager/src/workspace.rs. 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 horus_manager/src/commands/run/install.rs:1230— `input.is_empty() || input == "y" || input == "yes"` appears character-identically in 2 files — horus_manager/src/commands/run/install.rs, horus_manager/src/registry/helpers.rs. 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 horus_manager/src/paths.rs:79— `name.is_empty() || name.contains(['/', '\\']) || name.contains("..")` appears character-identically in 2 files — horus_manager/src/paths.rs, horus_manager/src/registry/helpers.rs. 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 horus_core/src/scheduling/primitives.rs:354— `new_rate_hz > 0.0 && old_rate > new_rate_hz` appears character-identically in 2 files — horus_core/src/scheduling/primitives.rs, horus_core/src/scheduling/scheduler/mod.rs. 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 horus_core/src/scheduling/async_executor.rs:366— `node.is_rt_node || node.node_watchdog.is_some()` appears character-identically in 4 files — horus_core/src/scheduling/async_executor.rs, horus_core/src/scheduling/compute_executor.rs, horus_core/src/scheduling/event_executor.rs, horus_core/src/scheduling/rt_executor.rs. 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 horus_core/src/scheduling/async_executor.rs:197— `rate_hz > 0.0 && elapsed < 1.0 / rate_hz` appears character-identically in 2 files — horus_core/src/scheduling/async_executor.rs, horus_core/src/scheduling/compute_executor.rs. 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 horus_manager/src/cmake_gen.rs:1390— `std::env::var("CI").is_ok() || std::env::var("USER").as_deref() == Ok("root")` appears character-identically in 2 files — horus_manager/src/cmake_gen.rs, horus_manager/src/commands/doc_extract.rs. 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 horus_manager/src/commands/bench.rs:39— `tool.bin == "cargo" && use_horus_manifest` appears character-identically in 4 files — horus_manager/src/commands/bench.rs, horus_manager/src/commands/doc.rs, horus_manager/src/commands/fmt.rs, horus_manager/src/commands/lint.rs. 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 horus_py/src/depth_image.rs:188— `x >= self.inner.width() || y >= self.inner.height()` appears character-identically in 2 files — horus_py/src/depth_image.rs, horus_py/src/image.rs. 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 on Err benchmarks/src/bin/competitor_comparison.rs:205— `main` turns every `Err` into `5` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_cpp/src/c_api.rs:1441— `horus_params_get_string` turns every `Err` into `-1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/plugins/discovery.rs:341— `discover_registry` turns every `Err` into `Ok(Vec::new())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/commands/deploy.rs:1444— `deploy_python_requirements` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/commands/msg.rs:489— `git_packages_in_lock` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/commands/run/install.rs:1980— `top_level_modules` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/manifest_lint.rs:311— `find_unknown_keys` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_manager/src/registry/publish.rs:197— `load_horusignore` turns every `Err` into `vec![]` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_net/src/netfilter.rs:133— `from_env` turns every `Err` into `Self::default()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_py/src/node.rs:318— `__repr__` turns every `Err` into `Ok("NodeInfo(locked)".to_string())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/discover/mod.rs:216— `find_nodes` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/process/mod.rs:369— `pid_start_time_linux` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/rt/linux.rs:654— `present_cpus` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/rt/linux.rs:1235— `detect_isolated_cpus` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/rt/linux.rs:1243— `detect_nohz_full_cpus` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/rt/windows.rs:184— `get_windows_version` turns every `Err` into `"Windows".to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/shm/mod.rs:1165— `list_topic_metas` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err horus_sys/src/shm/mod.rs:1836— `list_all_horus_namespaces` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:185— `info!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:199— `warn!` at line 199 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:205— `error!` at line 205 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:247— `error!` at line 247 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:267— `warn!` at line 267 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:282— `info!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/drivers/exec_driver.rs:307— `warn!` at line 307 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/dispatch.rs:1203— `warn!` at line 1203 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/dispatch.rs:1325— `warn!` at line 1325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/dispatch.rs:1894— `warn!` at line 1894 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/dispatch.rs:2636— `warn!` at line 2636 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/mod.rs:2204— `warn!` at line 2204 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging horus_core/src/communication/topic/mod.rs:3639— `warn!` at line 3639 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Subsumed condition operand horus_net/tests/replicator_output_safety.rs:80— `code.contains("eprintln!")` can never decide this `||` — every value satisfying `code.contains("eprintln!")` also satisfies `code.contains("println!")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/tests/docs_examples_python.rs:279— `l.starts_with("*, ")` can never decide this `||` — every value satisfying `l.starts_with("*, ")` also satisfies `l.starts_with("*,")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/tests/e2e_introspection.rs:86— `combined.contains("e2e_camera")` can never decide this `||` — every value satisfying `combined.contains("e2e_camera")` also satisfies `combined.contains("camera")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/tests/e2e_introspection.rs:152— `combined.contains("e2e_imu_data")` can never decide this `||` — every value satisfying `combined.contains("e2e_imu_data")` also satisfies `combined.contains("imu")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/tests/workflow_e2e.rs:284— `content.contains(".horus")` can never decide this `||` — every value satisfying `content.contains(".horus")` also satisfies `content.contains("horus")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/src/cargo_gen.rs:3821— `content.contains("src/main.rs")` can never decide this `||` — every value satisfying `content.contains("src/main.rs")` also satisfies `content.contains("main.rs")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/src/error_wrapper.rs:306— `stderr.contains("ld: cannot find -l")` can never decide this `||` — every value satisfying `stderr.contains("ld: cannot find -l")` also satisfies `stderr.contains("cannot find -l")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/src/plugins/discovery.rs:291— `name_lower.contains("rplidar")` can never decide this `||` — every value satisfying `name_lower.contains("rplidar")` also satisfies `name_lower.contains("lidar")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_manager/src/discovery/tests.rs:2741— `age.contains("1h")` can never decide this `||` — every value satisfying `age.contains("1h")` also satisfies `age.contains("h")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand REDACTED:301— `t.topic_name.contains("transform_frame")` can never decide this `||` — every value satisfying `t.topic_name.contains("transform_frame")` also satisfies `t.topic_name.contains("transform")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_core/tests/cli_runtime_integration.rs:158— `output.contains("sensor.cmd_vel")` can never decide this `||` — every value satisfying `output.contains("sensor.cmd_vel")` also satisfies `output.contains("cmd_vel")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand horus_core/src/communication/topic/tests.rs:8044— `msg.contains("File name too long")` can never decide this `||` — every value satisfying `msg.contains("File name too long")` also satisfies `msg.contains("too long")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion horus_manager/Cargo.toml:1— `horus_manager` (121189 LoC, 270 module-visible types across 8 directories) overshoots its size bounds. 3 of 11 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 4.5/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 horus_core/Cargo.toml:1— `horus_core` (112714 LoC, 270 module-visible types across 13 directories) overshoots its size bounds. 3 of 11 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 4.5/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 horus_py/Cargo.toml:1— `horus_py` (21565 LoC, 136 module-visible types across 5 directories) overshoots its size bounds. 3 of 11 build unit(s) (Cargo) overshoot their size bounds, lowering Project Cohesion to 4.5/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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: horus_manager/tests/web_e2e horus_manager/tests/web_e2e/basic.test.js:25— No conventional assertion call was detected in 43 of 43 tests in `horus_manager/tests/web_e2e` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
No ADRs found horus_manager/Cargo.toml:26— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `horus_manager/Cargo.toml` makes this repository a deployable product (line 26).
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 5/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
Silent fallback default on parse failure .github/scripts/autopilot_triage.py:129— `failed_runs` returns `[]` when `json.JSONDecodeError` is raised, with no log or raise — 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 on the handler or in the docstring, and the row stops firing.
Outdated: ctor — `ctor` is locked at 1.0.13 but 1.0.14 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ctor` and commit the updated REDACTED.
Outdated: cxx — `cxx` is locked at 1.0.202 but 1.0.205 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus_cpp/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cxx` and commit the updated REDACTED.
Outdated: cxx-build — `cxx-build` is locked at 1.0.202 but 1.0.205 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus_cpp/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cxx-build` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.10 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: lazy_static — `lazy_static` is locked at 1.5.0 but 1.5.1 is the current stable release on crates.io, and it already satisfies the `"1.4"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p lazy_static` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.34 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: memmap2 — `memmap2` is locked at 0.9.11 but 0.9.12 is the current stable release on crates.io, and it already satisfies the `"0.9"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p memmap2` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.2 is the current stable release on crates.io, and it already satisfies the `"8.2"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: open — `open` is locked at 5.4.4 but 5.4.5 is the current stable release on crates.io, and it already satisfies the `"5.0"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p open` and commit the updated REDACTED.
Outdated: schemars — `schemars` is locked at 1.2.2 but 1.2.3 is the current stable release on crates.io, and it already satisfies the `"1.2"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p schemars` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in benchmarks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: sha2 — `sha2` is locked at 0.11.0 but 0.11.1 is the current stable release on crates.io, and it already satisfies the `"0.11"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p sha2` and commit the updated REDACTED.
Outdated: syn — `syn` is locked at 3.0.6 but 3.0.10 is the current stable release on crates.io, and it already satisfies the `"3.0"` requirement declared in horus_cpp_macros/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p syn` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.1 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: toml — `toml` is locked at 1.1.6+spec-1.1.0 but 1.2.1+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml` and commit the updated REDACTED.
Outdated: toml_edit — `toml_edit` is locked at 0.25.15+spec-1.1.0 but 0.25.19+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml_edit` and commit the updated REDACTED.
Outdated: tree-sitter — `tree-sitter` is locked at 0.27.0 but 0.27.2 is the current stable release on crates.io, and it already satisfies the `"0.27"` requirement declared in horus_manager/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tree-sitter` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.26.1 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
Outdated: zstd — `zstd` is locked at 0.14.0 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in horus_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zstd` and commit the updated REDACTED.
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.
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 01a1e623-7255-722f-93d1-1da771d0cfd3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 13 · Warnings: 1264 · Recommendations: 115 · Info: 20 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 20:54 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.