Public report of multiplex-term/Multiplex, 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 22:24 UTC · Survey ID cd_76452618b33648faa73e9458eaaa1436

multiplex-term/Multiplex

Measured 16 November 2026, 22:22 UTC, at code version f395338

First survey, so nothing to compare with yet Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 65.7out of 100 Adequate
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 92,554 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Production Readiness, 54.0

Findings by how serious they are

8 critical 750 serious 25 minor

32 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 22:22 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 ▸

42of 42 dimensions measured by tools.
779of 783 findings point to an exact file and line, so you can open each one in the code. The other 4 concern the repository as a whole, such as missing documentation.
42dimensions across 7 lenses, read from 92,554 lines of product code in 2 projects.
Chapters

Executive summary

multiplex-term/Multiplex falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 65.7 out of 100 and is rated Adequate, and six of its eight critical findings are security problems in the build pipeline and in the packages it uses.

Production Readiness, at 54.0, is the weakest lens and counts most in the score. The best first step is making the tests check their results, worth about 7.6 points. Keeping a changelog would lift Production Readiness itself, worth about 4.0 points. Raising Production Readiness to 70 would lift the score to about 72.7.

Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. The two tests that check nothing need to check the result they produce.

The product code is 92,554 lines, about €150,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 for The 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.
Production Readiness 54.0 · counts for 46%Maturity 68.5 · counts for 25%Code Health 70.0 · counts for 14%Performance 85.0 · counts for 8%Architecture 99.2 · counts for 4%Security and Compliance 100.0 · counts for 2%Domain Modelling 100.0 · counts for 1%

If Production Readiness rose from 54.0 to 70, the lowest score rated Strong, the score would rise from 65.7 to about 72.7.

Code composition: what the lines of code are
Product code 74%Tests 26%
Rebuild cost: about €150,000 · Estimate
Cost to rebuild€50,000 to €250,000, for 830 to 2,632 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 66. 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.
SizeMedium: 92,554 lines of product code
What it is notNot 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 Assertions commented out finding(s) in Test Quality — start with MeanTests.swift.
Raises the score by about 7.6 points · Low effort · Test Quality
2
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FuzzerTests.swift.
Raises the score by about 7.6 points · Low effort · Test Quality
3
Resolve the 2 `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` finding(s) in Naming Consistency — start with MacTerminalView.swift, iOSTerminalView.swift.
Raises the score by about 3.6 points · Low effort · Naming Consistency

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Production Readiness, at 54.0 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Assertions commented out finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7.6 points for low effort, because it clears the 1 Test 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 7.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 31,529 lines over the last 90 days, which is about 127,868 lines a year. At that pace, the extra work comes to an estimated 6.4 to 42.6 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.

arch Multiplex Multiplex MultiplexWidgets MultiplexWidgets

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.

17 modules, with 22 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

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.
uses →1 (global)2 Tools3 Tools.appstore4 Tools.echo-bench5 Vendor.SwiftTerm.scripts6 repository7 Vendor~SwiftTerm~SwiftTermBuildInfoGenerator8 Vendor~swift-nio-ssh~NIOSSH9 Vendor~SwiftTerm~SwiftTerm10 Vendor~swift-nio-ssh~NIOSSHClient11 Vendor~swift-nio-ssh~NIOSSHPerformanceTester12 Vendor~swift-nio-ssh~NIOSSHServer13 Vendor~SwiftTerm~CaptureOutput14 Vendor~SwiftTerm~SwiftTermFuzz15 Vendor~SwiftTerm~SwiftTermWasmSmoke16 Vendor~SwiftTerm~SwiftTermWebWasm17 Vendor~SwiftTerm~Termcast
1 (global)
2 Tools
3 Tools.appstore
4 Tools.echo-bench
5 Vendor.SwiftTerm.scripts
6 repository2053
7 Vendor~SwiftTerm~SwiftTermBuildInfoGenerator7
8 Vendor~swift-nio-ssh~NIOSSH471
9 Vendor~SwiftTerm~SwiftTerm19753
10 Vendor~swift-nio-ssh~NIOSSHClient24
11 Vendor~swift-nio-ssh~NIOSSHPerformanceTester48
12 Vendor~swift-nio-ssh~NIOSSHServer29
13 Vendor~SwiftTerm~CaptureOutput26
14 Vendor~SwiftTerm~SwiftTermFuzz3
15 Vendor~SwiftTerm~SwiftTermWasmSmoke3
16 Vendor~SwiftTerm~SwiftTermWebWasm131724
17 Vendor~SwiftTerm~Termcast123
Uses a module listed above itPart of a loopThe module itself
1 (global)2 Tools3 Tools.appstore4 Tools.echo-bench5 Vendor.SwiftTerm.scripts6 repository7 Vendor~SwiftTerm~SwiftTermBuildInfoGenerator8 Vendor~swift-nio-ssh~NIOSSH9 Vendor~SwiftTerm~SwiftTerm10 Vendor~swift-nio-ssh~NIOSSHClient11 Vendor~swift-nio-ssh~NIOSSHPerformanceTester12 Vendor~swift-nio-ssh~NIOSSHServer13 Vendor~SwiftTerm~CaptureOutput14 Vendor~SwiftTerm~SwiftTermFuzz15 Vendor~SwiftTerm~SwiftTermWasmSmoke16 Vendor~SwiftTerm~SwiftTermWebWasm17 Vendor~SwiftTerm~Termcast(global)1Tools2Tools.appstore3Tools.echo-bench4Vendor.SwiftTerm.scripts5repository6Vendor~SwiftTerm~SwiftTermBuildInfoGenerator7Vendor~swift-nio-ssh~NIOSSH8Vendor~SwiftTerm~SwiftTerm9Vendor~swift-nio-ssh~NIOSSHClient10Vendor~swift-nio-ssh~NIOSSHPerformanceTester11Vendor~swift-nio-ssh~NIOSSHServer12Vendor~SwiftTerm~CaptureOutput13Vendor~SwiftTerm~SwiftTermFuzz14Vendor~SwiftTerm~SwiftTermWasmSmoke15Vendor~SwiftTerm~SwiftTermWebWasm16Vendor~SwiftTerm~Termcast1720537471197532448292633131724123

At a glance — Code Health · 70.0 · Strong ·

At a glance — Architecture · 99.2 · Exemplary ·

At a glance — Maturity · 68.5 · Adequate · gated by M2 ·

At a glance — Readiness · 54.0 · Adequate · gated by P3 ·

At a glance — Security · 100.0 · Exemplary ·

At a glance — Domain Modelling · 100.0 · Exemplary ·

At a glance — Performance · 85.0 · Strong ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection5High / Critical
A03:2025 — Software Supply Chain Failures3High / Critical

Roadmap

Top priorities: Resolve the 1 Assertions commented out finding(s) in Test Quality — start with MeanTests.swift; Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FuzzerTests.swift; Resolve the 274 No assertions finding(s) in Test Quality — start with KittyKeyboardEncoderTests.swift (51), CsiParameterParsingTests.swift (32), CertifiedKeyTests.swift (24).

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with MeanTests.swift.+7.6 ptsLowTest Quality
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FuzzerTests.swift.+7.6 ptsLowTest Quality
Resolve the 2 `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` finding(s) in Naming Consistency — start with MacTerminalView.swift, iOSTerminalView.swift.+3.6 ptsLowNaming Consistency
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+4.0 ptsMediumRelease Hygiene
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.+3.1 ptsMediumArchitecture documentation
Resolve the 274 No assertions finding(s) in Test Quality — start with KittyKeyboardEncoderTests.swift (51), CsiParameterParsingTests.swift (32), CertifiedKeyTests.swift (24).+5.3 ptsHighTest Quality
Swallowed exception (caught, then discarded)+2.3 ptsMediumException handling
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.+1.1 ptsMediumAsync & latency hygiene

File quality

Per-file score 0–10 — a quality signature. Of 123 files carrying findings, judged against the Production bar: 0% slop · 68% mixed · 32% near-clean.

FileScoreBandWorst signal
REDACTED4.4MixedDependency Vulnerabilities: High CVE: REDACTED
Multiplex/Views/Terminal/TerminalKeyBar.swift4.8MixedCyclomatic Complexity: TerminalKeyBar.rebuildRow (cyclomatic 21)
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
Multiplex/Views/Deck/FleetWall.swift5.5MixedCyclomatic Complexity: FleetHostSectionView.render (cyclomatic 31)
Multiplex/Services/TerminalSessionController.swift5.5MixedCyclomatic Complexity: TerminalSessionController.runHistoryJump (cyclomatic 25)
Multiplex/Design/Chassis.swift5.5MixedGod Classes: FileTooLong: Design/Chassis.swift
Multiplex/Views/Terminal/TerminalVisionOrnaments.swift5.5MixedCyclomatic Complexity: TerminalVisionOrnamentState.update (cyclomatic 23)
Multiplex/Services/SSHConnection.swift5.6MixedCyclomatic Complexity: SSHConnection.makeAuthenticationMethod (cyclomatic 22)
Multiplex/Views/Terminal/SwiftTermView.swift5.9MixedGod Classes: MethodTooLong: TerminalSurfaceView.installTerminal
Multiplex/Views/Settings/ProPaywallView.swift5.9MixedCode Duplication: Duplicated block (11 lines × 2)
Multiplex/Views/Terminal/TerminalTabStrip.swift6.3MixedGod Classes: FileTooLong: Terminal/TerminalTabStrip.swift
Multiplex/Views/Terminal/TerminalWindow.swift6.3MixedCode Duplication: Edited copy of a member (23 corresponding lines)
Vendor/SwiftTerm/Tests/SwiftTermTests/FuzzerTests.swift6.5MixedTest Quality: No assertions (empty test): testCrashes
Multiplex/Services/ConnectionHub.swift7.0MixedCyclomatic Complexity: HostConnectionModel.performRefresh (cyclomatic 42)
Multiplex/Views/Terminal/TerminalWindowUIKit.swift7.0MixedCyclomatic Complexity: TerminalWindowViewController.watchActivePane (cyclomatic 38)
Multiplex/Views/Deck/DeckWindow.swift7.0MixedCyclomatic Complexity: DeckScene.autoAttachIfRequested (cyclomatic 26)
Multiplex/Views/Terminal/UMDBarUIKit.swift7.0MixedCyclomatic Complexity: UMDBarViewController.makeOverflowMenu (cyclomatic 25)
Multiplex/Services/TmuxProbe.swift7.0MixedCyclomatic Complexity: TmuxProbe.parse (cyclomatic 21)
Multiplex/Views/Deck/ConnectionStatsView.swift7.0MixedCyclomatic Complexity: ConnectionStatsStripView.rebuildCluster (cyclomatic 19)
Multiplex/Views/Terminal/FileViewerPane.swift7.0MixedCyclomatic Complexity: FileViewerPaneViewController.headerMeta (cyclomatic 19)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 8

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 750

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 — 25

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 32

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 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 42 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D21D27D28D29D30D34D35D43D44AX10AX3AX4AX6AX8AX9DM4DM5DM6M1M2M3M4P1P2P3P6PF3X14X28X3

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
  1. 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, 779 of 783 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e674-3e22-7035-9d30-679992e310c6.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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 Swift half could not be measured — the Swift suite in Vendor/SwiftTerm produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (2 packages), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 457 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D20 ADR Quality — 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. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. No manifest, project file or entry point of any ecosystem it reads exists in this tree.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — 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. `(repository root)` (75779 LoC, 1501 module-visible types across 47 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Multiplex/App/MultiplexApp.swift`, `Multiplex/Models/Bind/BindProtocol.swift`, `Multiplex/Models/KeyCommand.swift`, `Multiplex/Models/SidePanel.swift`, `Multiplex/Services/AppLockStore.swift`, … (+31 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Multiplex/Views/Deck/DeckWindow.swift, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (Vendor/swift-nio-ssh/docker/docker-compose.1804.54.yaml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — shell Error pull access denied for swift-nio-ssh, repository does not exist or may require 'docker login': denied: requested access to the resource is denied test Error pull access denied for swift-nio-ssh, repository does not exist or may require 'docker login': denied: requested access to the resource is denied runtime-setup Built container docker-runtime-setup-1 exited (0); runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Swift, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Swift, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# and Elixir source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# or Elixir was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's C, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Go source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Go was found, and this repository's C, Swift (Foundation mutable collections) is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby and Erlang source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby or Erlang was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's C, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.8 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Prevented

35 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SingleWindowShellNativeLayout.resolve at 48. A further 4 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 TerminalKeyBar.press at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Multiplex/Views/Terminal/TerminalGuidePictograms.swift (TerminalGuidePictogramView.draw at 20). 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.

SingleWindowShellNativeLayout.resolve (cyclomatic 48)Multiplex/Views/Shell/SingleWindowShell.swift:155
HostConnectionModel.performRefresh (cyclomatic 42)Multiplex/Services/ConnectionHub.swift:518
TerminalWindowViewController.watchActivePane (cyclomatic 38)Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1790
FleetHostSectionView.render (cyclomatic 31)Multiplex/Views/Deck/FleetWall.swift:1803
TerminalWindowViewController.layoutNativeChrome (cyclomatic 31)Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393

+ 30 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with SingleWindowShellNativeLayout.resolve (cyclomatic 48), HostConnectionModel.performRefresh (cyclomatic 42), TerminalWindowViewController.watchActivePane (cyclomatic 38). — 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 5 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.4 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 100% · ceiling Prevented

58 method(s) exceeded the cognitive complexity threshold of 15; the worst was HostConnectionModel.performRefresh at 71.

HostConnectionModel.performRefresh (cognitive 71)Multiplex/Services/ConnectionHub.swift:518
TerminalWindowViewController.watchActivePane (cognitive 71)Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1790
SingleWindowShellNativeLayout.resolve (cognitive 54)Multiplex/Views/Shell/SingleWindowShell.swift:155
TerminalWindowViewController.layoutNativeChrome (cognitive 45)Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393
FleetHostSectionView.render (cognitive 41)Multiplex/Views/Deck/FleetWall.swift:1803

+ 53 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with HostConnectionModel.performRefresh (cognitive 71), TerminalWindowViewController.watchActivePane (cognitive 71). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.0 / 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.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Prevented

96 god class(es) detected.

FileTooLong: Deck/FleetWall.swift · ×35Multiplex/Views/Deck/FleetWall.swift
ClassTooLong: AddHostViewController · ×27Multiplex/Views/Deck/AddHostSheet.swift:252
TooManyMethods: TerminalWindowViewController · ×19Multiplex/Views/Terminal/TerminalWindowUIKit.swift:296
MethodTooLong: TerminalWindowViewController.layoutNativeChrome · ×15Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393

What to do

  1. Resolve the 35 FileTooLong finding(s) in God Classes — start with FleetWall.swift, FileViewerPane.swift, TerminalWindowUIKit.swift. — One of this dimension's main actionable groups (35 warning-level).
  2. Resolve the 27 ClassTooLong finding(s) in God Classes — start with FleetWall.swift (2), AddHostSheet.swift, TerminalSessionController.swift. — One of this dimension's main actionable groups (27 warning-level).
  3. Resolve the 19 TooManyMethods finding(s) in God Classes — start with TerminalKeyBar.swift (2), TerminalWindowUIKit.swift, TerminalSessionController.swift. — 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.

D4 · Code Duplication7.4 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.4 / 10 · rule-coverage 100% · ceiling Verified

134 duplicated block group(s) detected. 6.5 % of the production lines (5,996 of 92,554) are in a reported copy. A further 113 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 247 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.

Duplicated block (6 lines × 2) · ×11Multiplex/Views/Deck/ConnectionStatsView.swift:578
Edited copy of a member (10 corresponding lines) · ×10Multiplex/AppIntents/OpenHostIntents.swift:214
Duplicated block (7 lines × 2) · ×9Multiplex/AppIntents/OpenHostIntents.swift:265
Duplicated block (9 lines × 2) · ×8Multiplex/Views/Deck/AddHostSheet.swift:1541
Edited copy of a member (19 corresponding lines) · ×7Multiplex/Services/TmuxProbe.swift:394

+ 108 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ConnectionStatsView.swift (2), CustomAgentCommandPanel.swift, FileViewerPane.swift. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 10 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with TerminalSessionController.swift (2), OpenHostIntents.swift, AgentChoice.swift. — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CustomAgentCommandPanel.swift (2), FileViewerPane.swift (2), OpenHostIntents.swift. — One of this dimension's main actionable groups (9 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

2 production modules (XcodeGen), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; an XcodeGen target's dependency on a local Swift package or on a target of another project is not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.4 / 10Stronggated by 11 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Verified

11 of 231 classes have LCOM4 above 3.

Low cohesion: TerminalSessionController (LCOM4 12) · ×11Multiplex/Services/TerminalSessionController.swift:11

What to do

  1. Resolve the 11 Low cohesion finding(s) in Cohesion (LCOM4) — start with TerminalKeyBar.swift (2), TerminalSessionController.swift, SSHConnection.swift. — One of this dimension's main actionable groups (11 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality8.8 / 10Adequategated by 2 critical findings✓ 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.

Maturity: Documented → Verified → Prevented · effective 8.8 / 10 · rule-coverage 100% · ceiling Prevented

16 skipped (13 with a documented reason), 276 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3577 tests.

No assertions (empty test): testCrashesVendor/SwiftTerm/Tests/SwiftTermTests/FuzzerTests.swift:60
Assertions commented out: testInvalidMarginsVendor/SwiftTerm/Tests/SwiftTermTests/MeanTests.swift:40
No assertions: testBindHostLimitObservationUsesNativePaywallRoute · ×274MultiplexTests/AddHostUIKitTests.swift:608
Skipped test: testPressAndDragReordersTheKeys · ×3MultiplexUITests/ArrangeKeysUITests.swift:21
Skipped (documented): aSixtyFourMiBFragmentedWriteCommits · ×13Vendor/SwiftTerm/Tests/SwiftTermTests/KittyClipboardProtocolTests.swift:1435

What to do

  1. Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with FuzzerTests.swift. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Assertions commented out finding(s) in Test Quality — start with MeanTests.swift. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 274 No assertions finding(s) in Test Quality — start with KittyKeyboardEncoderTests.swift (51), CsiParameterParsingTests.swift (32), CertifiedKeyTests.swift (24). — One of this dimension's main actionable groups (274 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 outdated direct gem(s), 0 pinning defect(s). 1 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed REDACTED. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Outdated: fastlane

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 98 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 98 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 9 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Multiplex/Views/Terminal/TerminalWindowUIKit.swift (16×31=496); Multiplex/Views/Shell/SingleWindowShell.swift (8×48=384); Multiplex/Views/Deck/FleetWall.swift (8×31=248)

Hotspot: Multiplex/Views/Terminal/TerminalWindowUIKit.swift · ×9Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393

What to do

  1. Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with TerminalWindowUIKit.swift, SingleWindowShell.swift, FleetWall.swift. — One of this dimension's main actionable groups (9 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 92554 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D21 · Naming Consistency5.0 / 10Adequate✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Verified

2 naming inconsistencies among 40 declarations measured against a convention their peers follow.

`updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` · ×2Vendor/SwiftTerm/Sources/SwiftTerm/Mac/MacTerminalView.swift:1129

What to do

  1. Resolve the 2 `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` finding(s) in Naming Consistency — start with MacTerminalView.swift, iOSTerminalView.swift. — One of this dimension's main actionable groups (2 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Adequategated by 5 critical findings○ Nothing flagged

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).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 5 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 13 file(s) — `Multiplex/Services/AppLockStore.swift` (line 53), `Multiplex/Services/AttentionCenter.swift` (line 316, line 317, line 319, …), `Multiplex/Views/Deck/FleetWall.swift` (line 4055, line 4056, line 4057), `Tools/appstore/compose.sh` (lines 69–100), `Vendor/SwiftTerm/Sources/SwiftTerm/Mac/MacTerminalView.swift` (line 4792), … (+8 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED

What to do

  1. No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities9.1 / 10Adequategated by 1 critical finding✓ Tool-verified

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 REDACTED 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.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 1 high, 1 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 184 of the 221 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.6 / 10Stronggated by 3 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: SingleWindowShellPolicy.swift↔TerminalKeyBar.swift 55%; SwiftTermView.swift↔TerminalWindow.swift 53%; AgentSignature.swift↔TerminalWindow.swift 50%

Change coupling: SingleWindowShellPolicy.swift ↔ TerminalKeyBar.swift · ×2Multiplex/Models/SingleWindowShellPolicy.swift:1
Change-coupling hub: TerminalWindow.swift → AgentSignature.swift, TerminalWorkspace.swift, SwiftTermView.swiftMultiplex/Views/Terminal/TerminalWindow.swift

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with SingleWindowShellPolicy.swift, ProPaywallView.swift. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with TerminalWindow.swift. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain entities own their behaviour — a data-only reference entity whose logic lives in a foreign service is anemic. Rich models enforce their own invariants.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a reference entity protects its own invariants — a class whose identity is a computed content hash but whose hashed fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM on its own declaration (active-record), or reaching a web-framework transport type in its own method, couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

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.

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

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.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:16

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene8.5 / 10Strong✓ Tool-verified

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.

  • `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Multiplex/Services/Mosh/MoshSession.swift:361

What to do

  • Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

X3 · Exception handling5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×12) — Multiplex/Views/Deck/FleetWall.swift:871, Multiplex/Views/Deck/FleetWall.swift:875, Multiplex/Shared/SharedStateStore.swift:180, …

What to do

  • Swallowed exception (caught, then discarded)

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.

LensScoreRatingImpact
Code Health70.0StrongSolid.
Architecture99.2ExemplarySolid.
Maturity68.5Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness54.0Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100.0ExemplaryStrongest area.
Domain Modelling100.0ExemplarySolid.
Performance85.0StrongSolid.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 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 — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC2 Forms & labels — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC3 Page structure — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — shell Error pull access denied for swift-nio-ssh, repository does not exist or may require 'docker login': denied: requested access to the resource is denied test Error pull access denied for swift-nio-ssh, repository does not exist or may require 'docker login': denied: requested access to the resource is denied runtime-setup Built container docker-runtime-setup-1 exited (0); runtime evidence skipped 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported 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 .swift 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.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D20 ADR Quality — Repository kind not determined
  • D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Swift 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. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rb, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 36 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • 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 — Swift suite
  • DM1 Aggregate boundaries — not scored for Swift: the sidecar flattens array/collection types (a child COLLECTION = legitimate membership vs a single embedded aggregate is indistinguishable), and aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike) — reported as guidance rather than measured
  • DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
  • DM3 Integration-event coupling — not scored for Swift: a cross-SwiftPM-target domain leak cannot be told apart in source from a legitimate shared-kernel/contracts module, and most repositories ship a single module — reported as guidance rather than measured
  • DM7 Repository granularity — not scored for Swift: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Swift 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
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X15 Unvalidated length from an untrusted reader — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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.
  • X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. In C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Swift was read, and it logs through none: `print` and `NSLog` take one finished line, and os's `Logger` keeps each interpolated value as its own argument, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through swift-log (`import Logging`) and `os_log` calls would be judged.
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 8 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×1
  • No assertions (empty test): testCrashes Vendor/SwiftTerm/Tests/SwiftTermTests/FuzzerTests.swift:60 — Test method has an empty body — it asserts nothing and exercises no code.
D10 · Test Quality · Assertions commented out · ×1
  • Assertions commented out: testInvalidMargins Vendor/SwiftTerm/Tests/SwiftTermTests/MeanTests.swift:40 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 750 finding(s)
D10 · Test Quality · No assertions · ×274
  • No assertions: testBindHostLimitObservationUsesNativePaywallRoute MultiplexTests/AddHostUIKitTests.swift:608 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testOverlongCSIParameterDoesNotTrap MultiplexTests/HostileInputTests.swift:83 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testOverlongOSCCommandNumberDoesNotTrap MultiplexTests/HostileInputTests.swift:87 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testNegativeOSC104PaletteIndexDoesNotTrap MultiplexTests/HostileInputTests.swift:91 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testEraseAboveAtTheBottomRightCellDoesNotTrap MultiplexTests/HostileInputTests.swift:95 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testUnterminatedOSCPayloadStaysBounded MultiplexTests/HostileInputTests.swift:101 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testManyEmptyCSIParametersStayBounded MultiplexTests/HostileInputTests.swift:107 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSixelWithoutALineTerminatorDoesNotTrap MultiplexTests/HostileInputTests.swift:124 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSixelOverlongRepeatCountDoesNotTrap MultiplexTests/HostileInputTests.swift:130 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testKittyDeleteRangeAboveUInt32DoesNotTrap MultiplexTests/HostileInputTests.swift:134 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testKittyOversizedPlacementDoesNotTrap MultiplexTests/HostileInputTests.swift:139 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testClusterControlKeyHoldsIntoKeyCommands MultiplexTests/KeyCommandRailHookTests.swift:37 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testExportLocalShellProofFixtures MultiplexTests/RemoteShellEnvelopeTests.swift:77 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testAppCatalogIsComplete MultiplexTests/StringCatalogTests.swift:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testInfoPlistCatalogIsComplete MultiplexTests/StringCatalogTests.swift:62 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testWidgetCatalogIsComplete MultiplexTests/StringCatalogTests.swift:66 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testGlassTokensResolveOnlyForTheDarkGlassTrait MultiplexTests/TallyPaletteTests.swift:7 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testScrollWithCorruptedYBase Vendor/SwiftTerm/Tests/SwiftTermTests/BufferTests.swift:459 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorUpDefaultParam Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:12 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorUpExplicitParam Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:19 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorUpClampedToTop Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:26 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorDownDefaultParam Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:35 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorDownExplicitParam Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:42 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorDownClampedToBottom Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:49 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCursorForwardDefaultParam Vendor/SwiftTerm/Tests/SwiftTermTests/CsiParameterParsingTests.swift:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 249 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×35
  • FileTooLong: Deck/FleetWall.swift Multiplex/Views/Deck/FleetWall.swift — FileTooLong — 3915 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3415 over it, 7.83× 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: Terminal/FileViewerPane.swift Multiplex/Views/Terminal/FileViewerPane.swift — FileTooLong — 2972 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2472 over it, 5.94× 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: Terminal/TerminalWindowUIKit.swift Multiplex/Views/Terminal/TerminalWindowUIKit.swift — FileTooLong — 2948 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2448 over it, 5.90× 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: Deck/AddHostSheet.swift Multiplex/Views/Deck/AddHostSheet.swift — FileTooLong — 2192 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: AddHostViewController (253-2201). The bar is 500 significant lines; this is 1692 over it, 4.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Terminal/TerminalKeyBar.swift Multiplex/Views/Terminal/TerminalKeyBar.swift — FileTooLong — 2158 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1658 over it, 4.32× 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: Terminal/UMDBarUIKit.swift Multiplex/Views/Terminal/UMDBarUIKit.swift — FileTooLong — 1514 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: UMDBarViewController (183-1432). The bar is 500 significant lines; this is 1014 over it, 3.03× 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: Services/TerminalSessionController.swift Multiplex/Services/TerminalSessionController.swift — FileTooLong — 1476 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TerminalSessionController (13-2503). The bar is 500 significant lines; this is 976 over it, 2.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: Terminal/ViewportPane.swift Multiplex/Views/Terminal/ViewportPane.swift — FileTooLong — 1451 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 951 over it, 2.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Settings/SettingsView.swift Multiplex/Views/Settings/SettingsView.swift — FileTooLong — 1393 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 893 over it, 2.79× 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: Shell/SingleWindowShell.swift Multiplex/Views/Shell/SingleWindowShell.swift — FileTooLong — 1335 significant lines (blank, comment-only and punctuation-only lines excluded), about 65% of them inside a single declaration: SingleWindowShellViewController (399-1607). The bar is 500 significant lines; this is 835 over it, 2.67× 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: Terminal/KeyCommandPanel.swift Multiplex/Views/Terminal/KeyCommandPanel.swift — FileTooLong — 1248 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 748 over it, 2.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Deck/BindPane.swift Multiplex/Views/Deck/BindPane.swift — FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 582 over it, 2.16× 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: Terminal/TalkbackComposer.swift Multiplex/Views/Terminal/TalkbackComposer.swift — FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: TalkbackComposerViewController (53-1050). The bar is 500 significant lines; this is 582 over it, 2.16× 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: Terminal/TerminalPaneUIKit.swift Multiplex/Views/Terminal/TerminalPaneUIKit.swift — FileTooLong — 1018 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 518 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: Services/ConnectionHub.swift Multiplex/Services/ConnectionHub.swift — FileTooLong — 904 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: HostConnectionModel (167-1689). The bar is 500 significant lines; this is 404 over it, 1.81× 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: Terminal/CustomAgentCommandPanel.swift Multiplex/Views/Terminal/CustomAgentCommandPanel.swift — FileTooLong — 869 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 369 over it, 1.74× 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: Deck/DeckWindow.swift Multiplex/Views/Deck/DeckWindow.swift — FileTooLong — 859 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: DeckWindowViewController (274-1193). The bar is 500 significant lines; this is 359 over it, 1.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: Terminal/TerminalVisionOrnaments.swift Multiplex/Views/Terminal/TerminalVisionOrnaments.swift — FileTooLong — 853 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 353 over it, 1.71× 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: Terminal/SidePanelUIKit.swift Multiplex/Views/Terminal/SidePanelUIKit.swift — FileTooLong — 849 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 349 over it, 1.70× 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: Terminal/AgentHelperStrip.swift Multiplex/Views/Terminal/AgentHelperStrip.swift — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 295 over it, 1.59× 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: Services/FileViewerController.swift Multiplex/Services/FileViewerController.swift — FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: FileViewerController (22-1202). The bar is 500 significant lines; this is 218 over it, 1.44× 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: Terminal/TerminalTabStrip.swift Multiplex/Views/Terminal/TerminalTabStrip.swift — FileTooLong — 699 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 199 over it, 1.40× 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: Services/HerdrProbe.swift Multiplex/Services/HerdrProbe.swift — FileTooLong — 694 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: HerdrProbe (56-1275). The bar is 500 significant lines; this is 194 over it, 1.39× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Settings/LicensesView.swift Multiplex/Views/Settings/LicensesView.swift — FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 190 over it, 1.38× 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: Services/EntitlementStore.swift Multiplex/Services/EntitlementStore.swift — FileTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: EntitlementStore (231-974). The bar is 500 significant lines; this is 97 over it, 1.19× 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.
  • + 10 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×27
  • ClassTooLong: AddHostViewController Multiplex/Views/Deck/AddHostSheet.swift:252 — ClassTooLong — 1481 significant lines (blank, comment-only and punctuation-only lines excluded), 65 methods. The bar is 400 significant lines; this is 1081 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: TerminalSessionController Multiplex/Services/TerminalSessionController.swift:11 — ClassTooLong — 1432 significant lines (blank, comment-only and punctuation-only lines excluded), 120 methods. The bar is 400 significant lines; this is 1032 over it, 3.58× 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: TerminalWindowViewController Multiplex/Views/Terminal/TerminalWindowUIKit.swift:296 — ClassTooLong — 1248 significant lines (blank, comment-only and punctuation-only lines excluded), 133 methods. The bar is 400 significant lines; this is 848 over it, 3.12× 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: FileViewerPaneViewController Multiplex/Views/Terminal/FileViewerPane.swift:103 — ClassTooLong — 1205 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 400 significant lines; this is 805 over it, 3.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: UMDBarViewController Multiplex/Views/Terminal/UMDBarUIKit.swift:182 — ClassTooLong — 921 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 521 over it, 2.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SingleWindowShellViewController Multiplex/Views/Shell/SingleWindowShell.swift:398 — ClassTooLong — 871 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 471 over it, 2.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: HostConnectionModel Multiplex/Services/ConnectionHub.swift:165 — ClassTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 423 over it, 2.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: FileViewerController Multiplex/Services/FileViewerController.swift:20 — ClassTooLong — 710 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 310 over it, 1.78× 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: TalkbackComposerViewController Multiplex/Views/Terminal/TalkbackComposer.swift:52 — ClassTooLong — 694 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 294 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SettingsViewController Multiplex/Views/Settings/SettingsView.swift:8 — ClassTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 279 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: FleetWallViewController Multiplex/Views/Deck/FleetWall.swift:244 — ClassTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 264 over it, 1.66× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DeckWindowViewController Multiplex/Views/Deck/DeckWindow.swift:273 — ClassTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 245 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: HerdrProbe Multiplex/Services/HerdrProbe.swift:56 — ClassTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 400 significant lines; this is 236 over it, 1.59× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: TerminalKeyBar Multiplex/Views/Terminal/TerminalKeyBar.swift:1103 — ClassTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 233 over it, 1.58× 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: TerminalGuidePictogramView Multiplex/Views/Terminal/TerminalGuidePictograms.swift:5 — ClassTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 168 over it, 1.42× 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: TmuxProbe Multiplex/Services/TmuxProbe.swift:83 — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 143 over it, 1.36× 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: TerminalSurfaceView Multiplex/Views/Terminal/SwiftTermView.swift:9 — ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 116 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MultiplexSceneDelegate Multiplex/App/MultiplexApp.swift:110 — ClassTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 110 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AgentSessionHistory Multiplex/Services/AgentSessionHistory.swift:42 — ClassTooLong — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 98 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: NewSessionViewController Multiplex/Views/Deck/FleetWall.swift:4253 — ClassTooLong — 488 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 88 over it, 1.22× 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: EntitlementStore Multiplex/Services/EntitlementStore.swift:229 — ClassTooLong — 461 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 61 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SidePanelHeaderView Multiplex/Views/Terminal/SidePanelUIKit.swift:516 — ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 52 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: DictationSession Multiplex/Services/DictationSession.swift:34 — ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 51 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AgentHelperStripViewController Multiplex/Views/Terminal/AgentHelperStrip.swift:67 — ClassTooLong — 442 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 42 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: TerminalPaneViewController Multiplex/Views/Terminal/TerminalPaneUIKit.swift:66 — ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 29 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 2 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×19
  • TooManyMethods: TerminalWindowViewController Multiplex/Views/Terminal/TerminalWindowUIKit.swift:296 — TooManyMethods — 133 methods. The bar is 30 methods; this is 103 over it, 4.43× 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: TerminalSessionController Multiplex/Services/TerminalSessionController.swift:11 — TooManyMethods — 120 methods. The bar is 30 methods; this is 90 over it, 4.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileViewerPaneViewController Multiplex/Views/Terminal/FileViewerPane.swift:103 — TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.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: AddHostViewController Multiplex/Views/Deck/AddHostSheet.swift:252 — TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SingleWindowShellViewController Multiplex/Views/Shell/SingleWindowShell.swift:398 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: DeckWindowViewController Multiplex/Views/Deck/DeckWindow.swift:273 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: TerminalKeyBar Multiplex/Views/Terminal/TerminalKeyBar.swift:1103 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TalkbackComposerViewController Multiplex/Views/Terminal/TalkbackComposer.swift:52 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UMDBarViewController Multiplex/Views/Terminal/UMDBarUIKit.swift:182 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileViewerController Multiplex/Services/FileViewerController.swift:20 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× 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: SettingsViewController Multiplex/Views/Settings/SettingsView.swift:8 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TerminalPaneViewController Multiplex/Views/Terminal/TerminalPaneUIKit.swift:66 — 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: MultiplexSceneDelegate Multiplex/App/MultiplexApp.swift:110 — 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: HostStore Multiplex/Services/HostStore.swift:13 — 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: HostConnectionModel Multiplex/Services/ConnectionHub.swift:165 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FleetWallViewController Multiplex/Views/Deck/FleetWall.swift:244 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TerminalTallyKeyControl Multiplex/Views/Terminal/TerminalKeyBar.swift:13 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TerminalGuidePictogramView Multiplex/Views/Terminal/TerminalGuidePictograms.swift:5 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TerminalTabStripView Multiplex/Views/Terminal/TerminalTabStrip.swift:87 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · MethodTooLong · ×15
  • MethodTooLong: TerminalWindowViewController.layoutNativeChrome Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393 — MethodTooLong — layoutNativeChrome runs 198 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× 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: FleetHostSectionView.render Multiplex/Views/Deck/FleetWall.swift:1803 — MethodTooLong — render runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: KeyCommandComposerView.build Multiplex/Views/Terminal/KeyCommandPanel.swift:1157 — MethodTooLong — build runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SingleWindowShellNativeLayout.resolve Multiplex/Views/Shell/SingleWindowShell.swift:155 — MethodTooLong — resolve runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
  • MethodTooLong: FleetHostRailView.configure Multiplex/Views/Deck/FleetWall.swift:2196 — MethodTooLong — configure runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TerminalSurfaceView.installTerminal Multiplex/Views/Terminal/SwiftTermView.swift:82 — MethodTooLong — installTerminal runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TerminalKeyBar.rebuildRow Multiplex/Views/Terminal/TerminalKeyBar.swift:1387 — MethodTooLong — rebuildRow runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CustomCommandRowView.init Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:906 — MethodTooLong — init runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) 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: HostConnectionModel.performRefresh Multiplex/Services/ConnectionHub.swift:518 — MethodTooLong — performRefresh runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ViewportUMDViewController.makeFileViewerRow Multiplex/Views/Terminal/ViewportPane.swift:1081 — MethodTooLong — makeFileViewerRow runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FileViewerPaneViewController.rebuildRail Multiplex/Views/Terminal/FileViewerPane.swift:817 — MethodTooLong — rebuildRail runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: SidePanelHeaderView.buildFileRow Multiplex/Views/Terminal/SidePanelUIKit.swift:780 — MethodTooLong — buildFileRow runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: BindCandidateRowView.build Multiplex/Views/Deck/BindPane.swift:860 — MethodTooLong — build runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FileViewerMarkdownContentView.makeBlock Multiplex/Views/Terminal/FileViewerPane.swift:3589 — MethodTooLong — makeBlock runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AddHostViewController.renderWorkingDirectories Multiplex/Views/Deck/AddHostSheet.swift:1436 — MethodTooLong — renderWorkingDirectories runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×12
  • Swallowed exception (caught, then discarded) Multiplex/Views/Deck/FleetWall.swift:871 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Views/Deck/FleetWall.swift:875 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Shared/SharedStateStore.swift:180 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/ConnectionHub.swift:950 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/Deadline.swift:26 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/NetworkChangeMonitor.swift:83 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/NetworkChangeMonitor.swift:92 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/RNNoiseModelStore.swift:266 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/TerminalSessionController.swift:749 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/Mosh/MoshProtobuf.swift:147 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/Mosh/MoshProtobuf.swift:226 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Multiplex/Services/Mosh/MoshProtobuf.swift:279 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×11
  • Duplicated block (6 lines × 2) Multiplex/Views/Deck/ConnectionStatsView.swift:578 — Multiplex/Views/Deck/ConnectionStatsView.swift:578-583 | Multiplex/Views/Settings/LicensesView.swift:289-294 — 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 `Multiplex/Views/Deck/ConnectionStatsView.swift:578` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1025 — Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1025-1030 | Multiplex/Views/Terminal/ShortcutPanel.swift:443-448 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1025` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Terminal/FileViewerPane.swift:451 — Multiplex/Views/Terminal/FileViewerPane.swift:451-456 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:284-289 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/FileViewerPane.swift:451` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Terminal/TerminalFocusArbiter.swift:653 — Multiplex/Views/Terminal/TerminalFocusArbiter.swift:653-658 | Multiplex/Views/Terminal/TerminalFocusArbiter.swift:663-668 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/TerminalFocusArbiter.swift:653` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2537 — Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2537-2542 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2571-2576 — both copies are in the same file, so extract the 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) Multiplex/Views/Terminal/UMDBarUIKit.swift:1977 — Multiplex/Views/Terminal/UMDBarUIKit.swift:1977-1982 | Multiplex/Views/Terminal/ViewportPane.swift:1847-1852 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) Multiplex/Views/Deck/FleetWall.swift:3937 — Multiplex/Views/Deck/FleetWall.swift:3937-3942 | Multiplex/Views/Terminal/FileViewerPane.swift:4107-4112 — 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 `Multiplex/Views/Deck/FleetWall.swift:3937` it begins part-way through the construct above it, so those 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, `Multiplex/Views/Terminal/FileViewerPane.swift:4105` calls `constraint` and `Multiplex/Views/Deck/FleetWall.swift:3935` 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 lines × 2) Multiplex/Design/Chassis.swift:533 — Multiplex/Design/Chassis.swift:533-538 | Multiplex/Views/Terminal/KeyCommandPanel.swift:633-638 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Multiplex/Views/Deck/ConnectionStatsView.swift:650 — Multiplex/Views/Deck/ConnectionStatsView.swift:650-655 | Multiplex/Views/Terminal/AgentHelperStrip.swift:926-931 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Multiplex/Views/Terminal/TerminalFilePathSheet.swift:75 — Multiplex/Views/Terminal/TerminalFilePathSheet.swift:75-80 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:206-211 — before extracting anything, compare `Multiplex/Views/Terminal/TerminalFilePathSheet.swift` and `Multiplex/Views/Terminal/TerminalLinkSheet.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) Multiplex/Services/HostStore.swift:304 — Multiplex/Services/HostStore.swift:304-309 | Multiplex/Services/ThemeStore.swift:213-218 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×11
  • Low cohesion: TerminalSessionController (LCOM4 12) Multiplex/Services/TerminalSessionController.swift:11 — TerminalSessionController's methods fall into 12 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 12 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: SSHConnection (LCOM4 10) Multiplex/Services/SSHConnection.swift:269 — SSHConnection's methods fall into 10 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 10 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: TerminalKeyBar (LCOM4 8) Multiplex/Views/Terminal/TerminalKeyBar.swift:1103 — TerminalKeyBar's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TerminalTabCell (LCOM4 7) Multiplex/Views/Terminal/TerminalTabStrip.swift:641 — TerminalTabCell's methods fall into 7 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 7 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: Coordinator (LCOM4 6) Multiplex/Views/Terminal/SwiftTermView.swift:429 — Coordinator'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: UIViewController (LCOM4 5) Multiplex/Design/Chassis.swift:114 — UIViewController's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: FleetSessionTileView (LCOM4 4) Multiplex/Views/Deck/FleetWall.swift:3038 — FleetSessionTileView'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.
  • Low cohesion: UIKitHostGuideSheetViewController (LCOM4 4) Multiplex/Views/Deck/HostGuideSheets.swift:131 — UIKitHostGuideSheetViewController'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.
  • Low cohesion: TerminalFullScreenExitButton (LCOM4 4) Multiplex/Views/Terminal/TerminalFullScreen.swift:76 — TerminalFullScreenExitButton'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.
  • Low cohesion: TerminalTallyKeyControl (LCOM4 4) Multiplex/Views/Terminal/TerminalKeyBar.swift:13 — TerminalTallyKeyControl'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.
  • Low cohesion: TerminalVisionControllerHost (LCOM4 4) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1204 — TerminalVisionControllerHost'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.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×10
  • Edited copy of a member (10 corresponding lines) Multiplex/AppIntents/OpenHostIntents.swift:214 — Multiplex/AppIntents/OpenHostIntents.swift:214-224 | Multiplex/AppIntents/OpenHostIntents.swift:281-290 — 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) Multiplex/Shared/AgentChoice.swift:57 — Multiplex/Shared/AgentChoice.swift:57-66 | Multiplex/Shared/ShortcutWorkingDirectoryOptions.swift:22-32 — 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) Multiplex/Services/TerminalSessionController.swift:1167 — Multiplex/Services/TerminalSessionController.swift:1167-1176 | Multiplex/Services/TerminalSessionController.swift:1189-1198 — 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) Multiplex/Design/Chassis.swift:897 — Multiplex/Design/Chassis.swift:897-914 | Multiplex/Views/Terminal/FileViewerFindBar.swift:151-160 — 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) Multiplex/Views/Deck/BindPane.swift:617 — Multiplex/Views/Deck/BindPane.swift:617-627 | Multiplex/Views/Deck/HostGuideSheets.swift:28-37 — 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) Multiplex/Services/TerminalSessionController.swift:1115 — Multiplex/Services/TerminalSessionController.swift:1115-1126 | Multiplex/Services/TerminalSessionController.swift:1202-1211 — 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) Multiplex/Views/SSHKeyPassphrasePrompt.swift:178 — Multiplex/Views/SSHKeyPassphrasePrompt.swift:178-187 | Multiplex/Views/Terminal/FileAttachMenu.swift:272-281 — 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) Multiplex/Views/Terminal/UMDBarUIKit.swift:733 — Multiplex/Views/Terminal/UMDBarUIKit.swift:733-743 | Multiplex/Views/Terminal/ViewportPane.swift:1348-1357 — 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) Multiplex/Views/Terminal/FileViewerPane.swift:1764 — Multiplex/Views/Terminal/FileViewerPane.swift:1764-1775 | Multiplex/Views/Terminal/ViewportPane.swift:628-637 — 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) Multiplex/Services/BackgroundRefresh.swift:97 — Multiplex/Services/BackgroundRefresh.swift:97-106 | Multiplex/Views/Terminal/TerminalKeyBar.swift:202-211 — 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×9
  • Hotspot: Multiplex/Views/Terminal/TerminalWindowUIKit.swift Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393 — Multiplex/Views/Terminal/TerminalWindowUIKit.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in TerminalWindowViewController.layoutNativeChrome at line 3393. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Terminal/TerminalWindowUIKit.swift`: 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: Multiplex/Views/Shell/SingleWindowShell.swift Multiplex/Views/Shell/SingleWindowShell.swift:155 — Multiplex/Views/Shell/SingleWindowShell.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in SingleWindowShellNativeLayout.resolve at line 155. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Shell/SingleWindowShell.swift`: 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: Multiplex/Views/Deck/FleetWall.swift Multiplex/Views/Deck/FleetWall.swift:1803 — Multiplex/Views/Deck/FleetWall.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in FleetHostSectionView.render at line 1803. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Deck/FleetWall.swift`: 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: Multiplex/Views/Terminal/UMDBarUIKit.swift Multiplex/Views/Terminal/UMDBarUIKit.swift:1038 — Multiplex/Views/Terminal/UMDBarUIKit.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in UMDBarViewController.makeOverflowMenu at line 1038. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Terminal/UMDBarUIKit.swift`: 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: Multiplex/Views/Terminal/TerminalKeyBar.swift Multiplex/Views/Terminal/TerminalKeyBar.swift:1387 — Multiplex/Views/Terminal/TerminalKeyBar.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in TerminalKeyBar.rebuildRow at line 1387. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Terminal/TerminalKeyBar.swift`: 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: Multiplex/Services/ConnectionHub.swift Multiplex/Services/ConnectionHub.swift:518 — Multiplex/Services/ConnectionHub.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in HostConnectionModel.performRefresh at line 518. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Services/ConnectionHub.swift`: 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: Multiplex/Views/Terminal/TerminalVisionOrnaments.swift Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198 — Multiplex/Views/Terminal/TerminalVisionOrnaments.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in TerminalVisionOrnamentState.update at line 198. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Terminal/TerminalVisionOrnaments.swift`: 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: Multiplex/Views/Terminal/FileViewerPane.swift Multiplex/Views/Terminal/FileViewerPane.swift:817 — Multiplex/Views/Terminal/FileViewerPane.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in FileViewerPaneViewController.rebuildRail at line 817. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Views/Terminal/FileViewerPane.swift`: 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: Multiplex/Models/ViewportReach.swift Multiplex/Models/ViewportReach.swift:88 — Multiplex/Models/ViewportReach.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in ViewportReach.ipv4MappedLiteral at line 88. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 19:41:01 +08:00' --until='2026-11-14 19:41:01 +08:00' --full-history --no-merges -- Multiplex/Models/ViewportReach.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×9
  • Duplicated block (7 lines × 2) Multiplex/AppIntents/OpenHostIntents.swift:265 — Multiplex/AppIntents/OpenHostIntents.swift:265-271 | MultiplexWidgets/HostWidgetConfigurationIntent.swift:112-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/AppIntents/OpenHostIntents.swift:265` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) Multiplex/Design/Chassis.swift:627 — Multiplex/Design/Chassis.swift:627-633 | Multiplex/Views/Deck/FleetWall.swift:4925-4931 — 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 `Multiplex/Design/Chassis.swift:627` it does not close everything it opens, so those exact lines 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) Multiplex/Services/TmuxProbe.swift:844 — Multiplex/Services/TmuxProbe.swift:844-850 | Multiplex/Services/TmuxProbe.swift:893-899 — both copies are in the same file, so extract the 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 (7 lines × 2) Multiplex/Views/Deck/FleetWall.swift:1151 — Multiplex/Views/Deck/FleetWall.swift:1151-1157 | Multiplex/Views/Deck/FleetWall.swift:1161-1167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/FleetWall.swift:1151` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:746 — Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:746-752 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:214-220 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:746` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Terminal/FileViewerPane.swift:1922 — Multiplex/Views/Terminal/FileViewerPane.swift:1922-1928 | Multiplex/Views/Terminal/KeyCommandPanel.swift:967-973 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/FileViewerPane.swift:1922` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Views/Settings/LicensesView.swift:891 — Multiplex/Views/Settings/LicensesView.swift:891-897 | Multiplex/Views/Settings/ThemeEditorView.swift:550-556 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:395 — Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:395-401 | Multiplex/Views/Terminal/FileViewerTreeColumn.swift:493-499 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) Multiplex/Views/Terminal/FileViewerPane.swift:1728 — Multiplex/Views/Terminal/FileViewerPane.swift:1728-1734 | Multiplex/Views/Terminal/FileViewerTreeColumn.swift:501-507 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×8
  • Duplicated block (9 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:1541 — Multiplex/Views/Deck/AddHostSheet.swift:1541-1549 | Multiplex/Views/Deck/AddHostSheet.swift:1719-1727 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) Multiplex/Views/Settings/LicensesView.swift:279 — Multiplex/Views/Settings/LicensesView.swift:279-287 | Multiplex/Views/Settings/LicensesView.swift:410-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Settings/LicensesView.swift:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Multiplex/Views/Settings/ProPaywallView.swift:249 — Multiplex/Views/Settings/ProPaywallView.swift:249-257 | Multiplex/Views/Settings/ProPaywallView.swift:335-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Settings/ProPaywallView.swift:249` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) Multiplex/Views/Settings/ProPaywallView.swift:308 — Multiplex/Views/Settings/ProPaywallView.swift:308-316 | Multiplex/Views/Terminal/ViewportPane.swift:783-791 — 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) Multiplex/Views/Settings/ReleaseNotesView.swift:200 — Multiplex/Views/Settings/ReleaseNotesView.swift:200-208 | Multiplex/Views/Settings/ReleaseNotesView.swift:466-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.
  • Duplicated block (9 lines × 2) Multiplex/Views/Shell/SingleWindowShell.swift:1857 — Multiplex/Views/Shell/SingleWindowShell.swift:1857-1865 | Multiplex/Views/Terminal/FileViewerPane.swift:3173-3181 — 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 `Multiplex/Views/Shell/SingleWindowShell.swift:1857` it does not close everything it opens, so those 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, `Multiplex/Views/Terminal/FileViewerPane.swift:3184` calls `apply` and `Multiplex/Views/Shell/SingleWindowShell.swift:1868` 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) Multiplex/Views/Terminal/KeyCommandPanel.swift:794 — Multiplex/Views/Terminal/KeyCommandPanel.swift:794-802 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1428-1436 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/KeyCommandPanel.swift:794` it does not close everything it opens, so those exact lines 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) Multiplex/Design/Chassis.swift:419 — Multiplex/Design/Chassis.swift:419-427 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1986-1994 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×7
  • Edited copy of a member (19 corresponding lines) Multiplex/Services/TmuxProbe.swift:394 — Multiplex/Services/TmuxProbe.swift:394-412 | Multiplex/Services/TmuxProbe.swift:435-455 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Services/ConnectionHub.swift:936 — Multiplex/Services/ConnectionHub.swift:936-955 | Multiplex/Services/Deadline.swift:13-31 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:2780 — Multiplex/Views/Deck/AddHostSheet.swift:2780-2798 | Multiplex/Views/Deck/BindPane.swift:1212-1230 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Views/Terminal/TerminalPaneUIKit.swift:692 — Multiplex/Views/Terminal/TerminalPaneUIKit.swift:692-710 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:780-802 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Views/Terminal/TerminalKeyBar.swift:784 — Multiplex/Views/Terminal/TerminalKeyBar.swift:784-802 | Multiplex/Views/Terminal/TerminalTabStrip.swift:445-466 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Services/BackgroundActivity.swift:42 — Multiplex/Services/BackgroundActivity.swift:42-60 | Multiplex/Services/TerminalWorkspace.swift:51-71 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Multiplex/Views/Settings/SettingsView.swift:457 — Multiplex/Views/Settings/SettingsView.swift:457-475 | Multiplex/Views/Settings/SettingsView.swift:497-519 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×7
  • Edited copy of a member (11 corresponding lines) Tools/mosh-interop/Shims.swift:27 — Multiplex/Services/Mosh/MoshBootstrap.swift:73-83 | Tools/mosh-interop/Shims.swift:27-40 — 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) Multiplex/Views/Terminal/TerminalKeyBar.swift:1649 — Multiplex/Views/Terminal/TerminalKeyBar.swift:1649-1659 | Multiplex/Views/Terminal/TerminalKeyBar.swift:2397-2408 — 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) Multiplex/Views/Deck/DeckWindow.swift:963 — Multiplex/Views/Deck/DeckWindow.swift:963-973 | Multiplex/Views/Deck/DeckWindow.swift:983-1000 — 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) Multiplex/Views/Terminal/TerminalKeyBar.swift:403 — Multiplex/Views/Terminal/TerminalKeyBar.swift:403-413 | Multiplex/Views/Terminal/TerminalTabStrip.swift:895-908 — 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) Multiplex/Services/HostStore.swift:259 — Multiplex/Services/HostStore.swift:259-269 | Multiplex/Services/HostStore.swift:271-281 — 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) Multiplex/Views/Deck/FleetWall.swift:3427 — Multiplex/Views/Deck/FleetWall.swift:3427-3437 | Multiplex/Views/Deck/FleetWall.swift:3439-3450 — 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) Multiplex/Services/HostStore.swift:480 — Multiplex/Services/HostStore.swift:480-490 | Multiplex/Services/HostStore.swift:497-509 — 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 · Duplicated block (8 lines × 2) · ×7
  • Duplicated block (8 lines × 2) Multiplex/Services/AgentSessionHistory.swift:199 — Multiplex/Services/AgentSessionHistory.swift:199-206 | Multiplex/Services/AgentSessionHistory.swift:226-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Services/AgentSessionHistory.swift:199` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Services/AttentionCenter.swift:108 — Multiplex/Services/AttentionCenter.swift:108-115 | Multiplex/Services/AttentionCenter.swift:134-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Services/AttentionCenter.swift:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:2305 — Multiplex/Views/Deck/AddHostSheet.swift:2305-2312 | Multiplex/Views/Settings/SettingsView.swift:1023-1030 — 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 `Multiplex/Views/Deck/AddHostSheet.swift:2305` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/AgentPromptSheet.swift:551 — Multiplex/Views/Deck/AgentPromptSheet.swift:551-558 | Multiplex/Views/Deck/FleetWall.swift:5376-5383 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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) Multiplex/Views/Deck/FleetWall.swift:2211 — Multiplex/Views/Deck/FleetWall.swift:2211-2218 | Multiplex/Views/Deck/FleetWall.swift:2378-2385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/FleetWall.swift:2211` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Views/Terminal/FileViewerPane.swift:2272 — Multiplex/Views/Terminal/FileViewerPane.swift:2272-2279 | Multiplex/Views/Terminal/FileViewerPane.swift:3322-3329 — both copies are in the same file, so extract the 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) Multiplex/Views/Terminal/UMDBarUIKit.swift:486 — Multiplex/Views/Terminal/UMDBarUIKit.swift:486-493 | Multiplex/Views/Terminal/UMDBarUIKit.swift:863-870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/UMDBarUIKit.swift:486` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×6
  • Edited copy of a member (13 corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:2932 — Multiplex/Views/Deck/AddHostSheet.swift:2932-2944 | Multiplex/Views/Settings/SettingsView.swift:1842-1854 — 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) Multiplex/Views/Terminal/TerminalKeyBar.swift:1671 — Multiplex/Views/Terminal/TerminalKeyBar.swift:1671-1683 | Multiplex/Views/Terminal/TerminalKeyBar.swift:2434-2446 — 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) Multiplex/Views/Terminal/AgentHistoryPanel.swift:396 — Multiplex/Views/Terminal/AgentHistoryPanel.swift:396-409 | Multiplex/Views/Terminal/FileViewerPane.swift:2234-2246 — 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) Multiplex/Services/WidgetStatePublisher.swift:63 — Multiplex/Services/WidgetStatePublisher.swift:63-75 | Multiplex/Services/WidgetStatePublisher.swift:84-96 — 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) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:653 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:653-671 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:673-685 — 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) Tools/bake-vision-icon.swift:231 — Tools/bake-vision-icon.swift:231-243 | Tools/bake-vision-icon.swift:244-256 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×5
  • Edited copy of a member (18 corresponding lines) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:167 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:167-185 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:449-474 — 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) Multiplex/Views/Deck/FleetWall.swift:4755 — Multiplex/Views/Deck/FleetWall.swift:4755-4772 | Multiplex/Views/Deck/FleetWall.swift:4774-4792 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2105 — Multiplex/Views/Deck/AddHostSheet.swift:2105-2122 | Multiplex/Views/Deck/AddHostSheet.swift:2124-2141 — 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) Multiplex/Views/Settings/SettingsView.swift:477 — Multiplex/Views/Settings/SettingsView.swift:477-494 | Multiplex/Views/Settings/SettingsView.swift:521-543 — 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) Multiplex/Views/Terminal/UMDBarUIKit.swift:745 — Multiplex/Views/Terminal/UMDBarUIKit.swift:745-762 | Multiplex/Views/Terminal/UMDBarUIKit.swift:764-782 — 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 · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Multiplex/App/UIKitSceneRootViewController.swift:105 — Multiplex/App/UIKitSceneRootViewController.swift:105-170 | Multiplex/App/UIKitSceneRootViewController.swift:390-404 | Multiplex/Views/Deck/BindPane.swift:1350-1390 | Multiplex/Views/Deck/FleetWall.swift:91-117 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2211 — Multiplex/Views/Deck/AddHostSheet.swift:2211-2275 | Multiplex/Views/Deck/BindPane.swift:650-712 | Multiplex/Views/Settings/SettingsView.swift:940-1015 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1243-1365 — 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) Multiplex/Views/Deck/FleetWall.swift:2180 — Multiplex/Views/Deck/FleetWall.swift:2180-2191 | Multiplex/Views/Terminal/FileViewerPane.swift:2028-2068 | Multiplex/Views/Terminal/FileViewerPane.swift:3056-3080 | Multiplex/Views/Terminal/KeyCommandPanel.swift:694-710 — 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) Multiplex/Views/Deck/FleetWall.swift:2893 — Multiplex/Views/Deck/FleetWall.swift:2893-2910 | Multiplex/Views/Terminal/FileViewerPane.swift:1744-1757 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:356-376 | Multiplex/Views/Terminal/ViewportPane.swift:610-623 — 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) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:114 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:114-142 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:227-267 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:357-447 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:561-572 — 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 (8 corresponding lines) · ×5
  • Edited copy of a member (8 corresponding lines) Multiplex/Services/TmuxProbe.swift:843 — Multiplex/Services/TmuxProbe.swift:843-850 | Multiplex/Services/TmuxProbe.swift:892-899 — 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) Multiplex/Views/Terminal/KeyCommandPanel.swift:418 — Multiplex/Views/Terminal/KeyCommandPanel.swift:418-425 | Multiplex/Views/Terminal/ShortcutPanel.swift:371-380 — 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) Multiplex/Views/Terminal/TerminalFilePathSheet.swift:65 — Multiplex/Views/Terminal/TerminalFilePathSheet.swift:65-73 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:197-204 — 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) Multiplex/Views/Settings/LicensesView.swift:899 — Multiplex/Views/Settings/LicensesView.swift:899-906 | Multiplex/Views/Settings/ReleaseNotesView.swift:547-554 — 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) Multiplex/Views/Terminal/TerminalKeyBar.swift:452 — Multiplex/Views/Terminal/TerminalKeyBar.swift:452-459 | Multiplex/Views/Terminal/TerminalTabStrip.swift:995-1002 — 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 · Duplicated block (8 lines × 3) · ×5
  • Duplicated block (8 lines × 3) Multiplex/Views/Deck/AddHostSheet.swift:2222 — Multiplex/Views/Deck/AddHostSheet.swift:2222-2229 | Multiplex/Views/Deck/BindPane.swift:663-670 | Multiplex/Views/Settings/SettingsView.swift:953-960 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2222` 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, `Multiplex/Views/Settings/SettingsView.swift:962` calls `UIStackView` and `Multiplex/Views/Deck/BindPane.swift:672` 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 × 3) Multiplex/Views/Deck/FleetWall.swift:5176 — Multiplex/Views/Deck/FleetWall.swift:5176-5183 | Multiplex/Views/Shell/SingleWindowShell.swift:1860-1867 | Multiplex/Views/Terminal/FileViewerPane.swift:3176-3183 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/FileViewerPane.swift:3184` calls `apply` and `Multiplex/Views/Shell/SingleWindowShell.swift:1868` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) Multiplex/Views/Settings/LicensesView.swift:419 — Multiplex/Views/Settings/LicensesView.swift:419-426 | Multiplex/Views/Settings/ReleaseNotesView.swift:165-172 | Multiplex/Views/Terminal/DictationChrome.swift:95-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Settings/LicensesView.swift:419` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 3) Multiplex/Services/TmuxProbe.swift:916 — Multiplex/Models/AgentSignature.swift:124-131 | Multiplex/Models/SessionScript.swift:30-37 | Multiplex/Services/TmuxProbe.swift:916-923 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Models/AgentSignature.swift:124` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Views/Terminal/TerminalGuideViewController.swift:526 — Multiplex/Views/Terminal/TerminalGuideViewController.swift:526-533 | Multiplex/Views/Terminal/UMDBarUIKit.swift:2021-2028 | Multiplex/Views/Terminal/ViewportPane.swift:1839-1846 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) Multiplex/Views/Terminal/KeyCommandPanel.swift:1499 — Multiplex/Views/Terminal/KeyCommandPanel.swift:1499-1518 | Multiplex/Views/Terminal/UMDBarUIKit.swift:2059-2082 — 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) Multiplex/App/UIKitSceneRootViewController.swift:585 — Multiplex/App/UIKitSceneRootViewController.swift:585-604 | Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1246-1276 — 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) Multiplex/Views/Deck/DeckWindow.swift:1028 — Multiplex/Views/Deck/DeckWindow.swift:1028-1054 | Multiplex/Views/Deck/FleetWall.swift:1118-1137 — 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) Multiplex/Views/Terminal/AgentHistoryPanel.swift:60 — Multiplex/Views/Terminal/AgentHistoryPanel.swift:60-79 | Multiplex/Views/Terminal/ShortcutPanel.swift:39-58 — 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 (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:2305 — Multiplex/Views/Deck/AddHostSheet.swift:2305-2316 | Multiplex/Views/Settings/SettingsView.swift:1023-1034 — 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) Multiplex/Views/Terminal/TerminalLinkSheet.swift:323 — Multiplex/Views/Terminal/TerminalLinkSheet.swift:323-334 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:336-347 — 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) Multiplex/Services/EntitlementStore.swift:142 — Multiplex/Services/EntitlementStore.swift:142-153 | Multiplex/Services/EntitlementStore.swift:155-166 — 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) Multiplex/Views/Terminal/TerminalFullScreen.swift:169 — Multiplex/Views/Terminal/TerminalFullScreen.swift:169-180 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:554-568 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) Multiplex/Views/Deck/FleetWall.swift:1149 — Multiplex/Views/Deck/FleetWall.swift:1149-1157 | Multiplex/Views/Deck/FleetWall.swift:1159-1167 — 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) Multiplex/Views/Terminal/ViewportPane.swift:1359 — Multiplex/Views/Terminal/ViewportPane.swift:1359-1367 | Multiplex/Views/Terminal/ViewportPane.swift:1580-1588 — 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) Multiplex/Views/Deck/FleetWall.swift:1139 — Multiplex/Views/Deck/FleetWall.swift:1139-1147 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1556-1569 — 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) Multiplex/Views/Settings/SettingsView.swift:861 — Multiplex/Views/Settings/SettingsView.swift:861-874 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3924-3932 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×4
  • Edited copy of a member (14 corresponding lines) Multiplex/Views/Terminal/FileViewerPane.swift:1409 — Multiplex/Views/Terminal/FileViewerPane.swift:1409-1422 | Multiplex/Views/Terminal/FileViewerPane.swift:1427-1443 — 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) MultiplexWidgets/FleetWidget.swift:11 — MultiplexWidgets/FleetWidget.swift:11-24 | MultiplexWidgets/HostWidget.swift:13-27 — 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) Multiplex/Views/Terminal/TerminalFilePathSheet.swift:105 — Multiplex/Views/Terminal/TerminalFilePathSheet.swift:105-120 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:237-250 — 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) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1026 — Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1026-1039 | Multiplex/App/UIKitSceneRootViewController.swift:524-537 — 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 · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:2780 — Multiplex/Views/Deck/AddHostSheet.swift:2780-2790 | Multiplex/Views/Deck/BindPane.swift:1212-1222 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Deck/AddHostSheet.swift:2780` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/AddHostSheet.swift:2934 — Multiplex/Views/Deck/AddHostSheet.swift:2934-2944 | Multiplex/Views/Settings/SettingsView.swift:1844-1854 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Multiplex/Views/Settings/ProPaywallView.swift:85 — Multiplex/Views/Settings/ProPaywallView.swift:85-96 | Multiplex/Views/Settings/SettingsView.swift:108-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Settings/ProPaywallView.swift:85` 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) Multiplex/Views/Terminal/AgentHelperStrip.swift:823 — Multiplex/Views/Terminal/AgentHelperStrip.swift:823-833 | Multiplex/Views/Terminal/AgentHelperStrip.swift:869-879 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/AgentHelperStrip.swift:823` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×4
  • Duplicated block (8 lines × 4) Multiplex/Views/Deck/AddHostSheet.swift:2214 — Multiplex/Views/Deck/AddHostSheet.swift:2214-2221 | Multiplex/Views/Deck/BindPane.swift:655-662 | Multiplex/Views/Deck/FleetWall.swift:4904-4911 | Multiplex/Views/Settings/SettingsView.swift:945-952 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Multiplex/Views/Deck/AgentPromptSheet.swift:630 — Multiplex/Views/Deck/AgentPromptSheet.swift:630-637 | Multiplex/Views/Deck/FleetWall.swift:5339-5346 | Multiplex/Views/Terminal/KeyCommandPanel.swift:795-802 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1429-1436 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AgentPromptSheet.swift:630` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 4) Multiplex/Views/Deck/FleetWall.swift:2182 — Multiplex/Views/Deck/FleetWall.swift:2182-2189 | Multiplex/Views/Terminal/FileViewerPane.swift:2060-2067 | Multiplex/Views/Terminal/FileViewerPane.swift:3072-3079 | Multiplex/Views/Terminal/KeyCommandPanel.swift:701-708 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Deck/FleetWall.swift:2190` calls `addInteraction`, `UIContextMenuInteraction` and `Multiplex/Views/Terminal/FileViewerPane.swift:2068` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 4) Multiplex/Views/Deck/FleetWall.swift:2901 — Multiplex/Views/Deck/FleetWall.swift:2901-2908 | Multiplex/Views/Terminal/FileViewerPane.swift:1749-1756 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:368-375 | Multiplex/Views/Terminal/ViewportPane.swift:613-620 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/ViewportPane.swift:622` calls `setText` and `Multiplex/Views/Terminal/TerminalGuideViewController.swift:376` 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) Multiplex/Design/Chassis.swift:357 — Multiplex/Design/Chassis.swift:357-363 | Multiplex/Views/Deck/FleetWall.swift:3063-3069 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1948-1954 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:357` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/AddHostSheet.swift:2332 — Multiplex/Views/Deck/AddHostSheet.swift:2332-2338 | Multiplex/Views/Deck/AgentPromptSheet.swift:294-300 | Multiplex/Views/Deck/BindPane.swift:893-899 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Deck/AddHostSheet.swift:2332` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/FleetWall.swift:5041 — Multiplex/Views/Deck/FleetWall.swift:5041-5047 | Multiplex/Views/Deck/FleetWall.swift:5103-5109 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:798-804 — 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 `Multiplex/Views/Deck/FleetWall.swift:5041` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/FleetWall.swift:3175 — Multiplex/Views/Deck/FleetWall.swift:3175-3181 | Multiplex/Views/Terminal/TerminalKeyBar.swift:415-421 | Multiplex/Views/Terminal/TerminalTabStrip.swift:910-916 — 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.
D10 · Test Quality · Skipped test · ×3
  • Skipped test: testPressAndDragReordersTheKeys MultiplexUITests/ArrangeKeysUITests.swift:21 — Skipped — throws XCTSkip
  • Skipped test: testCheckedLaunchWriteAndResize Vendor/SwiftTerm/Tests/SwiftTermTests/LocalProcessLifecycleTests.swift:590 — Skipped — throws XCTSkip
  • Skipped test: testPendingWriteCompletesWhenProcessIsReleased Vendor/SwiftTerm/Tests/SwiftTermTests/LocalProcessLifecycleTests.swift:688 — Skipped — throws XCTSkip
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×3
  • Edited copy of a member (21 corresponding lines) Multiplex/Views/Terminal/AgentHelperStrip.swift:817 — Multiplex/Views/Terminal/AgentHelperStrip.swift:817-837 | Multiplex/Views/Terminal/AgentHelperStrip.swift:863-892 — 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) Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:695 — Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:695-715 | Multiplex/Views/Terminal/ShortcutPanel.swift:424-453 — 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) Multiplex/Services/AgentSessionHistory.swift:194 — Multiplex/Services/AgentSessionHistory.swift:194-214 | Multiplex/Services/AgentSessionHistory.swift:216-240 — 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 (23 corresponding lines) · ×3
  • Edited copy of a member (23 corresponding lines) Multiplex/Design/TallyEditorControls.swift:132 — Multiplex/Design/TallyEditorControls.swift:132-154 | Multiplex/Views/Settings/SettingsView.swift:1392-1414 — 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) Multiplex/Views/Terminal/TerminalWindow.swift:90 — Multiplex/Views/Terminal/TerminalWindow.swift:90-112 | Multiplex/Views/Terminal/TerminalWindow.swift:200-227 — 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) Multiplex/Views/Terminal/TerminalLinkSheet.swift:424 — Multiplex/Views/Terminal/TerminalLinkSheet.swift:424-446 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:448-494 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) Multiplex/Views/Terminal/FileViewerPane.swift:797 — Multiplex/Views/Terminal/FileViewerPane.swift:797-813 | Multiplex/Views/Terminal/FileViewerTreeColumn.swift:509-534 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2436 — Multiplex/Views/Deck/AddHostSheet.swift:2436-2452 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:820-836 — 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) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2983 — Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2983-2999 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3076-3095 — 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 (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) Multiplex/Views/Terminal/TerminalWindow.swift:241 — Multiplex/Views/Terminal/TerminalWindow.swift:241-256 | Multiplex/Views/Terminal/TerminalWindow.swift:267-286 — 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) Multiplex/Views/Settings/SettingsView.swift:814 — Multiplex/Views/Settings/SettingsView.swift:814-829 | Multiplex/Views/Settings/SettingsView.swift:835-850 — 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) Multiplex/Views/Terminal/TerminalKeyBar.swift:1880 — Multiplex/Views/Terminal/TerminalKeyBar.swift:1880-1900 | Multiplex/Views/Terminal/TerminalKeyBar.swift:1902-1917 — 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 (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) Multiplex/Services/FileViewerAudioVolumeStore.swift:19 — Multiplex/Services/FileViewerAudioVolumeStore.swift:19-24 | Multiplex/Services/FileViewerTextScaleStore.swift:23-28 — 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) Multiplex/Views/Settings/ReleaseNotesView.swift:556 — Multiplex/Views/Settings/ReleaseNotesView.swift:556-561 | Multiplex/Views/Settings/SettingsView.swift:1818-1824 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2673 — Multiplex/Views/Deck/AddHostSheet.swift:2673-2678 | Multiplex/Views/Deck/HostGuideSheets.swift:39-44 — 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) · ×3
  • Edited copy of a member (4 corresponding lines) Multiplex/Services/ThemeStore.swift:207 — Multiplex/Services/ThemeStore.swift:207-211 | Multiplex/Services/HostStore.swift:299-302 — 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) Multiplex/Views/Terminal/SidePanelUIKit.swift:499 — Multiplex/Views/Terminal/SidePanelUIKit.swift:499-502 | Multiplex/Views/Terminal/TerminalLinkHoverOverlay.swift:56-59 — 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) Multiplex/Views/Terminal/TerminalGuideViewController.swift:549 — Multiplex/Views/Terminal/TerminalGuideViewController.swift:549-552 | Multiplex/Views/Terminal/ViewportPane.swift:1863-1871 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×3
  • Edited copy of a member (3 corresponding lines) Multiplex/Design/Chassis.swift:58 — Multiplex/Design/Chassis.swift:58-60 | Multiplex/Views/Terminal/FileViewerTextView.swift:49-55 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Multiplex/Views/Terminal/AgentHelperStrip.swift:852 — Multiplex/Views/Terminal/AgentHelperStrip.swift:852-854 | Multiplex/Views/Terminal/TerminalFullScreen.swift:182-184 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Multiplex/Services/ConnectionStatsSetting.swift:14 — Multiplex/Services/ConnectionStatsSetting.swift:14-16 | Multiplex/Services/NoiseReductionSetting.swift:11-13 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) Multiplex/Views/Deck/AddHostSheet.swift:2262 — Multiplex/Views/Deck/AddHostSheet.swift:2262-2270 | Multiplex/Views/Terminal/KeyCommandPanel.swift:1159-1167 | Multiplex/Views/Terminal/ViewportPane.swift:1769-1777 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2262` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Deck/FleetWall.swift:3720 — Multiplex/Views/Deck/FleetWall.swift:3720-3728 | Multiplex/Views/Deck/FleetWall.swift:3929-3937 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1271-1279 — 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 `Multiplex/Views/Deck/FleetWall.swift:3720` it does not close everything it opens, so those exact lines 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) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:202 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:202-210 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:295-303 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:488-496 — 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 `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:202` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:499` calls `drawPastePermission` and `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:212` 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×3
  • Duplicated block (6 lines × 3) Multiplex/Design/TallyEditorControls.swift:209 — Multiplex/Design/TallyEditorControls.swift:209-215 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1176-1182 | Multiplex/Views/Terminal/KeyCommandPanel.swift:1696-1701 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2604 — Multiplex/Views/Deck/AddHostSheet.swift:2604-2609 | Multiplex/Views/Settings/SettingsView.swift:1257-1262 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:883-888 — 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) Multiplex/Views/Terminal/AgentHelperStrip.swift:1040 — Multiplex/Views/Terminal/AgentHelperStrip.swift:1040-1045 | Multiplex/Views/Terminal/TalkbackComposer.swift:1219-1224 | Multiplex/Views/Terminal/TerminalKeyBar.swift:176-181 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) Multiplex/Views/Terminal/FileViewerPane.swift:540 — Multiplex/Views/Terminal/FileViewerPane.swift:540-544 | Multiplex/Views/Terminal/ViewportPane.swift:327-331 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:2774 — Multiplex/Views/Deck/AddHostSheet.swift:2774-2778 | Multiplex/Views/Deck/BindPane.swift:1206-1210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:647 — Multiplex/Views/Deck/AddHostSheet.swift:647-651 | Multiplex/Views/Shell/SingleWindowShell.swift:983-987 — 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 `Multiplex/Views/Deck/AddHostSheet.swift:647` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: SingleWindowShellPolicy.swift ↔ TerminalKeyBar.swift Multiplex/Models/SingleWindowShellPolicy.swift:1 — `Multiplex/Models/SingleWindowShellPolicy.swift` and `Multiplex/Views/Terminal/TerminalKeyBar.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `125b6e79` Run the iPhone Duo key rail through the side strip, off the corners; `cf10c2e5` Terminal: full screen from the ⋯ menu (#72); `b86f69a2` Give herdr tabs their own shortcut panel (HRDR) — run `git show` on any of them.
  • Change coupling: ProPaywallView.swift ↔ AgentHelperStrip.swift Multiplex/Views/Settings/ProPaywallView.swift:1 — `Multiplex/Views/Settings/ProPaywallView.swift` and `Multiplex/Views/Terminal/AgentHelperStrip.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `458a56f4` Put form dialogs on opaque chassis and make visionOS presentations fo…; `3980a4ee` Agent History: Claude Code prompt history with exact jump-back (Pro) …; `666ae81e` Add custom agent helper commands — run `git show` on any of them.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Multiplex/Design/Chassis.swift:328 — Multiplex/Design/Chassis.swift:328-389 | Multiplex/Views/Deck/FleetWall.swift:3058-3087 | Multiplex/Views/Settings/ProPaywallView.swift:527-580 | Multiplex/Views/Settings/SettingsView.swift:1421-1464 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1937-1984 — 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) Multiplex/Views/Settings/LicensesView.swift:240 — Multiplex/Views/Settings/LicensesView.swift:240-269 | Multiplex/Views/Terminal/AgentHelperStrip.swift:424-510 | Multiplex/Views/Terminal/AgentHistoryPanel.swift:268-324 | Multiplex/Views/Terminal/FileViewerPane.swift:4027-4135 | Multiplex/Views/Terminal/ShortcutPanel.swift:93-142 — 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 (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:280 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:280-304 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:476-497 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2541 — Multiplex/Views/Deck/AddHostSheet.swift:2541-2563 | Multiplex/Views/Settings/SettingsView.swift:1208-1229 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 11+ corresponding lines) Multiplex/Views/Terminal/AgentHistoryPanel.swift:415 — Multiplex/Views/Terminal/AgentHistoryPanel.swift:415-426 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:606-617 | Multiplex/Views/Terminal/ShortcutPanel.swift:580-590 — 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) Multiplex/Views/Terminal/FileViewerPane.swift:548 — Multiplex/Views/Terminal/FileViewerPane.swift:548-558 | Multiplex/Views/Terminal/TerminalKeyBar.swift:1370-1385 | Multiplex/Views/Terminal/ViewportPane.swift:214-224 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) Multiplex/Views/Deck/DeckWindow.swift:936 — Multiplex/Views/Deck/DeckWindow.swift:936-942 | Multiplex/Views/Deck/DeckWindow.swift:975-981 — 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) Multiplex/Services/ViewportController.swift:58 — Multiplex/Models/ViewportReach.swift:147-153 | Multiplex/Services/ViewportController.swift:58-64 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) Multiplex/Views/Terminal/FileViewerPane.swift:3911 — Multiplex/Views/Terminal/FileViewerPane.swift:3911-3915 | Multiplex/Views/Terminal/FileViewerTextView.swift:357-361 — 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) Multiplex/Views/Deck/AddHostSheet.swift:2470 — Multiplex/Views/Deck/AddHostSheet.swift:2470-2474 | Multiplex/Views/Deck/FleetWall.swift:5058-5062 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) Multiplex/Views/Deck/AgentPromptSheet.swift:567 — Multiplex/Views/Deck/AgentPromptSheet.swift:567-583 | Multiplex/Views/Deck/FleetWall.swift:5389-5405 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Deck/AgentPromptSheet.swift:567` it does not close everything it opens, so those 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, `Multiplex/Views/Deck/FleetWall.swift:5406` calls `constraint` and `Multiplex/Views/Deck/AgentPromptSheet.swift:584` 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 (17 lines × 2) Multiplex/Views/Terminal/ViewportPane.swift:433 — Multiplex/Views/Terminal/ViewportPane.swift:433-449 | Multiplex/Views/Terminal/ViewportPane.swift:1527-1543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/ViewportPane.swift:433` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:169 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:169-184 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:452-467 — both copies are in the same file, so extract the 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 lines × 2) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3595 — Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3595-3610 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3645-3660 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×2
  • Duplicated block (13–14 lines × 2) Multiplex/Views/Settings/FAQView.swift:24 — Multiplex/Views/Settings/FAQView.swift:24-37 | Multiplex/Views/Settings/ProPaywallView.swift:82-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13–14 lines × 2) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198 — Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198-211 | Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:352-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) Multiplex/Design/TallyEditorControls.swift:136 — Multiplex/Design/TallyEditorControls.swift:136-148 | Multiplex/Views/Settings/SettingsView.swift:1396-1408 — 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 `Multiplex/Design/TallyEditorControls.swift:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) Multiplex/Views/Deck/AgentPromptSheet.swift:377 — Multiplex/Views/Deck/AgentPromptSheet.swift:377-389 | Multiplex/Views/Deck/FleetWall.swift:4708-4720 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) Multiplex/Views/Deck/AgentPromptSheet.swift:363 — Multiplex/Views/Deck/AgentPromptSheet.swift:363-374 | Multiplex/Views/Deck/FleetWall.swift:4832-4842 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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–12 lines × 2) Multiplex/Views/Deck/BindPane.swift:697 — Multiplex/Views/Deck/BindPane.swift:697-708 | Multiplex/Views/Deck/FleetWall.swift:4962-4972 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Deck/BindPane.swift:697` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×2
  • Duplicated block (9–11 lines × 2) Multiplex/Design/Chassis.swift:353 — Multiplex/Design/Chassis.swift:353-363 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1946-1954 — 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 `Multiplex/Design/Chassis.swift:353` it begins part-way through the construct above it, so those exact lines 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–11 lines × 2) Multiplex/Views/Settings/SettingsView.swift:104 — Multiplex/Views/Settings/SettingsView.swift:104-112 | Multiplex/Views/Terminal/TerminalFilePathSheet.swift:105-115 — 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 `Multiplex/Views/Settings/SettingsView.swift:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 7) · ×2
  • Duplicated block (10 lines × 7) Multiplex/Views/Deck/ConnectionStatsView.swift:58 — Multiplex/Views/Deck/ConnectionStatsView.swift:58-68 | Multiplex/Views/Deck/HostGuideSheets.swift:163-172 | Multiplex/Views/Settings/FAQView.swift:29-38 | Multiplex/Views/Settings/ProPaywallView.swift:85-95 | Multiplex/Views/Settings/ReleaseNotesView.swift:346-356 | Multiplex/Views/Settings/SettingsView.swift:108-117 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:42-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Deck/ConnectionStatsView.swift:72` calls `observe` and `Multiplex/Views/Deck/HostGuideSheets.swift:176` 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 × 7) Multiplex/Views/Deck/DeckWindow.swift:21 — Multiplex/Views/Deck/DeckWindow.swift:21-32 | Multiplex/Views/Terminal/AgentHelperStrip.swift:1083-1095 | Multiplex/Views/Terminal/AgentHelperStrip.swift:1103-1115 | Multiplex/Views/Terminal/AgentHelperStrip.swift:1123-1132 | Multiplex/Views/Terminal/TerminalWindow.swift:73-82 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1451-1463 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1471-1483 — there are 7 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×2
  • Duplicated block (9–10 lines × 5) Multiplex/Design/Chassis.swift:639 — Multiplex/Design/Chassis.swift:639-648 | Multiplex/Views/Deck/AddHostSheet.swift:2238-2246 | Multiplex/Views/Deck/BindPane.swift:677-685 | Multiplex/Views/Deck/FleetWall.swift:4942-4950 | Multiplex/Views/Settings/SettingsView.swift:968-976 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:639` it does not close everything it opens, so those exact lines 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 × 5) Multiplex/Views/Deck/AddHostSheet.swift:2757 — Multiplex/Views/Deck/AddHostSheet.swift:2757-2765 | Multiplex/Views/Deck/BindPane.swift:1189-1197 | Multiplex/Views/Deck/FleetWall.swift:220-228 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:215-223 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1353-1362 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2757` it does not close everything it opens, so those 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, `Multiplex/Views/Deck/AddHostSheet.swift:2768` calls `refreshPresentation` and `Multiplex/Views/Deck/FleetWall.swift:231` 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.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×2
  • Duplicated block (7–10 lines × 2) Tools/mosh-interop/Shims.swift:31 — Multiplex/Services/Mosh/MoshBootstrap.swift:77-83 | Tools/mosh-interop/Shims.swift:31-40 — 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 `Multiplex/Services/Mosh/MoshBootstrap.swift:77` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7–10 lines × 2) Multiplex/Views/Deck/FleetWall.swift:3810 — Multiplex/Views/Deck/FleetWall.swift:3810-3819 | Multiplex/Views/Deck/FleetWall.swift:3898-3904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/FleetWall.swift:3810` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) Multiplex/Views/Deck/AddHostSheet.swift:2341 — Multiplex/Views/Deck/AddHostSheet.swift:2341-2349 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1033-1042 — 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 `Multiplex/Views/Deck/AddHostSheet.swift:2341` it begins part-way through the construct above it, so those exact lines 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) Multiplex/Views/Terminal/AgentHistoryPanel.swift:415 — Multiplex/Views/Terminal/AgentHistoryPanel.swift:415-423 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:606-615 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/AgentHistoryPanel.swift:415` it does not close everything it opens, so those 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:295 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:295-304 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:488-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:295` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) Multiplex/Views/Terminal/TerminalDrop.swift:20 — Multiplex/Views/Terminal/TerminalDrop.swift:20-29 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:699-708 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) Multiplex/Design/Chassis.swift:509 — Multiplex/Design/Chassis.swift:509-517 | Multiplex/Design/TallyEditorControls.swift:58-66 | Multiplex/Views/Deck/FleetWall.swift:2611-2619 | Multiplex/Views/Deck/FleetWall.swift:5258-5266 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:509` it does not close everything it opens, so those exact lines 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 × 4) Multiplex/Views/Deck/AddHostSheet.swift:2911 — Multiplex/Views/Deck/AddHostSheet.swift:2911-2919 | Multiplex/Views/Settings/LicensesView.swift:881-889 | Multiplex/Views/Settings/SettingsView.swift:1856-1864 | Multiplex/Views/Settings/ThemeEditorView.swift:558-566 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×2
  • Duplicated block (8–9 lines × 2) Multiplex/Views/Terminal/AgentHistoryPanel.swift:396 — Multiplex/Views/Terminal/AgentHistoryPanel.swift:396-404 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:590-597 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/AgentHistoryPanel.swift:396` it does not close everything it opens, so those 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) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:285 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:285-293 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:329-336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/TerminalGuidePictograms.swift: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:328` calls `stroke`, `drawArrow` and `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:285` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×2
  • Duplicated block (7–8 lines × 2) Multiplex/Views/Deck/AgentPromptSheet.swift:321 — Multiplex/Views/Deck/AgentPromptSheet.swift:321-328 | Multiplex/Views/Deck/FleetWall.swift:4603-4609 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7–8 lines × 2) Multiplex/Views/Deck/FleetWall.swift:5102 — Multiplex/Views/Deck/FleetWall.swift:5102-5109 | Multiplex/Views/Terminal/KeyCommandPanel.swift:1604-1610 — 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 `Multiplex/Views/Deck/FleetWall.swift:5102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2
  • Duplicated block (6 lines × 4) Multiplex/Design/Chassis.swift:297 — Multiplex/Design/Chassis.swift:297-302 | Multiplex/Views/Settings/ProPaywallView.swift:595-600 | Multiplex/Views/Terminal/ShortcutPanel.swift:681-686 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1712-1717 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (6 lines × 4) Multiplex/Views/Terminal/FileAttachMenu.swift:534 — Multiplex/Views/Terminal/FileAttachMenu.swift:534-539 | Multiplex/Views/Terminal/TalkbackComposer.swift:1433-1438 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1914-1919 | Multiplex/Views/Terminal/ViewportPane.swift:1882-1887 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D1 · Cyclomatic Complexity · SingleWindowShellNativeLayout.resolve (cyclomatic 48) · ×1
  • SingleWindowShellNativeLayout.resolve (cyclomatic 48) Multiplex/Views/Shell/SingleWindowShell.swift:155 — SingleWindowShellNativeLayout.resolve has cyclomatic complexity 48 (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.
D1 · Cyclomatic Complexity · HostConnectionModel.performRefresh (cyclomatic 42) · ×1
  • HostConnectionModel.performRefresh (cyclomatic 42) Multiplex/Services/ConnectionHub.swift:518 — HostConnectionModel.performRefresh has cyclomatic complexity 42 (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.
D1 · Cyclomatic Complexity · TerminalWindowViewController.watchActivePane (cyclomatic 38) · ×1
  • TerminalWindowViewController.watchActivePane (cyclomatic 38) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1790 — TerminalWindowViewController.watchActivePane has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FleetHostSectionView.render (cyclomatic 31) · ×1
  • FleetHostSectionView.render (cyclomatic 31) Multiplex/Views/Deck/FleetWall.swift:1803 — FleetHostSectionView.render 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.
D1 · Cyclomatic Complexity · TerminalWindowViewController.layoutNativeChrome (cyclomatic 31) · ×1
  • TerminalWindowViewController.layoutNativeChrome (cyclomatic 31) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393 — TerminalWindowViewController.layoutNativeChrome 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.
D1 · Cyclomatic Complexity · TerminalWindowViewController.renderSidePanel (cyclomatic 28) · ×1
  • TerminalWindowViewController.renderSidePanel (cyclomatic 28) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2193 — TerminalWindowViewController.renderSidePanel has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DeckScene.autoAttachIfRequested (cyclomatic 26) · ×1
  • DeckScene.autoAttachIfRequested (cyclomatic 26) Multiplex/Views/Deck/DeckWindow.swift:62 — DeckScene.autoAttachIfRequested 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.
D1 · Cyclomatic Complexity · TerminalSessionController.runHistoryJump (cyclomatic 25) · ×1
  • TerminalSessionController.runHistoryJump (cyclomatic 25) Multiplex/Services/TerminalSessionController.swift:1505 — TerminalSessionController.runHistoryJump 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.
D1 · Cyclomatic Complexity · TerminalWindowViewController.renderUMD (cyclomatic 25) · ×1
  • TerminalWindowViewController.renderUMD (cyclomatic 25) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2846 — TerminalWindowViewController.renderUMD has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · UMDBarViewController.makeOverflowMenu (cyclomatic 25) · ×1
  • UMDBarViewController.makeOverflowMenu (cyclomatic 25) Multiplex/Views/Terminal/UMDBarUIKit.swift:1038 — UMDBarViewController.makeOverflowMenu 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.
D1 · Cyclomatic Complexity · HerdrProbe.sessionNameArgument (cyclomatic 24) · ×1
  • HerdrProbe.sessionNameArgument (cyclomatic 24) Multiplex/Services/HerdrProbe.swift:1175 — HerdrProbe.sessionNameArgument has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TerminalSessionController.refreshSelectTextClamp (cyclomatic 24) · ×1
  • TerminalSessionController.refreshSelectTextClamp (cyclomatic 24) Multiplex/Services/TerminalSessionController.swift:1004 — TerminalSessionController.refreshSelectTextClamp 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.
D1 · Cyclomatic Complexity · TerminalVisionOrnamentState.update (cyclomatic 23) · ×1
  • TerminalVisionOrnamentState.update (cyclomatic 23) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198 — TerminalVisionOrnamentState.update has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SSHConnection.makeAuthenticationMethod (cyclomatic 22) · ×1
  • SSHConnection.makeAuthenticationMethod (cyclomatic 22) Multiplex/Services/SSHConnection.swift:361 — SSHConnection.makeAuthenticationMethod 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.
D1 · Cyclomatic Complexity · HostStore.seedFromEnvironmentIfNeeded (cyclomatic 21) · ×1
  • HostStore.seedFromEnvironmentIfNeeded (cyclomatic 21) Multiplex/Services/HostStore.swift:391 — HostStore.seedFromEnvironmentIfNeeded 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.
D1 · Cyclomatic Complexity · TmuxProbe.parse (cyclomatic 21) · ×1
  • TmuxProbe.parse (cyclomatic 21) Multiplex/Services/TmuxProbe.swift:244 — TmuxProbe.parse 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.
D1 · Cyclomatic Complexity · TerminalKeyBar.rebuildRow (cyclomatic 21) · ×1
  • TerminalKeyBar.rebuildRow (cyclomatic 21) Multiplex/Views/Terminal/TerminalKeyBar.swift:1387 — TerminalKeyBar.rebuildRow has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TerminalKeyBar.press (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · HostConnectionModel.detectActiveAgent (cyclomatic 20) · ×1
  • HostConnectionModel.detectActiveAgent (cyclomatic 20) Multiplex/Services/ConnectionHub.swift:411 — HostConnectionModel.detectActiveAgent has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · DeckWindowViewController.process (cyclomatic 20) · ×1
  • DeckWindowViewController.process (cyclomatic 20) Multiplex/Views/Deck/DeckWindow.swift:665 — DeckWindowViewController.process 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.
D1 · Cyclomatic Complexity · SidePanelHeaderView.fileMenu (cyclomatic 20) · ×1
  • SidePanelHeaderView.fileMenu (cyclomatic 20) Multiplex/Views/Terminal/SidePanelUIKit.swift:922 — SidePanelHeaderView.fileMenu 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.
D1 · Cyclomatic Complexity · UMDBarViewController.columnChip (cyclomatic 20) · ×1
  • UMDBarViewController.columnChip (cyclomatic 20) Multiplex/Views/Terminal/UMDBarUIKit.swift:433 — UMDBarViewController.columnChip 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.
D1 · Cyclomatic Complexity · ConnectionStatsStripView.rebuildCluster (cyclomatic 19) · ×1
  • ConnectionStatsStripView.rebuildCluster (cyclomatic 19) Multiplex/Views/Deck/ConnectionStatsView.swift:396 — ConnectionStatsStripView.rebuildCluster 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.
D1 · Cyclomatic Complexity · FileViewerPaneViewController.headerMeta (cyclomatic 19) · ×1
  • FileViewerPaneViewController.headerMeta (cyclomatic 19) Multiplex/Views/Terminal/FileViewerPane.swift:765 — FileViewerPaneViewController.headerMeta has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · FileViewerPaneViewController.rebuildRail (cyclomatic 19) · ×1
  • FileViewerPaneViewController.rebuildRail (cyclomatic 19) Multiplex/Views/Terminal/FileViewerPane.swift:817 — FileViewerPaneViewController.rebuildRail 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.
D1 · Cyclomatic Complexity · FileViewerPaneViewController.runFind (cyclomatic 19) · ×1
  • FileViewerPaneViewController.runFind (cyclomatic 19) Multiplex/Views/Terminal/FileViewerPane.swift:1577 — FileViewerPaneViewController.runFind has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · HostConnectionModel.ensureConnection (cyclomatic 18) · ×1
  • HostConnectionModel.ensureConnection (cyclomatic 18) Multiplex/Services/ConnectionHub.swift:844 — HostConnectionModel.ensureConnection has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DeckWindowViewController.update (cyclomatic 18) · ×1
  • DeckWindowViewController.update (cyclomatic 18) Multiplex/Views/Deck/DeckWindow.swift:455 — DeckWindowViewController.update has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · FileViewerPaneViewController.bodyKey (cyclomatic 18) · ×1
  • FileViewerPaneViewController.bodyKey (cyclomatic 18) Multiplex/Views/Terminal/FileViewerPane.swift:1124 — FileViewerPaneViewController.bodyKey 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.
D1 · Cyclomatic Complexity · HerdrProbe.parsePaneScreenRects (cyclomatic 17) · ×1
  • HerdrProbe.parsePaneScreenRects (cyclomatic 17) Multiplex/Services/HerdrProbe.swift:894 — HerdrProbe.parsePaneScreenRects has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ConnectionStatsStripView.configure (cyclomatic 17) · ×1
  • ConnectionStatsStripView.configure (cyclomatic 17) Multiplex/Views/Deck/ConnectionStatsView.swift:320 — ConnectionStatsStripView.configure 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.
D1 · Cyclomatic Complexity · SingleWindowShellViewController.applyLayout (cyclomatic 16) · ×1
  • SingleWindowShellViewController.applyLayout (cyclomatic 16) Multiplex/Views/Shell/SingleWindowShell.swift:1261 — SingleWindowShellViewController.applyLayout 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.
D1 · Cyclomatic Complexity · FileViewerTextContent.diff (cyclomatic 16) · ×1
  • FileViewerTextContent.diff (cyclomatic 16) Multiplex/Views/Terminal/FileViewerTextView.swift:144 — FileViewerTextContent.diff 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.
D1 · Cyclomatic Complexity · SidePanelHeaderView.buildFileRow (cyclomatic 16) · ×1
  • SidePanelHeaderView.buildFileRow (cyclomatic 16) Multiplex/Views/Terminal/SidePanelUIKit.swift:780 — SidePanelHeaderView.buildFileRow 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.
D1 · Cyclomatic Complexity · TerminalKeyClusterGroupView.makeKey (cyclomatic 16) · ×1
  • TerminalKeyClusterGroupView.makeKey (cyclomatic 16) Multiplex/Views/Terminal/TerminalKeyBar.swift:2882 — TerminalKeyClusterGroupView.makeKey has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: TerminalKeyBar.press (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · TerminalVisionControllerHost.fittingSize (cyclomatic 16) · ×1
  • TerminalVisionControllerHost.fittingSize (cyclomatic 16) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1278 — TerminalVisionControllerHost.fittingSize 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.
D2 · Cognitive Complexity · HostConnectionModel.performRefresh (cognitive 71) · ×1
  • HostConnectionModel.performRefresh (cognitive 71) Multiplex/Services/ConnectionHub.swift:518 — HostConnectionModel.performRefresh has cognitive complexity 71 (threshold 15). Drivers by points: if/else 25 (52 pts), boolean chains 10, loops 2 (4 pts), error handling 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalWindowViewController.watchActivePane (cognitive 71) · ×1
  • TerminalWindowViewController.watchActivePane (cognitive 71) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1790 — TerminalWindowViewController.watchActivePane has cognitive complexity 71 (threshold 15). Drivers by points: if/else 19 (51 pts), boolean chains 15, loops 3 (5 pts) (nesting depth added 34). 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.
D2 · Cognitive Complexity · SingleWindowShellNativeLayout.resolve (cognitive 54) · ×1
  • SingleWindowShellNativeLayout.resolve (cognitive 54) Multiplex/Views/Shell/SingleWindowShell.swift:155 — SingleWindowShellNativeLayout.resolve has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 23, ternaries 17 (20 pts), if/else 11 (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.
D2 · Cognitive Complexity · TerminalWindowViewController.layoutNativeChrome (cognitive 45) · ×1
  • TerminalWindowViewController.layoutNativeChrome (cognitive 45) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3393 — TerminalWindowViewController.layoutNativeChrome has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 10, ternaries 4 (10 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FleetHostSectionView.render (cognitive 41) · ×1
  • FleetHostSectionView.render (cognitive 41) Multiplex/Views/Deck/FleetWall.swift:1803 — FleetHostSectionView.render has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 9, ternaries 2 (3 pts), loops 1 (2 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.
D2 · Cognitive Complexity · SidePanelHeaderView.fileMenu (cognitive 36) · ×1
  • SidePanelHeaderView.fileMenu (cognitive 36) Multiplex/Views/Terminal/SidePanelUIKit.swift:922 — SidePanelHeaderView.fileMenu has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 3 (9 pts), match/switch 1 (2 pts), loops 1 (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.
D2 · Cognitive Complexity · DeckScene.autoAttachIfRequested (cognitive 35) · ×1
  • DeckScene.autoAttachIfRequested (cognitive 35) Multiplex/Views/Deck/DeckWindow.swift:62 — DeckScene.autoAttachIfRequested has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 8, loops 3 (5 pts), match/switch 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.
D2 · Cognitive Complexity · TmuxProbe.parse (cognitive 34) · ×1
  • TmuxProbe.parse (cognitive 34) Multiplex/Services/TmuxProbe.swift:244 — TmuxProbe.parse has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 4 (5 pts), match/switch 1 (2 pts), ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalWindowViewController.renderSidePanel (cognitive 34) · ×1
  • TerminalWindowViewController.renderSidePanel (cognitive 34) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2193 — TerminalWindowViewController.renderSidePanel has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 10, ternaries 4, 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.
D2 · Cognitive Complexity · SSHConnection.makeAuthenticationMethod (cognitive 33) · ×1
  • SSHConnection.makeAuthenticationMethod (cognitive 33) Multiplex/Services/SSHConnection.swift:361 — SSHConnection.makeAuthenticationMethod has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 8, match/switch 1 (nesting depth added 13). 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.
D2 · Cognitive Complexity · TerminalWindowViewController.renderUMD (cognitive 33) · ×1
  • TerminalWindowViewController.renderUMD (cognitive 33) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:2846 — TerminalWindowViewController.renderUMD has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 12 (13 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FileViewerTextContent.diff (cognitive 32) · ×1
  • FileViewerTextContent.diff (cognitive 32) Multiplex/Views/Terminal/FileViewerTextView.swift:144 — FileViewerTextContent.diff has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (6 pts), match/switch 1 (4 pts), ternaries 1 (3 pts), boolean chains 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.
D2 · Cognitive Complexity · UMDBarViewController.makeOverflowMenu (cognitive 31) · ×1
  • UMDBarViewController.makeOverflowMenu (cognitive 31) Multiplex/Views/Terminal/UMDBarUIKit.swift:1038 — UMDBarViewController.makeOverflowMenu has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 6 (12 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · EntitlementStore.listenForTransactions (cognitive 30) · ×1
  • EntitlementStore.listenForTransactions (cognitive 30) Multiplex/Services/EntitlementStore.swift:788 — EntitlementStore.listenForTransactions has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 2 (6 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.
D2 · Cognitive Complexity · TerminalSessionController.runHistoryJump (cognitive 30) · ×1
  • TerminalSessionController.runHistoryJump (cognitive 30) Multiplex/Services/TerminalSessionController.swift:1505 — TerminalSessionController.runHistoryJump has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 4 (8 pts), match/switch 3 (5 pts), boolean chains 4, error handling 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.
D2 · Cognitive Complexity · TerminalKeyBar.rebuildRow (cognitive 30) · ×1
  • TerminalKeyBar.rebuildRow (cognitive 30) Multiplex/Views/Terminal/TerminalKeyBar.swift:1387 — TerminalKeyBar.rebuildRow has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 8 (10 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HerdrProbe.sessionNameArgument (cognitive 27) · ×1
  • HerdrProbe.sessionNameArgument (cognitive 27) Multiplex/Services/HerdrProbe.swift:1175 — HerdrProbe.sessionNameArgument has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 15, if/else 4 (7 pts), loops 4, ternaries 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · SSHConnection.uploadFiles (cognitive 27) · ×1
  • SSHConnection.uploadFiles (cognitive 27) Multiplex/Services/SSHConnection.swift:496 — SSHConnection.uploadFiles has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (6 pts), error handling 2 (5 pts), ternaries 1 (3 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.
D2 · Cognitive Complexity · TerminalSessionController.refreshSelectTextClamp (cognitive 27) · ×1
  • TerminalSessionController.refreshSelectTextClamp (cognitive 27) Multiplex/Services/TerminalSessionController.swift:1004 — TerminalSessionController.refreshSelectTextClamp has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, match/switch 3 (4 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.
D2 · Cognitive Complexity · FileViewerController.start (cognitive 25) · ×1
  • FileViewerController.start (cognitive 25) Multiplex/Services/FileViewerController.swift:423 — FileViewerController.start has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (3 pts), boolean chains 1, error handling 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.
D2 · Cognitive Complexity · ConnectionStatsStripView.rebuildCluster (cognitive 25) · ×1
  • ConnectionStatsStripView.rebuildCluster (cognitive 25) Multiplex/Views/Deck/ConnectionStatsView.swift:396 — ConnectionStatsStripView.rebuildCluster has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (19 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DeckWindowViewController.process (cognitive 25) · ×1
  • DeckWindowViewController.process (cognitive 25) Multiplex/Views/Deck/DeckWindow.swift:665 — DeckWindowViewController.process has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FileViewerPaneViewController.rebuildRail (cognitive 25) · ×1
  • FileViewerPaneViewController.rebuildRail (cognitive 25) Multiplex/Views/Terminal/FileViewerPane.swift:817 — FileViewerPaneViewController.rebuildRail has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 6 (9 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SSHConnection.readChunks (cognitive 24) · ×1
  • SSHConnection.readChunks (cognitive 24) Multiplex/Services/SSHConnection.swift:705 — SSHConnection.readChunks has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShellAgentProbe.parse (cognitive 23) · ×1
  • ShellAgentProbe.parse (cognitive 23) Multiplex/Services/ShellAgentProbe.swift:52 — ShellAgentProbe.parse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalPaneViewController.renderSelectionMenu (cognitive 23) · ×1
  • TerminalPaneViewController.renderSelectionMenu (cognitive 23) Multiplex/Views/Terminal/TerminalPaneUIKit.swift:357 — TerminalPaneViewController.renderSelectionMenu has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileViewerMarkdownContentView.applyFindWashes (cognitive 22) · ×1
  • FileViewerMarkdownContentView.applyFindWashes (cognitive 22) Multiplex/Views/Terminal/FileViewerPane.swift:3919 — FileViewerMarkdownContentView.applyFindWashes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · TerminalVisionOrnamentState.update (cognitive 22) · ×1
  • TerminalVisionOrnamentState.update (cognitive 22) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:198 — TerminalVisionOrnamentState.update has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, ternaries 7, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · BackendDiscovery.read (cognitive 21) · ×1
  • BackendDiscovery.read (cognitive 21) Multiplex/Services/BackendDiscovery.swift:142 — BackendDiscovery.read has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (3 pts) (nesting depth added 9). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HostStore.seedFromEnvironmentIfNeeded (cognitive 21) · ×1
  • HostStore.seedFromEnvironmentIfNeeded (cognitive 21) Multiplex/Services/HostStore.swift:391 — HostStore.seedFromEnvironmentIfNeeded has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, boolean chains 3, ternaries 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.
D2 · Cognitive Complexity · TerminalSessionController.loadAgentHistory (cognitive 21) · ×1
  • TerminalSessionController.loadAgentHistory (cognitive 21) Multiplex/Services/TerminalSessionController.swift:1398 — TerminalSessionController.loadAgentHistory has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, error handling 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.
D2 · Cognitive Complexity · ConnectionStatsStripView.configure (cognitive 21) · ×1
  • ConnectionStatsStripView.configure (cognitive 21) Multiplex/Views/Deck/ConnectionStatsView.swift:320 — ConnectionStatsStripView.configure has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 8 (9 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · FileViewerMarkdownInlineRenderer.render (cognitive 21) · ×1
  • FileViewerMarkdownInlineRenderer.render (cognitive 21) Multiplex/Views/Terminal/FileViewerPane.swift:2803 — FileViewerMarkdownInlineRenderer.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 2 (6 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · UMDBarViewController.columnChip (cognitive 21) · ×1
  • UMDBarViewController.columnChip (cognitive 21) Multiplex/Views/Terminal/UMDBarUIKit.swift:433 — UMDBarViewController.columnChip has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5 (9 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · HostConnectionModel.detectActiveAgent (cognitive 20) · ×1
  • HostConnectionModel.detectActiveAgent (cognitive 20) Multiplex/Services/ConnectionHub.swift:411 — HostConnectionModel.detectActiveAgent has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 9 (10 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · HostConnectionModel.ensureConnection (cognitive 20) · ×1
  • HostConnectionModel.ensureConnection (cognitive 20) Multiplex/Services/ConnectionHub.swift:844 — HostConnectionModel.ensureConnection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 9, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · HerdrProbe.parseProbe (cognitive 20) · ×1
  • HerdrProbe.parseProbe (cognitive 20) Multiplex/Services/HerdrProbe.swift:224 — HerdrProbe.parseProbe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TmuxProbe.tmuxConfOptions (cognitive 20) · ×1
  • TmuxProbe.tmuxConfOptions (cognitive 20) Multiplex/Services/TmuxProbe.swift:939 — TmuxProbe.tmuxConfOptions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FleetWallViewController.renderWall (cognitive 20) · ×1
  • FleetWallViewController.renderWall (cognitive 20) Multiplex/Views/Deck/FleetWall.swift:563 — FleetWallViewController.renderWall has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 6, loops 2 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KeyCommandDispatcher.perform (cognitive 19) · ×1
  • KeyCommandDispatcher.perform (cognitive 19) Multiplex/Services/KeyCommandDispatcher.swift:19 — KeyCommandDispatcher.perform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileViewerPaneViewController.bodyKey (cognitive 19) · ×1
  • FileViewerPaneViewController.bodyKey (cognitive 19) Multiplex/Views/Terminal/FileViewerPane.swift:1124 — FileViewerPaneViewController.bodyKey has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 1 (3 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · FileViewerController.open (cognitive 18) · ×1
  • FileViewerController.open (cognitive 18) Multiplex/Services/FileViewerController.swift:708 — FileViewerController.open has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), error handling 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.
D2 · Cognitive Complexity · BindController.runDebugAutomationIfRequested (cognitive 18) · ×1
  • BindController.runDebugAutomationIfRequested (cognitive 18) Multiplex/Services/Bind/BindController.swift:696 — BindController.runDebugAutomationIfRequested has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileViewerPaneViewController.headerMeta (cognitive 18) · ×1
  • FileViewerPaneViewController.headerMeta (cognitive 18) Multiplex/Views/Terminal/FileViewerPane.swift:765 — FileViewerPaneViewController.headerMeta has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (9 pts), match/switch 3 (6 pts), if/else 2 (3 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · FileViewerPaneViewController.runFind (cognitive 18) · ×1
  • FileViewerPaneViewController.runFind (cognitive 18) Multiplex/Views/Terminal/FileViewerPane.swift:1577 — FileViewerPaneViewController.runFind has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (6 pts), ternaries 2, match/switch 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · TerminalWindowViewController.syncTabs (cognitive 18) · ×1
  • TerminalWindowViewController.syncTabs (cognitive 18) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1282 — TerminalWindowViewController.syncTabs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · TerminalWindowViewController.renderTalkback (cognitive 18) · ×1
  • TerminalWindowViewController.renderTalkback (cognitive 18) Multiplex/Views/Terminal/TerminalWindowUIKit.swift:3103 — TerminalWindowViewController.renderTalkback has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HerdrProbe.parsePaneScreenRects (cognitive 17) · ×1
  • HerdrProbe.parsePaneScreenRects (cognitive 17) Multiplex/Services/HerdrProbe.swift:894 — HerdrProbe.parsePaneScreenRects has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · NewSessionPreferences.save (cognitive 17) · ×1
  • NewSessionPreferences.save (cognitive 17) Multiplex/Services/NewSessionPreferences.swift:68 — NewSessionPreferences.save has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DeckWindowViewController.update (cognitive 17) · ×1
  • DeckWindowViewController.update (cognitive 17) Multiplex/Views/Deck/DeckWindow.swift:455 — DeckWindowViewController.update has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, if/else 5. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · SingleWindowShellViewController.applyLayout (cognitive 17) · ×1
  • SingleWindowShellViewController.applyLayout (cognitive 17) Multiplex/Views/Shell/SingleWindowShell.swift:1261 — SingleWindowShellViewController.applyLayout has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · SidePanelHeaderView.buildFileRow (cognitive 17) · ×1
  • SidePanelHeaderView.buildFileRow (cognitive 17) Multiplex/Views/Terminal/SidePanelUIKit.swift:780 — SidePanelHeaderView.buildFileRow has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4, match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalVisionBottomOrnament.body (cognitive 17) · ×1
  • TerminalVisionBottomOrnament.body (cognitive 17) Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:474 — TerminalVisionBottomOrnament.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · DictationSession.begin (cognitive 16) · ×1
  • DictationSession.begin (cognitive 16) Multiplex/Services/DictationSession.swift:273 — DictationSession.begin has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 3, error handling 2, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FileViewerController.watchTick (cognitive 16) · ×1
  • FileViewerController.watchTick (cognitive 16) Multiplex/Services/FileViewerController.swift:1084 — FileViewerController.watchTick has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · HerdrProbe.parseTails (cognitive 16) · ×1
  • HerdrProbe.parseTails (cognitive 16) Multiplex/Services/HerdrProbe.swift:1241 — HerdrProbe.parseTails has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GzipInflater.inflateBody (cognitive 16) · ×1
  • GzipInflater.inflateBody (cognitive 16) Multiplex/Services/RNNoiseModelStore.swift:393 — GzipInflater.inflateBody has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · TerminalFocusArbiter.claim (cognitive 16) · ×1
  • TerminalFocusArbiter.claim (cognitive 16) Multiplex/Views/Terminal/TerminalFocusArbiter.swift:64 — TerminalFocusArbiter.claim has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: TerminalWindow.swift → AgentSignature.swift, TerminalWorkspace.swift, SwiftTermView.swift Multiplex/Views/Terminal/TerminalWindow.swift — `Multiplex/Views/Terminal/TerminalWindow.swift` changes together with 3 other files — `Multiplex/Models/AgentSignature.swift`, `Multiplex/Services/TerminalWorkspace.swift`, `Multiplex/Views/Terminal/SwiftTermView.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Near-duplicate member family (5 members, 23 shared lines) · ×1
  • Near-duplicate member family (5 members, 23 shared lines) Multiplex/Design/Chassis.swift:605 — Multiplex/Design/Chassis.swift:605-678 | Multiplex/Views/Deck/AddHostSheet.swift:2211-2275 | Multiplex/Views/Deck/BindPane.swift:650-712 | Multiplex/Views/Deck/FleetWall.swift:4901-4977 | Multiplex/Views/Settings/SettingsView.swift:940-1015 — These 5 members are variants of one another: a block of 23 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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 · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (13 members, 50+ identical tokens) Multiplex/Views/Deck/AddHostSheet.swift:516 — Multiplex/Views/Deck/AddHostSheet.swift:516-567 | Multiplex/Views/Deck/AgentPromptSheet.swift:165-219 | Multiplex/Views/Deck/ConnectionStatsView.swift:80-125 | Multiplex/Views/Deck/FleetWall.swift:4346-4429 | Multiplex/Views/Deck/HostGuideSheets.swift:196-246 | Multiplex/Views/Settings/FAQView.swift:49-102 | Multiplex/Views/Settings/ProPaywallView.swift:98-152 | Multiplex/Views/Settings/ReleaseNotesView.swift:84-142 | Multiplex/Views/Settings/ReleaseNotesView.swift:367-430 | Multiplex/Views/Settings/SettingsView.swift:139-189 | Multiplex/Views/Terminal/TerminalFilePathSheet.swift:122-247 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:76-126 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:252-321 — These 13 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 13 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 13 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Multiplex/Views/Deck/AddHostSheet.swift:516 — Multiplex/Views/Deck/AddHostSheet.swift:516-567 | Multiplex/Views/Settings/ProPaywallView.swift:98-152 | Multiplex/Views/Settings/ReleaseNotesView.swift:84-142 | Multiplex/Views/Settings/ReleaseNotesView.swift:367-430 | Multiplex/Views/Settings/SettingsView.swift:139-189 | Multiplex/Views/Settings/ThemeEditorView.swift:170-235 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:2714 — Multiplex/Views/Deck/AddHostSheet.swift:2714-2769 | Multiplex/Views/Deck/BindPane.swift:1153-1201 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) Multiplex/Views/Terminal/TerminalKeyBar.swift:3104 — Multiplex/Views/Terminal/TerminalKeyBar.swift:3104-3145 | Multiplex/Views/Terminal/TerminalWindow.swift:133-188 — 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:2324 — Multiplex/Views/Deck/AddHostSheet.swift:2324-2354 | Multiplex/Views/Deck/AgentPromptSheet.swift:496-530 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) Multiplex/Views/Deck/FleetWall.swift:5160 — Multiplex/Views/Deck/FleetWall.swift:5160-5191 | Multiplex/Views/Deck/FleetWall.swift:5321-5357 — 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 (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) Multiplex/Views/Terminal/TerminalGuideViewController.swift:191 — Multiplex/Views/Terminal/TerminalGuideViewController.swift:191-226 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:313-346 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) Multiplex/Views/Deck/AgentPromptSheet.swift:550 — Multiplex/Views/Deck/AgentPromptSheet.swift:550-585 | Multiplex/Views/Deck/FleetWall.swift:5375-5409 — 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 (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) Multiplex/Services/ConnectionHub.swift:1210 — Multiplex/Services/ConnectionHub.swift:1210-1254 | Multiplex/Services/ConnectionHub.swift:1431-1466 — 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 (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) Multiplex/Views/Deck/AgentPromptSheet.swift:116 — Multiplex/Views/Deck/AgentPromptSheet.swift:116-148 | Multiplex/Views/Deck/FleetWall.swift:4307-4339 — 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Multiplex/Views/Deck/FleetWall.swift:1088 — Multiplex/Views/Deck/FleetWall.swift:1088-1116 | Multiplex/Views/Terminal/TerminalWindowUIKit.swift:1430-1457 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) Multiplex/Views/Terminal/AgentHelperStrip.swift:522 — Multiplex/Views/Terminal/AgentHelperStrip.swift:522-555 | Multiplex/Views/Terminal/AgentHelperStrip.swift:557-585 — 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 (5 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 22+ corresponding lines) Multiplex/Views/Deck/ConnectionStatsView.swift:50 — Multiplex/Views/Deck/ConnectionStatsView.swift:50-73 | Multiplex/Views/Deck/HostGuideSheets.swift:155-176 | Multiplex/Views/Settings/FAQView.swift:19-42 | Multiplex/Views/Settings/LicensesView.swift:73-94 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:35-57 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) Multiplex/Views/Deck/FleetWall.swift:4815 — Multiplex/Views/Deck/FleetWall.swift:4815-4830 | Multiplex/Views/Settings/LicensesView.swift:908-924 | Multiplex/Views/Terminal/FileViewerTreeColumn.swift:479-491 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) Multiplex/Services/TmuxProbe.swift:913 — Multiplex/Models/AgentSignature.swift:122-133 | Multiplex/Models/ComposedText.swift:9-19 | Multiplex/Models/SessionScript.swift:28-39 | Multiplex/Services/TmuxProbe.swift:913-926 — 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 (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) Multiplex/Views/Terminal/ViewportPane.swift:416 — Multiplex/Views/Terminal/ViewportPane.swift:416-430 | Multiplex/Views/Terminal/ViewportPane.swift:1562-1578 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) Multiplex/AppIntents/OpenHostIntents.swift:260 — Multiplex/AppIntents/OpenHostIntents.swift:260-271 | Multiplex/AppIntents/OpenHostIntents.swift:373-383 | MultiplexWidgets/HostWidgetConfigurationIntent.swift:110-118 | MultiplexWidgets/HostWidgetConfigurationIntent.swift:127-135 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) Multiplex/Services/Bind/BindRotationStore.swift:39 — Multiplex/Services/Bind/BindRotationStore.swift:39-46 | Multiplex/Services/DeckSnapshotStore.swift:78-85 | Multiplex/Services/HostStore.swift:326-334 — 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 (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) Multiplex/Views/Deck/AddHostSheet.swift:228 — Multiplex/Views/Deck/AddHostSheet.swift:228-234 | Multiplex/Views/Deck/AddHostSheet.swift:240-245 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:36-41 | Multiplex/Views/Terminal/KeyCommandPanel.swift:190-196 — 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, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) Multiplex/Design/Chassis.swift:453 — Multiplex/Design/Chassis.swift:453-467 | Multiplex/Views/Terminal/FileAttachMenu.swift:541-554 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1996-2007 | Multiplex/Views/Terminal/ViewportPane.swift:1889-1901 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (35–54 lines × 2) · ×1
  • Duplicated block (35–54 lines × 2) Multiplex/Services/AgentSessionHistory.swift:1078 — Multiplex/Services/AgentSessionHistory.swift:1078-1131 | Multiplex/Services/AgentSessionHistory.swift:1134-1168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (43–45 lines × 2) · ×1
  • Duplicated block (43–45 lines × 2) Multiplex/Views/Terminal/TerminalFilePathSheet.swift:205 — Multiplex/Views/Terminal/TerminalFilePathSheet.swift:205-247 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:277-321 — before extracting anything, compare `Multiplex/Views/Terminal/TerminalFilePathSheet.swift` and `Multiplex/Views/Terminal/TerminalLinkSheet.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `Multiplex/Views/Terminal/TerminalFilePathSheet.swift: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.
D4 · Code Duplication · Duplicated block (41–42 lines × 2) · ×1
  • Duplicated block (41–42 lines × 2) Multiplex/Services/AgentSessionHistory.swift:1013 — Multiplex/Services/AgentSessionHistory.swift:1013-1053 | Multiplex/Services/AgentSessionHistory.swift:1055-1096 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (31–34 lines × 3) · ×1
  • Duplicated block (31–34 lines × 3) Multiplex/Views/Deck/AgentPromptSheet.swift:181 — Multiplex/Views/Deck/AgentPromptSheet.swift:181-214 | Multiplex/Views/Deck/FleetWall.swift:4362-4392 | Multiplex/Views/Deck/HostGuideSheets.swift:212-245 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (26–28 lines × 6) · ×1
  • Duplicated block (26–28 lines × 6) Multiplex/Views/Deck/AddHostSheet.swift:542 — Multiplex/Views/Deck/AddHostSheet.swift:542-567 | Multiplex/Views/Settings/ProPaywallView.swift:125-152 | Multiplex/Views/Settings/ReleaseNotesView.swift:115-142 | Multiplex/Views/Settings/ReleaseNotesView.swift:403-430 | Multiplex/Views/Settings/SettingsView.swift:162-189 | Multiplex/Views/Settings/ThemeEditorView.swift:208-235 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:542` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) Multiplex/Views/Terminal/FileViewerPane.swift:495 — Multiplex/Views/Terminal/FileViewerPane.swift:495-522 | Multiplex/Views/Terminal/ViewportPane.swift:235-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/FileViewerPane.swift:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) Multiplex/Views/Deck/FleetWall.swift:1827 — Multiplex/Views/Deck/FleetWall.swift:1827-1847 | Multiplex/Views/Deck/FleetWall.swift:1865-1885 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/FleetWall.swift:1827` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) Multiplex/Views/Terminal/FileAttachMenu.swift:490 — Multiplex/Views/Terminal/FileAttachMenu.swift:490-509 | Multiplex/Views/Terminal/TerminalTabStrip.swift:736-755 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (10–18 lines × 4) · ×1
  • Duplicated block (10–18 lines × 4) Multiplex/App/UIKitSceneRootViewController.swift:146 — Multiplex/App/UIKitSceneRootViewController.swift:146-163 | Multiplex/App/UIKitSceneRootViewController.swift:394-403 | Multiplex/Views/Deck/BindPane.swift:1379-1388 | Multiplex/Views/Deck/FleetWall.swift:106-115 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) Multiplex/Views/Terminal/FileViewerPane.swift:1081 — Multiplex/Views/Terminal/FileViewerPane.swift:1081-1098 | Multiplex/Views/Terminal/ViewportPane.swift:1246-1263 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) Multiplex/Design/Chassis.swift:638 — Multiplex/Design/Chassis.swift:638-654 | Multiplex/Views/Settings/SettingsView.swift:967-982 — 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.
D4 · Code Duplication · Duplicated block (13–17 lines × 2) · ×1
  • Duplicated block (13–17 lines × 2) Multiplex/Services/ExternalActionRouter.swift:437 — Multiplex/Services/ExternalActionRouter.swift:437-453 | Multiplex/Views/Deck/FleetWall.swift:959-971 — 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 `Multiplex/Services/ExternalActionRouter.swift:437` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) Multiplex/AppIntents/OpenHostIntents.swift:234 — Multiplex/AppIntents/OpenHostIntents.swift:234-249 | MultiplexWidgets/HostWidgetConfigurationIntent.swift:87-101 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) Multiplex/Views/Terminal/FileViewerPane.swift:999 — Multiplex/Views/Terminal/FileViewerPane.swift:999-1013 | Multiplex/Views/Terminal/ViewportPane.swift:1229-1243 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Terminal/FileViewerPane.swift:999` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (12–14 lines × 13) · ×1
  • Duplicated block (12–14 lines × 13) Multiplex/Views/Deck/AddHostSheet.swift:521 — Multiplex/Views/Deck/AddHostSheet.swift:521-532 | Multiplex/Views/Deck/AgentPromptSheet.swift:167-178 | Multiplex/Views/Deck/ConnectionStatsView.swift:82-93 | Multiplex/Views/Deck/FleetWall.swift:4348-4359 | Multiplex/Views/Deck/HostGuideSheets.swift:198-209 | Multiplex/Views/Settings/FAQView.swift:51-64 | Multiplex/Views/Settings/ProPaywallView.swift:100-111 | Multiplex/Views/Settings/ReleaseNotesView.swift:86-97 | Multiplex/Views/Settings/ReleaseNotesView.swift:369-380 | Multiplex/Views/Settings/SettingsView.swift:141-152 | Multiplex/Views/Terminal/TerminalFilePathSheet.swift:124-135 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:78-89 | Multiplex/Views/Terminal/TerminalLinkSheet.swift:254-265 — there are 13 copies across 12 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 13 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/TerminalLinkSheet.swift:267` calls `configureHostStack`, `configureReachStack`, `configureActionStack` and `Multiplex/Views/Deck/AddHostSheet.swift:534` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 4) · ×1
  • Duplicated block (13–14 lines × 4) Multiplex/Views/Deck/ConnectionStatsView.swift:50 — Multiplex/Views/Deck/ConnectionStatsView.swift:50-63 | Multiplex/Views/Deck/FleetWall.swift:4307-4320 | Multiplex/Views/Settings/ReleaseNotesView.swift:339-351 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:35-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/ConnectionStatsView.swift:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) Multiplex/Views/Deck/AddHostSheet.swift:2243 — Multiplex/Views/Deck/AddHostSheet.swift:2243-2256 | Multiplex/Views/Deck/BindPane.swift:682-695 | Multiplex/Views/Deck/FleetWall.swift:4947-4960 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Views/Deck/AddHostSheet.swift:2243` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 5) · ×1
  • Duplicated block (12–13 lines × 5) Multiplex/Views/Deck/ConnectionStatsView.swift:58 — Multiplex/Views/Deck/ConnectionStatsView.swift:58-70 | Multiplex/Views/Deck/HostGuideSheets.swift:163-174 | Multiplex/Views/Settings/FAQView.swift:29-40 | Multiplex/Views/Settings/ReleaseNotesView.swift:346-358 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:42-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Deck/ConnectionStatsView.swift:72` calls `observe` and `Multiplex/Views/Deck/HostGuideSheets.swift:176` 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.
D4 · Code Duplication · Duplicated block (11–13 lines × 4) · ×1
  • Duplicated block (11–13 lines × 4) Multiplex/Views/Deck/ConnectionStatsView.swift:55 — Multiplex/Views/Deck/ConnectionStatsView.swift:55-67 | Multiplex/Views/Settings/ReleaseNotesView.swift:344-355 | Multiplex/Views/Settings/SettingsView.swift:106-116 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:40-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/TerminalGuideViewController.swift:55` calls `rebuildContent` and `Multiplex/Views/Settings/ReleaseNotesView.swift: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.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) Multiplex/App/UIKitSceneRootViewController.swift:594 — Multiplex/App/UIKitSceneRootViewController.swift:594-603 | Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1263-1274 — 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 `Multiplex/Views/Terminal/TerminalVisionOrnaments.swift:1263` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Multiplex/Views/Deck/FleetWall.swift:4312 — Multiplex/Views/Deck/FleetWall.swift:4312-4323 | Multiplex/Views/Terminal/TerminalFilePathSheet.swift:107-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) Multiplex/Views/Deck/FleetWall.swift:360 — Multiplex/Views/Deck/FleetWall.swift:360-370 | Multiplex/Views/Terminal/FileViewerPane.swift:401-411 | Multiplex/Views/Terminal/ViewportPane.swift:169-179 — 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) Multiplex/Services/ConnectionHub.swift:941 — Multiplex/Services/ConnectionHub.swift:941-950 | Multiplex/Services/Deadline.swift:16-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single 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 `Multiplex/Services/ConnectionHub.swift:941` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) Multiplex/Views/Deck/BindPane.swift:1059 — Multiplex/Views/Deck/BindPane.swift:1059-1067 | Multiplex/Views/Deck/FleetWall.swift:5039-5047 | Multiplex/Views/Settings/SettingsView.swift:1004-1013 | Multiplex/Views/Settings/SettingsView.swift:1670-1678 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/BindPane.swift:1059` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) Multiplex/Design/Chassis.swift:509 — Multiplex/Design/Chassis.swift:509-518 | Multiplex/Design/TallyEditorControls.swift:58-67 | Multiplex/Views/Deck/FleetWall.swift:5258-5267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:509` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–10 lines × 3) · ×1
  • Duplicated block (4–10 lines × 3) Multiplex/Views/Deck/FleetWall.swift:3316 — Multiplex/Views/Deck/FleetWall.swift:3316-3319 | Multiplex/Views/Settings/LicensesView.swift:915-924 | Multiplex/Views/Terminal/FileViewerTreeColumn.swift:482-491 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/FleetWall.swift:3316` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `horizontal` to `CGFloat = 12` in one and `CGFloat` 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:387 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:387-396 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:401-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:387` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) Multiplex/Views/Deck/AgentPromptSheet.swift:630 — Multiplex/Views/Deck/AgentPromptSheet.swift:630-638 | Multiplex/Views/Deck/FleetWall.swift:5339-5347 | Multiplex/Views/Settings/SettingsView.swift:1075-1083 | Multiplex/Views/Settings/SettingsView.swift:1311-1319 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:661-669 | Multiplex/Views/Terminal/ShortcutPanel.swift:643-651 | Multiplex/Views/Terminal/ShortcutPanel.swift:839-847 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1429-1437 — there are 8 copies across 6 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AgentPromptSheet.swift:630` it does not close everything it opens, so those 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, `Multiplex/Views/Settings/SettingsView.swift:1086` calls `constraint` and `Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1440` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) Multiplex/Views/Deck/BindPane.swift:749 — Multiplex/Views/Deck/BindPane.swift:749-756 | Multiplex/Views/Settings/ThemeEditorView.swift:495-503 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:704-711 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:747-754 | Multiplex/Views/Terminal/ViewportPane.swift:694-702 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/BindPane.swift:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) Multiplex/Design/Chassis.swift:656 — Multiplex/Design/Chassis.swift:656-666 | Multiplex/Views/Deck/AddHostSheet.swift:2250-2260 | Multiplex/Views/Deck/BindPane.swift:689-699 | Multiplex/Views/Deck/FleetWall.swift:4954-4964 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Multiplex/Design/Chassis.swift:652` calls `UIStackView` and `Multiplex/Views/Deck/AddHostSheet.swift:2248` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×1
  • Duplicated block (8–9 lines × 3) Multiplex/Views/Deck/AddHostSheet.swift:2343 — Multiplex/Views/Deck/AddHostSheet.swift:2343-2350 | Multiplex/Views/Deck/BindPane.swift:980-988 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1036-1043 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2343` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 29) · ×1
  • Duplicated block (8 lines × 29) Multiplex/Design/Chassis.swift:513 — Multiplex/Design/Chassis.swift:513-520 | Multiplex/Design/Chassis.swift:670-677 | Multiplex/Design/TallyEditorControls.swift:62-69 | Multiplex/Views/Deck/AddHostSheet.swift:2265-2272 | Multiplex/Views/Deck/AddHostSheet.swift:2760-2767 | Multiplex/Views/Deck/AgentPromptSheet.swift:522-529 | Multiplex/Views/Deck/BindPane.swift:704-711 | Multiplex/Views/Deck/BindPane.swift:1061-1068 | Multiplex/Views/Deck/BindPane.swift:1192-1199 | Multiplex/Views/Deck/ConnectionStatsView.swift:302-309 | Multiplex/Views/Deck/FleetWall.swift:223-230 | Multiplex/Views/Deck/FleetWall.swift:4968-4975 | Multiplex/Views/Settings/FAQView.swift:175-182 | Multiplex/Views/Settings/LicensesView.swift:846-853 | Multiplex/Views/Settings/SettingsView.swift:1007-1014 | Multiplex/Views/Settings/SettingsView.swift:1672-1679 | Multiplex/Views/Settings/SettingsVoiceInputSection.swift:79-86 | Multiplex/Views/Terminal/AgentHelperStrip.swift:822-829 | Multiplex/Views/Terminal/AgentHelperStrip.swift:868-875 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:592-599 | Multiplex/Views/Terminal/FileViewerPane.swift:2238-2245 | Multiplex/Views/Terminal/KeyCommandPanel.swift:1162-1169 | Multiplex/Views/Terminal/KeyCommandPanel.swift:1604-1611 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:218-225 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:297-304 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:338-345 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1357-1364 | Multiplex/Views/Terminal/UMDBarUIKit.swift:2073-2080 | Multiplex/Views/Terminal/ViewportPane.swift:1772-1779 — there are 29 copies across 19 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 29 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Design/Chassis.swift:521` calls `refreshInk` and `Multiplex/Design/Chassis.swift:678` 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.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) Multiplex/Views/Deck/ConnectionStatsView.swift:54 — Multiplex/Views/Deck/ConnectionStatsView.swift:54-63 | Multiplex/Views/Deck/FleetWall.swift:4311-4320 | Multiplex/Views/Settings/ReleaseNotesView.swift:343-351 | Multiplex/Views/Settings/SettingsView.swift:105-112 | Multiplex/Views/Terminal/TerminalFilePathSheet.swift:106-115 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:39-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/ConnectionStatsView.swift:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) Multiplex/Design/Chassis.swift:513 — Multiplex/Design/Chassis.swift:513-519 | Multiplex/Design/TallyEditorControls.swift:62-68 | Multiplex/Views/Deck/FleetWall.swift:5262-5268 | Multiplex/Views/Terminal/AgentHelperStrip.swift:822-828 | Multiplex/Views/Terminal/UMDBarUIKit.swift:2073-2079 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:513` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) Multiplex/Views/Deck/AddHostSheet.swift:2222 — Multiplex/Views/Deck/AddHostSheet.swift:2222-2228 | Multiplex/Views/Deck/BindPane.swift:663-669 | Multiplex/Views/Settings/SettingsView.swift:953-959 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1280-1286 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2222` 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, `Multiplex/Views/Settings/SettingsView.swift:962` calls `UIStackView` and `Multiplex/Views/Deck/BindPane.swift:672` 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.
D4 · Code Duplication · Duplicated block (3–7 lines × 6) · ×1
  • Duplicated block (3–7 lines × 6) Multiplex/Views/Terminal/TerminalGuidePictograms.swift:127 — Multiplex/Views/Terminal/TerminalGuidePictograms.swift:127-131 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:132-138 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:255-261 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:263-265 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:440-443 | Multiplex/Views/Terminal/TerminalGuidePictograms.swift:565-568 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:131` calls `addLine`, `CGPoint` and `Multiplex/Views/Terminal/TerminalGuidePictograms.swift:443` 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.
D4 · Code Duplication · Duplicated block (6 lines × 20) · ×1
  • Duplicated block (6 lines × 20) Multiplex/Views/Deck/AddHostSheet.swift:2308 — Multiplex/Views/Deck/AddHostSheet.swift:2308-2313 | Multiplex/Views/Deck/AddHostSheet.swift:2346-2351 | Multiplex/Views/Deck/AddHostSheet.swift:2365-2370 | Multiplex/Views/Deck/AgentPromptSheet.swift:634-639 | Multiplex/Views/Deck/BindPane.swift:752-757 | Multiplex/Views/Deck/BindPane.swift:984-989 | Multiplex/Views/Deck/FleetWall.swift:5343-5348 | Multiplex/Views/Deck/HostGuideSheets.swift:72-77 | Multiplex/Views/Settings/SettingsView.swift:1026-1031 | Multiplex/Views/Settings/SettingsView.swift:1079-1084 | Multiplex/Views/Settings/ThemeEditorView.swift:499-504 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:665-670 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:707-712 | Multiplex/Views/Terminal/CustomAgentCommandPanel.swift:1039-1044 | Multiplex/Views/Terminal/FileViewerFindBar.swift:98-103 | Multiplex/Views/Terminal/FileViewerPane.swift:1924-1929 | Multiplex/Views/Terminal/KeyCommandPanel.swift:969-974 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:497-502 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1433-1438 | Multiplex/Views/Terminal/ViewportPane.swift:698-703 — there are 20 copies across 14 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 20 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/AddHostSheet.swift:2308` it does not close everything it opens, so those 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, `Multiplex/Views/Deck/HostGuideSheets.swift:69` calls `UIStackView` and `Multiplex/Views/Deck/AddHostSheet.swift:2307` 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.
D4 · Code Duplication · Duplicated block (6 lines × 11) · ×1
  • Duplicated block (6 lines × 11) Multiplex/Design/Chassis.swift:644 — Multiplex/Design/Chassis.swift:644-649 | Multiplex/Views/Deck/AddHostSheet.swift:1023-1028 | Multiplex/Views/Deck/AddHostSheet.swift:2242-2247 | Multiplex/Views/Deck/BindPane.swift:681-686 | Multiplex/Views/Deck/FleetWall.swift:3357-3362 | Multiplex/Views/Deck/FleetWall.swift:4946-4951 | Multiplex/Views/Settings/LicensesView.swift:418-423 | Multiplex/Views/Settings/ReleaseNotesView.swift:164-169 | Multiplex/Views/Settings/SettingsView.swift:972-977 | Multiplex/Views/Terminal/DictationChrome.swift:94-99 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:638-643 — there are 11 copies across 9 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 11 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:644` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) Multiplex/Views/Deck/BindPane.swift:532 — Multiplex/Views/Deck/BindPane.swift:532-537 | Multiplex/Views/Deck/ConnectionStatsView.swift:573-578 | Multiplex/Views/Deck/FleetWall.swift:3413-3418 | Multiplex/Views/Deck/FleetWall.swift:3723-3728 | Multiplex/Views/Deck/FleetWall.swift:3932-3937 | Multiplex/Views/Settings/SettingsView.swift:989-1000 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1274-1279 — there are 7 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 7 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Deck/BindPane.swift:532` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Multiplex/Views/Deck/ConnectionStatsView.swift:572` calls `padded` and `Multiplex/Views/Deck/BindPane.swift:530` 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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) Multiplex/Design/Chassis.swift:359 — Multiplex/Design/Chassis.swift:359-366 | Multiplex/Views/Deck/FleetWall.swift:3065-3072 | Multiplex/Views/Settings/ProPaywallView.swift:568-575 | Multiplex/Views/Settings/SettingsView.swift:1454-1461 | Multiplex/Views/Terminal/UMDBarUIKit.swift:1950-1957 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (4–6 lines × 5) · ×1
  • Duplicated block (4–6 lines × 5) Multiplex/Views/Settings/LicensesView.swift:258 — Multiplex/Views/Settings/LicensesView.swift:258-263 | Multiplex/Views/Terminal/AgentHelperStrip.swift:445-450 | Multiplex/Views/Terminal/AgentHistoryPanel.swift:308-313 | Multiplex/Views/Terminal/FileViewerPane.swift:4126-4129 | Multiplex/Views/Terminal/ShortcutPanel.swift:125-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Views/Settings/LicensesView.swift:258` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 20) · ×1
  • Duplicated block (5 lines × 20) Multiplex/Design/Chassis.swift:629 — Multiplex/Design/Chassis.swift:629-633 | Multiplex/Views/Deck/AddHostSheet.swift:2217-2221 | Multiplex/Views/Deck/AddHostSheet.swift:2334-2338 | Multiplex/Views/Deck/AgentPromptSheet.swift:296-300 | Multiplex/Views/Deck/BindPane.swift:533-537 | Multiplex/Views/Deck/BindPane.swift:658-662 | Multiplex/Views/Deck/BindPane.swift:895-899 | Multiplex/Views/Deck/ConnectionStatsView.swift:574-578 | Multiplex/Views/Deck/FleetWall.swift:3414-3418 | Multiplex/Views/Deck/FleetWall.swift:3724-3728 | Multiplex/Views/Deck/FleetWall.swift:3933-3937 | Multiplex/Views/Deck/FleetWall.swift:4907-4911 | Multiplex/Views/Deck/FleetWall.swift:4927-4931 | Multiplex/Views/Settings/LicensesView.swift:285-289 | Multiplex/Views/Settings/SettingsView.swift:948-952 | Multiplex/Views/Settings/SettingsView.swift:990-1000 | Multiplex/Views/Terminal/FileViewerPane.swift:452-456 | Multiplex/Views/Terminal/FileViewerPane.swift:2044-2048 | Multiplex/Views/Terminal/TerminalGuideViewController.swift:285-289 | Multiplex/Views/Terminal/TerminalPaneUIKit.swift:1275-1279 — there are 20 copies across 11 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 20 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Multiplex/Design/Chassis.swift:629` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Multiplex/Views/Deck/AgentPromptSheet.swift:294` calls `UIKitTallyBorderedView` and `Multiplex/Views/Terminal/FileViewerPane.swift:451` 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) Multiplex/Views/Terminal/FileViewerPane.swift:1015 — Multiplex/Views/Terminal/FileViewerPane.swift:1015-1019 | Multiplex/Views/Terminal/ViewportPane.swift:1328-1332 | Multiplex/Views/Terminal/ViewportPane.swift:1545-1549 — 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×1
  • Sync-over-async blocking Multiplex/Services/Mosh/MoshSession.swift:361 — `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Minor — 11 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate Multiplex/App/UIKitSceneRootViewController.swift:514 — `GlassPrototype.enabled && GlassSelectionState.shared.isGlass` appears character-identically in 3 files — Multiplex/App/UIKitSceneRootViewController.swift, Multiplex/Design/Chassis.swift, Multiplex/Views/Terminal/TerminalVisionOrnaments.swift. 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 Multiplex/Models/AgentSignature.swift:128 — `allowedControl || !CharacterSet.controlCharacters.contains(scalar)` appears character-identically in 4 files — Multiplex/Models/AgentSignature.swift, Multiplex/Models/ComposedText.swift, Multiplex/Models/SessionScript.swift, Multiplex/Services/TmuxProbe.swift. 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 Multiplex/Views/Terminal/FileAttachMenu.swift:119 — `enabled && FileAttachAvailability.cameraAvailable` appears character-identically in 2 files — Multiplex/Views/Terminal/FileAttachMenu.swift, Multiplex/Views/Terminal/UMDBarUIKit.swift. 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 Multiplex/Models/AgentSignature.swift:127 — `scalar.value == 0x09 || scalar.value == 0x0A` appears character-identically in 4 files — Multiplex/Models/AgentSignature.swift, Multiplex/Models/ComposedText.swift, Multiplex/Models/SessionScript.swift, Multiplex/Services/TmuxProbe.swift. 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.
D21 · Naming Consistency · `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` · ×2
  • `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` Vendor/SwiftTerm/Sources/SwiftTerm/Mac/MacTerminalView.swift:1129 — 38 of 40 names in project Vendor~SwiftTerm~CaptureOutput spell the token `UI` (38 of 40; unit: names in project Vendor~SwiftTerm~CaptureOutput containing `UI`). Peers: MultiplexApplicationDelegate.adoptPersistedSwiftUIScene (Multiplex/App/MultiplexApp.swift:56); TerminalGlassWindowMount.makeUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:544); TerminalGlassWindowMount.updateUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:551); TerminalGlassWindowMount.dismantleUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:559); UIKitLegacySceneMigrationPolicy.swiftUIDelegateClassName (Multiplex/Models/UIKitScenePresentationPlan.swift:228). Rename to `updateUIClosed`. [rule N6]
  • `updateUiClosed` spells `Ui` where 38 names in the project spell it `UI` Vendor/SwiftTerm/Sources/SwiftTerm/iOS/iOSTerminalView.swift:684 — 38 of 40 names in project Vendor~SwiftTerm~CaptureOutput spell the token `UI` (38 of 40; unit: names in project Vendor~SwiftTerm~CaptureOutput containing `UI`). Peers: MultiplexApplicationDelegate.adoptPersistedSwiftUIScene (Multiplex/App/MultiplexApp.swift:56); TerminalGlassWindowMount.makeUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:544); TerminalGlassWindowMount.updateUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:551); TerminalGlassWindowMount.dismantleUIViewController (Multiplex/App/UIKitSceneRootViewController.swift:559); UIKitLegacySceneMigrationPolicy.swiftUIDelegateClassName (Multiplex/Models/UIKitScenePresentationPlan.swift:228). Rename to `updateUIClosed`. [rule N6]
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:16 — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Minor — 14 finding(s)
D10 · Test Quality · Skipped (documented) · ×13
  • Skipped (documented): aSixtyFourMiBFragmentedWriteCommits Vendor/SwiftTerm/Tests/SwiftTermTests/KittyClipboardProtocolTests.swift:1435 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittySharedMemoryLoad Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:218 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittySharedMemoryBoundsRejected Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:245 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittyUnicodePlaceholderFrameFromSharedMemory Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:314 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittySharedMemoryNameWithoutLeadingSlashIsRefused Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:339 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittySharedMemoryOffsetCountsTheImageFromTheOffset Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:364 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): testKittySharedMemorySizeIsClampedToTheObject Vendor/SwiftTerm/Tests/SwiftTermTests/KittyTransmissionTests.swift:392 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): repeatedOnOffTogglesAreStable Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:45 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): settingTheSameValueDoesNothing Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:67 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): togglingManyViewsTogether Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:85 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): requestRedrawIsSafeInEitherState Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:119 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): opaqueBackgroundCoversAZeroSizedMetalSurface Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:139 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): translucentMetalBackgroundKeepsTheHostLayerClear Vendor/SwiftTerm/Tests/SwiftTermTests/MetalToggleTests.swift:156 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: fastlane — `fastlane` is resolved to 2.237.0 in the committed REDACTED but 2.242.0 is the current release on rubygems.org, and Gemfile declares no version requirement for it, so nothing but the lockfile is holding it back. This build is therefore missing every fix published since, including any security fix. Run `bundle update fastlane` 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-d6943c369fd14c3ea9261535080c4fd4/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=257" --report-format json --report-path /tmp/watchdog-gitleaks-d6943c369fd14c3ea9261535080c4fd4/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d6943c369fd14c3ea9261535080c4fd4/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .3artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 36 file(s) — `Multiplex/App/MultiplexApp.swift`, `Multiplex/Models/Bind/BindProtocol.swift`, `Multiplex/Models/KeyCommand.swift`, `Multiplex/Models/SidePanel.swift`, `Multiplex/Services/AppLockStore.swift`, … (+31 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e674-3e22-7035-9d30-679992e310c6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md