{"$schema":"https://json.schemastore.org/sarif-2.1.0.json","version":"2.1.0","runs":[{"tool":{"driver":{"name":"codehealth","informationUri":"https://codehealth.canine.dev","rules":[{"id":"D1","name":"Cyclomatic Complexity","shortDescription":{"text":"Cyclomatic Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D1"},{"id":"D2","name":"Cognitive Complexity","shortDescription":{"text":"Cognitive Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D2"},{"id":"D3","name":"God Classes","shortDescription":{"text":"God Classes"},"helpUri":"https://codehealth.canine.dev/dimensions/D3"},{"id":"D4","name":"Code Duplication","shortDescription":{"text":"Code Duplication"},"helpUri":"https://codehealth.canine.dev/dimensions/D4"},{"id":"D6","name":"Cohesion (LCOM4)","shortDescription":{"text":"Cohesion (LCOM4)"},"helpUri":"https://codehealth.canine.dev/dimensions/D6"},{"id":"D8","name":"Code Coverage","shortDescription":{"text":"Code Coverage"},"helpUri":"https://codehealth.canine.dev/dimensions/D8"},{"id":"D9","name":"Test Distribution","shortDescription":{"text":"Test Distribution"},"helpUri":"https://codehealth.canine.dev/dimensions/D9"},{"id":"D10","name":"Test Quality","shortDescription":{"text":"Test Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D10"},{"id":"D11","name":"Test Reliability","shortDescription":{"text":"Test Reliability"},"helpUri":"https://codehealth.canine.dev/dimensions/D11"},{"id":"D12","name":"Dependency Hygiene","shortDescription":{"text":"Dependency Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/D12"},{"id":"D13","name":"Secret Scanning","shortDescription":{"text":"Secret Scanning"},"helpUri":"https://codehealth.canine.dev/dimensions/D13","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"]}},{"id":"D14","name":"License Compliance","shortDescription":{"text":"License Compliance"},"helpUri":"https://codehealth.canine.dev/dimensions/D14"},{"id":"D15","name":"Churn \u00D7 Complexity Hotspots","shortDescription":{"text":"Churn \u00D7 Complexity Hotspots"},"helpUri":"https://codehealth.canine.dev/dimensions/D15"},{"id":"D17","name":"Explicit Debt","shortDescription":{"text":"Explicit Debt"},"helpUri":"https://codehealth.canine.dev/dimensions/D17"},{"id":"D19","name":"Documentation Quality","shortDescription":{"text":"Documentation Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D19"},{"id":"D20","name":"ADR Quality","shortDescription":{"text":"ADR Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D20"},{"id":"D21","name":"Naming Consistency","shortDescription":{"text":"Naming Consistency"},"helpUri":"https://codehealth.canine.dev/dimensions/D21"},{"id":"D28","name":"Secrets (history)","shortDescription":{"text":"Secrets (history)"},"helpUri":"https://codehealth.canine.dev/dimensions/D28","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"]}},{"id":"D29","name":"Static Analysis (SAST)","shortDescription":{"text":"Static Analysis (SAST)"},"helpUri":"https://codehealth.canine.dev/dimensions/D29","relationships":[{"target":{"id":"CWE-79","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-78","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-94","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-77","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-79","CWE-89","CWE-78","CWE-94","CWE-77"]}},{"id":"D31","name":"IaC \u0026 Container Security","shortDescription":{"text":"IaC \u0026 Container Security"},"helpUri":"https://codehealth.canine.dev/dimensions/D31","relationships":[{"target":{"id":"CWE-1032","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-732","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-16","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1032","CWE-732","CWE-16"]}},{"id":"D34","name":"Knowledge Freshness","shortDescription":{"text":"Knowledge Freshness"},"helpUri":"https://codehealth.canine.dev/dimensions/D34"},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"D36","name":"Supply-chain Provenance \u0026 Signing","shortDescription":{"text":"Supply-chain Provenance \u0026 Signing"},"helpUri":"https://codehealth.canine.dev/dimensions/D36","relationships":[{"target":{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-494","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1357","CWE-494"]}},{"id":"D37","name":"Vulnerability-disclosure Policy","shortDescription":{"text":"Vulnerability-disclosure Policy"},"helpUri":"https://codehealth.canine.dev/dimensions/D37","relationships":[{"target":{"id":"CWE-1059","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1059"]}},{"id":"AX10","name":"Code composition","shortDescription":{"text":"Code composition"},"helpUri":"https://codehealth.canine.dev/dimensions/AX10"},{"id":"AX9","name":"CQS / query purity","shortDescription":{"text":"CQS / query purity"},"helpUri":"https://codehealth.canine.dev/dimensions/AX9"},{"id":"AXB2","name":"Runtime readiness","shortDescription":{"text":"Runtime readiness"},"helpUri":"https://codehealth.canine.dev/dimensions/AXB2"},{"id":"DM4","name":"Rich vs anemic domain model","shortDescription":{"text":"Rich vs anemic domain model"},"helpUri":"https://codehealth.canine.dev/dimensions/DM4"},{"id":"DM5","name":"Encapsulated state","shortDescription":{"text":"Encapsulated state"},"helpUri":"https://codehealth.canine.dev/dimensions/DM5"},{"id":"DM6","name":"Domain \u2194 infrastructure boundary","shortDescription":{"text":"Domain \u2194 infrastructure boundary"},"helpUri":"https://codehealth.canine.dev/dimensions/DM6"},{"id":"M1","name":"Documentation (README)","shortDescription":{"text":"Documentation (README)"},"helpUri":"https://codehealth.canine.dev/dimensions/M1"},{"id":"M2","name":"Architecture documentation","shortDescription":{"text":"Architecture documentation"},"helpUri":"https://codehealth.canine.dev/dimensions/M2"},{"id":"M3","name":"Folder \u0026 project structure","shortDescription":{"text":"Folder \u0026 project structure"},"helpUri":"https://codehealth.canine.dev/dimensions/M3"},{"id":"M4","name":"Documentation accuracy","shortDescription":{"text":"Documentation accuracy"},"helpUri":"https://codehealth.canine.dev/dimensions/M4"},{"id":"P1","name":"CI/CD gates","shortDescription":{"text":"CI/CD gates"},"helpUri":"https://codehealth.canine.dev/dimensions/P1"},{"id":"P12","name":"CI test-gate honesty","shortDescription":{"text":"CI test-gate honesty"},"helpUri":"https://codehealth.canine.dev/dimensions/P12"},{"id":"P2","name":"Observability","shortDescription":{"text":"Observability"},"helpUri":"https://codehealth.canine.dev/dimensions/P2"},{"id":"P3","name":"Security \u0026 performance tooling","shortDescription":{"text":"Security \u0026 performance tooling"},"helpUri":"https://codehealth.canine.dev/dimensions/P3"},{"id":"P4","name":"Deployment \u0026 Rollback","shortDescription":{"text":"Deployment \u0026 Rollback"},"helpUri":"https://codehealth.canine.dev/dimensions/P4"},{"id":"P5","name":"DR \u0026 Backup","shortDescription":{"text":"DR \u0026 Backup"},"helpUri":"https://codehealth.canine.dev/dimensions/P5"},{"id":"P6","name":"Release Hygiene","shortDescription":{"text":"Release Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/P6"},{"id":"PF2","name":"Allocation hygiene","shortDescription":{"text":"Allocation hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/PF2"},{"id":"X10","name":"Duplicated predicate","shortDescription":{"text":"Duplicated predicate"},"helpUri":"https://codehealth.canine.dev/dimensions/X10"},{"id":"X32","name":"Type resolved by simple name across every loaded assembly","shortDescription":{"text":"Type resolved by simple name across every loaded assembly"},"helpUri":"https://codehealth.canine.dev/dimensions/X32"},{"id":"X6","name":"Hand-rolled structured-format parsing","shortDescription":{"text":"Hand-rolled structured-format parsing"},"helpUri":"https://codehealth.canine.dev/dimensions/X6"},{"id":"X9","name":"Subsumed condition operand","shortDescription":{"text":"Subsumed condition operand"},"helpUri":"https://codehealth.canine.dev/dimensions/X9"}]}},"results":[{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureCoordinator.startAutoScrolling (cyclomatic 47): ScrollingCaptureCoordinator.startAutoScrolling has cyclomatic complexity 47 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":255}}}],"partialFingerprints":{"codehealthFindingId/v1":"0ceebf1e32223908d2fd834ebc6e453585f8d0077b50501813ed298cd1724628"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureCoordinator.refreshPreview (cyclomatic 46): ScrollingCaptureCoordinator.refreshPreview has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":761}}}],"partialFingerprints":{"codehealthFindingId/v1":"a6acfe407a37ac43a97d35344f7a8297357b1b98c8ad15e465194ca3f2949eb5"}},{"ruleId":"D1","level":"warning","message":{"text":"KeyboardShortcutManager.loadShortcuts (cyclomatic 41): KeyboardShortcutManager.loadShortcuts has cyclomatic complexity 41 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file\u0027s highest cyclomatic complexity: ShortcutConfig.keyCodeToString (cyclomatic 100) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1201}}}],"partialFingerprints":{"codehealthFindingId/v1":"aca5dfe5596d3b8983160e3e2413d26a0b392c55141090697d9f44ca37e36b70"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.mouseUp (cyclomatic 40): DrawingCanvasNSView.mouseUp has cyclomatic complexity 40 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1313}}}],"partialFingerprints":{"codehealthFindingId/v1":"5268a7e5091fa7f7dcee9fcdf981a180e59e92f68294fcb9cd3edf589e9725f9"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateWindow.performKeyEquivalent (cyclomatic 37): AnnotateWindow.performKeyEquivalent has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":175}}}],"partialFingerprints":{"codehealthFindingId/v1":"41291aea85b4bcf05ca7459f36214179d4a41d1c4af067992d11672690273b79"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureStitcher.append (cyclomatic 37): ScrollingCaptureStitcher.append has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":372}}}],"partialFingerprints":{"codehealthFindingId/v1":"df5350867dc9db7a9e4702e65f483b612aed69d65ab579cb18493d4ebc1cc627"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.mouseDragged (cyclomatic 34): DrawingCanvasNSView.mouseDragged has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1031}}}],"partialFingerprints":{"codehealthFindingId/v1":"f36a7fb185c6dcd4223ec92ebe65a2c6dbeae31789300836db42c3b485ad846b"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingSession.appendVideoSample (cyclomatic 33): RecordingSession.appendVideoSample has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":161}}}],"partialFingerprints":{"codehealthFindingId/v1":"00a84dbb88f39e7a2301c05e8251463031097fa42e6eded662eb5843466921c9"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateQuickPropertiesBar.activePropertiesContent (cyclomatic 33): AnnotateQuickPropertiesBar.activePropertiesContent has cyclomatic complexity 33 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"11f25259a45415e1ccde8b7482c224a9428e5be0db7bc9b10f4e244cdd2811a8"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.keyDown (cyclomatic 32): DrawingCanvasNSView.keyDown has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":515}}}],"partialFingerprints":{"codehealthFindingId/v1":"c5297162b97acdc955b0e30e5aeb589d55c9fd45d5424f242e1f18248a5c4519"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorExporter.exportWithZooms (cyclomatic 30): VideoEditorExporter.exportWithZooms has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":206}}}],"partialFingerprints":{"codehealthFindingId/v1":"90dd7a54314b8aad1b80ab4bbcc3734796a172313c878264810f49fa20129d54"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateExporter.renderFlatFinalImage (cyclomatic 29): AnnotateExporter.renderFlatFinalImage has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":403}}}],"partialFingerprints":{"codehealthFindingId/v1":"e489cb43c8d2cefb93e11033c7634a84ada873018a66f8f29fdc382654bceb26"}},{"ruleId":"D1","level":"warning","message":{"text":"CloudCredentialFormView.body (cyclomatic 29): CloudCredentialFormView.body has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":816}}}],"partialFingerprints":{"codehealthFindingId/v1":"61e4288adbc7f8b8e746c6003262e7c467da07e1b1622acc4d3b11550242c16c"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.updateAnnotationProperties (cyclomatic 27): AnnotateState.updateAnnotationProperties has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3679}}}],"partialFingerprints":{"codehealthFindingId/v1":"5bde46016e3e95e55de5d969d7078effdb79ca3abab775424bd20e207b8c2d72"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotationFactory.createAnnotation (cyclomatic 27): AnnotationFactory.createAnnotation has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"1c30e60f3fe4f3ffb35715981b5e19c1edddd38cec05298c18edd0d1e4ba3997"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureCoordinator.updatePreviewTruthState (cyclomatic 27): ScrollingCaptureCoordinator.updatePreviewTruthState has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":1782}}}],"partialFingerprints":{"codehealthFindingId/v1":"387ed885e76db70211a4776a7138506a1c33dd942424e00e71e4b01d4ee4c75d"}},{"ruleId":"D1","level":"warning","message":{"text":"KeyboardShortcutManager.saveShortcuts (cyclomatic 26): KeyboardShortcutManager.saveShortcuts has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file\u0027s highest cyclomatic complexity: ShortcutConfig.keyCodeToString (cyclomatic 100) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1127}}}],"partialFingerprints":{"codehealthFindingId/v1":"7c32a426b251004442e5d009ba57ffad5b654a587b167bfb2f61deb5c465ca55"}},{"ruleId":"D1","level":"warning","message":{"text":"QuickAccessCardView.body (cyclomatic 26): QuickAccessCardView.body has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"1f762159d3cd9624a98469f498aedb89da543d0c8c130c759b72c393d8f81ed2"}},{"ruleId":"D1","level":"warning","message":{"text":"CaptureSettingsView.body (cyclomatic 25): CaptureSettingsView.body 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":117}}}],"partialFingerprints":{"codehealthFindingId/v1":"d5e7c349a4bd381920d692d62b4d89c01cdc3b36d03ed093f2eabcffaefd9837"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureAccuracyBenchmark.run (cyclomatic 24): ScrollingCaptureAccuracyBenchmark.run 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift"},"region":{"startLine":165}}}],"partialFingerprints":{"codehealthFindingId/v1":"50ab46193aa043e89287b9363980aa9fc8ab84455a9c1015b6da40cebb066e3a"}},{"ruleId":"D1","level":"warning","message":{"text":"PostCaptureActionHandler.executeActions (cyclomatic 23): PostCaptureActionHandler.executeActions has cyclomatic complexity 23 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/PostCaptureActionHandler.swift"},"region":{"startLine":281}}}],"partialFingerprints":{"codehealthFindingId/v1":"69e2cd2d602b661f06f80966f5a197755f3dab6580b7a4db5cdb93292d916779"}},{"ruleId":"D1","level":"warning","message":{"text":"KeyboardShortcutManager.unregisterAllShortcuts (cyclomatic 23): KeyboardShortcutManager.unregisterAllShortcuts has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file\u0027s highest cyclomatic complexity: ShortcutConfig.keyCodeToString (cyclomatic 100) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1808}}}],"partialFingerprints":{"codehealthFindingId/v1":"f77bcb74692b22d60b73b6d01adcae8e3216371dabd8d18bbb8e39b431e85420"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateCanvasView.body (cyclomatic 23): AnnotateCanvasView.body has cyclomatic complexity 23 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":88}}}],"partialFingerprints":{"codehealthFindingId/v1":"f3f80a29d2a625d09a512b9d47698ad92c0f43008406d844b6fafacf421cdf4c"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateWindow.sendEvent (cyclomatic 23): AnnotateWindow.sendEvent has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":364}}}],"partialFingerprints":{"codehealthFindingId/v1":"49dd76097808afe809d3f94a06bf09a0021bf1c00c453af461e109f6c9b816b0"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureStitcher.isAcceptable (cyclomatic 23): ScrollingCaptureStitcher.isAcceptable has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1397}}}],"partialFingerprints":{"codehealthFindingId/v1":"0959ce75a1ef2d66d0a106e01bd0ab6171d9c9811e15fa5308f49730496a13ed"}},{"ruleId":"D1","level":"warning","message":{"text":"AreaSelectionMagnifier.update (cyclomatic 22): AreaSelectionMagnifier.update has cyclomatic complexity 22 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":340}}}],"partialFingerprints":{"codehealthFindingId/v1":"a1ff28a05a836cee27da4fb6f47aff3747dd35a79b0288ae160482a370b45ece"}},{"ruleId":"D1","level":"warning","message":{"text":"LiquidGlassSegmentedControl.body (cyclomatic 22): LiquidGlassSegmentedControl.body has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSegmentedControl.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"6f7b1634c7d685bb30cfe6b4ded5115a6bbeb8836c7d7714d869c8b5b48c247d"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.annotationPropertiesWillChange (cyclomatic 21): AnnotateState.annotationPropertiesWillChange has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3838}}}],"partialFingerprints":{"codehealthFindingId/v1":"a8a7a31a223647217d226dee307ffe045dc550fca9d10e7bed8c6e0c3b24f0bc"}},{"ruleId":"D1","level":"warning","message":{"text":"InlineAreaAnnotateRootView.body (cyclomatic 21): InlineAreaAnnotateRootView.body 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":234}}}],"partialFingerprints":{"codehealthFindingId/v1":"d76e3f2f0435fa630146905b9e82be880aa1ee73aa4776165553339e09b92108"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureViewModel.captureOCR (cyclomatic 21): ScreenCaptureViewModel.captureOCR 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\u0027s highest cyclomatic complexity: ScreenCaptureViewModel.shortcutTriggered (cyclomatic 24) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2366}}}],"partialFingerprints":{"codehealthFindingId/v1":"c07d3421170a6d4bf27a3f1e4468c196932bf818657b6da4964abe69ba6c8559"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorState.undo (cyclomatic 21): VideoEditorState.undo has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform \u2014 the same kind of value, with no behaviour of its own \u2014 a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (VideoEditorState.redo) has the same decision points, in the same order, at the same nesting depths \u2014 so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1941}}}],"partialFingerprints":{"codehealthFindingId/v1":"f47c5d7331698695d222b9011e197d5ab363b9a5c7e6d6fcdd167aa68cc9f607"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorState.redo (cyclomatic 21): VideoEditorState.redo has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform \u2014 the same kind of value, with no behaviour of its own \u2014 a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (VideoEditorState.undo) has the same decision points, in the same order, at the same nesting depths \u2014 so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":2045}}}],"partialFingerprints":{"codehealthFindingId/v1":"e567f4bd18a259e587d3965fb0cff50e7677b478cd2ded9ef8085a38d8342ad3"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenRecordingManager.prepareRecording (cyclomatic 21): ScreenRecordingManager.prepareRecording 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":790}}}],"partialFingerprints":{"codehealthFindingId/v1":"cf2074b61eb78281f70ce71a8f26c7cebea6f8ae003327a6a8d3f6badc64bc45"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.applySharedParameterDefaults (cyclomatic 20): AnnotateState.applySharedParameterDefaults 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":4586}}}],"partialFingerprints":{"codehealthFindingId/v1":"b9e1ec132fcc2d2af260a25fb8638073e2e9c33b9ddc533b4f28998a01601a05"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureViewModel.startAreaCapture (cyclomatic 20): ScreenCaptureViewModel.startAreaCapture 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. This is NOT this file\u0027s highest cyclomatic complexity: ScreenCaptureViewModel.shortcutTriggered (cyclomatic 24) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":657}}}],"partialFingerprints":{"codehealthFindingId/v1":"ab0a15efcbb9c6c18a1015e389f485398587ef3744ad8db4b12d85d5ef7c7b38"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.mouseDown (cyclomatic 20): DrawingCanvasNSView.mouseDown 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":817}}}],"partialFingerprints":{"codehealthFindingId/v1":"fadfde56c3009f8905183f10aa1a95c9018b382068e8b7904f1420f6b9ac91e7"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.updateDefaultAnnotationProperties (cyclomatic 19): AnnotateState.updateDefaultAnnotationProperties 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":4654}}}],"partialFingerprints":{"codehealthFindingId/v1":"2811b002ad638f9a7593fc611e55d8822cd5b6849cda76030cd7c0fc87e8e913"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureViewModel.startFrozenAreaSelection (cyclomatic 19): ScreenCaptureViewModel.startFrozenAreaSelection has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file\u0027s highest cyclomatic complexity: ScreenCaptureViewModel.shortcutTriggered (cyclomatic 24) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1037}}}],"partialFingerprints":{"codehealthFindingId/v1":"fe73b2866a8b090cc1c72433a8b1432dbc5fe433d7ce918cbdc9632f46b77d33"}},{"ruleId":"D1","level":"warning","message":{"text":"AreaSelectionController.startSelectionSession (cyclomatic 19): AreaSelectionController.startSelectionSession 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"3f55cc8d4020ae6e98e64f07a40d0298c31c4c760b3caf742f1dc4efe81494e3"}},{"ruleId":"D1","level":"warning","message":{"text":"WindowSelectionQueryService.prepareSnapshot (cyclomatic 19): WindowSelectionQueryService.prepareSnapshot 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"5be0fb31c9107f30a730dcd11e57882a5f6fa3483b33fc0eae68db3315d54d58"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateBottomBarView.handleCloudUpload (cyclomatic 19): AnnotateBottomBarView.handleCloudUpload 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"7436e3ec6e4db69b87445e478ac5e5b2004c3c2e25dc281981514b2d166a6bbb"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.handleCropResize (cyclomatic 19): DrawingCanvasNSView.handleCropResize 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 \u2014 the same kind of value, with no behaviour of its own \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2382}}}],"partialFingerprints":{"codehealthFindingId/v1":"c8c740da5248e3c96c22c20165c4e79c47b0ff3b8e12e83cca545ff6a460fc03"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.autoCropToContent (cyclomatic 18): AnnotateState.autoCropToContent 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3120}}}],"partialFingerprints":{"codehealthFindingId/v1":"89f7881d9e2e1c0fefebb9329ccd05f6d06a5a5f011027dd3132877c9a478586"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureViewModel.prepareLazyFrozenDisplay (cyclomatic 18): ScreenCaptureViewModel.prepareLazyFrozenDisplay has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file\u0027s highest cyclomatic complexity: ScreenCaptureViewModel.shortcutTriggered (cyclomatic 24) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1741}}}],"partialFingerprints":{"codehealthFindingId/v1":"6066792af4e9e06393ca99b8937724d1a9cd9a4e6927a1137581243f19923f73"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.applyGestureResize (cyclomatic 18): DrawingCanvasNSView.applyGestureResize 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1229}}}],"partialFingerprints":{"codehealthFindingId/v1":"0d48f98504aae184f48aa1c056b89da601ed511b976e2c48fa68d8052d717f3c"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotationRenderer.drawCurrentStroke (cyclomatic 18): AnnotationRenderer.drawCurrentStroke 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":128}}}],"partialFingerprints":{"codehealthFindingId/v1":"c01ecb7f441e9ee018fca2c38d2844eaaa8248641a4d8622bf1c8c70fd049f14"}},{"ruleId":"D1","level":"warning","message":{"text":"ToolError.errorDescription (cyclomatic 17): ToolError.errorDescription has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform \u2014 the same kind of value, with no behaviour of its own \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/localization/CatalogTool.swift"},"region":{"startLine":60}}}],"partialFingerprints":{"codehealthFindingId/v1":"ea4132fcdb2fa3f5b2a48d5ef979cdd813ef84ecedb2317bf86cb73c43e9fda0"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingSession.appendAudioSample (cyclomatic 17): RecordingSession.appendAudioSample has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":275}}}],"partialFingerprints":{"codehealthFindingId/v1":"0638d8742e5b3060b420c296d21430b5fc3400bdb60971a5e64d7e3a5f0a6b46"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingSession.appendMicrophoneSample (cyclomatic 17): RecordingSession.appendMicrophoneSample has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":319}}}],"partialFingerprints":{"codehealthFindingId/v1":"b32b9fcafcb5b3a95171216ec754d990eb34a7aece357664acd6bc5cd607a455"}},{"ruleId":"D1","level":"warning","message":{"text":"SplashWindowController.showWindow (cyclomatic 17): SplashWindowController.showWindow 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Splash/SplashWindow.swift"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"0c681d31d9a0f896be52630f343f52b31a5f57f8a06f97e3834011ae47f4b5c8"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorState.restoreSessionIfNeeded (cyclomatic 17): VideoEditorState.restoreSessionIfNeeded 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1091}}}],"partialFingerprints":{"codehealthFindingId/v1":"968499b7b7a625c794f03b0977d324e1f153be83cdafa3b3cdb1160bb89763ab"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorState.scheduleSpeedPreviewRebuild (cyclomatic 17): VideoEditorState.scheduleSpeedPreviewRebuild has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1401}}}],"partialFingerprints":{"codehealthFindingId/v1":"9ef655829281d5be6bbd0e5afdd49a590d7fcc224fe46c2d79cdbd2b6be6e697"}},{"ruleId":"D1","level":"warning","message":{"text":"AreaSelectionController.runSessionPresentationCheck (cyclomatic 17): AreaSelectionController.runSessionPresentationCheck has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":836}}}],"partialFingerprints":{"codehealthFindingId/v1":"076b17f93431d7478f22369e4832fd76ac293ca896dcfc379741633254bff772"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingAudioLevelMeter.rms (cyclomatic 17): RecordingAudioLevelMeter.rms has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/RecordingAudioLevelMeter.swift"},"region":{"startLine":120}}}],"partialFingerprints":{"codehealthFindingId/v1":"26cea88ea5dd3ffb2be2362702f4d27181e32f74e9f66a73b9aca03a1c9e0436"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureManager.scanTransparentFringeBounds (cyclomatic 17): ScreenCaptureManager.scanTransparentFringeBounds has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":2294}}}],"partialFingerprints":{"codehealthFindingId/v1":"2d25ceb8fca00767b45ee13b40c83502e59fff8e8f2d1dade3a8248b8d4d5e2c"}},{"ruleId":"D1","level":"warning","message":{"text":"WindowSelectionQueryService.captureImmediateMenuBarPopoverCaptures (cyclomatic 17): WindowSelectionQueryService.captureImmediateMenuBarPopoverCaptures has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":176}}}],"partialFingerprints":{"codehealthFindingId/v1":"1638bb441b0b8ad8307afd1fd908357aa8522d9d5aeddb41b9458515923f3f81"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotationRenderer.drawBlur (cyclomatic 17): AnnotationRenderer.drawBlur has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform \u2014 the same kind of value, with no behaviour of its own \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":641}}}],"partialFingerprints":{"codehealthFindingId/v1":"bf638286483a6d2086706fece812745064b30c091356be26ec3b94911870dc0c"}},{"ruleId":"D1","level":"warning","message":{"text":"HistoryFloatingPanel.performKeyEquivalent (cyclomatic 17): HistoryFloatingPanel.performKeyEquivalent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanel.swift"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"a8246690bda70f5dfa3f4071a48a6267e9c0a1fc916a5a1f87a1206a518db14e"}},{"ruleId":"D1","level":"warning","message":{"text":"SnapzyOnboardingBarSegment.body (cyclomatic 17): SnapzyOnboardingBarSegment.body 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyOnboardingActionBar.swift"},"region":{"startLine":96}}}],"partialFingerprints":{"codehealthFindingId/v1":"2e05522a332a67eba10af43d5fa34a741d3480e44a9b0fb99b69081cd084816b"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingRegionOverlayView.calculateResizedRect (cyclomatic 17): RecordingRegionOverlayView.calculateResizedRect has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform \u2014 the same kind of value, with no behaviour of its own \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":429}}}],"partialFingerprints":{"codehealthFindingId/v1":"5cb64a57494f7156224f448035f5118573ed844dab7c880acdab7876a94e0155"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingRegionOverlayView.drawGuidance (cyclomatic 17): RecordingRegionOverlayView.drawGuidance 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":802}}}],"partialFingerprints":{"codehealthFindingId/v1":"211cfd32c24bf6ae3d0919ba731ebb8283ae121d1225181218a1b1f87f2a8fd2"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureCoordinator.finish (cyclomatic 17): ScrollingCaptureCoordinator.finish 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":600}}}],"partialFingerprints":{"codehealthFindingId/v1":"e391893a443cbc987b280e3e0315a3375c9e376ca6dfb9a7aadae519f4daaa80"}},{"ruleId":"D1","level":"warning","message":{"text":"LiquidGlassBarSegment.body (cyclomatic 17): LiquidGlassBarSegment.body 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassActionBar.swift"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"93647cb1f76e81595c276c6c3983a01fe21d0b23ad6ddc7efbfc3acde1d97d20"}},{"ruleId":"D1","level":"warning","message":{"text":"LiquidGlassSurface.body (cyclomatic 17): LiquidGlassSurface.body has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift"},"region":{"startLine":86}}}],"partialFingerprints":{"codehealthFindingId/v1":"1cbb9011bbd85f13cfbe3f8ce8daa99eb0c6ebced3ce787bada1019f3f6fad06"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateState.visionSuggestedAutoCropRect (cyclomatic 16): AnnotateState.visionSuggestedAutoCropRect has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3176}}}],"partialFingerprints":{"codehealthFindingId/v1":"36ad6ec19f4c774c3e73a2ebee4e1a161032aa6e7c11a4ea870f79f97b3cb946"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateTextSnapping.resolve (cyclomatic 16): AnnotateTextSnapping.resolve 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateTextSnapping.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"2b6d8f5ac72be4cd759921e2cf75f6192dd435af82ed576937d267f94c940fae"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenCaptureViewModel.captureObjectCutout (cyclomatic 16): ScreenCaptureViewModel.captureObjectCutout has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file\u0027s highest cyclomatic complexity: ScreenCaptureViewModel.shortcutTriggered (cyclomatic 24) is higher and carries no row of its own \u2014 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\u0027s figures nor in its score."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2696}}}],"partialFingerprints":{"codehealthFindingId/v1":"be0101ff0c5947131e57300513a111d42d140d071722d78b0b409595b6dc7351"}},{"ruleId":"D1","level":"warning","message":{"text":"RecordingSession.logAudioSampleFormatIfNeeded (cyclomatic 16): RecordingSession.logAudioSampleFormatIfNeeded 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":451}}}],"partialFingerprints":{"codehealthFindingId/v1":"f852afad160483f24e8cf49ca7868cbcdce3f493d14e1698d33ddda542126bdc"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorState.play (cyclomatic 16): VideoEditorState.play 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1231}}}],"partialFingerprints":{"codehealthFindingId/v1":"dd5c41baa6c8f1ec77485d1f4651f4a60d64d9ce1d74a6dd5d49bf430a339d55"}},{"ruleId":"D1","level":"warning","message":{"text":"AreaSelectionOverlayView.handlePrimaryMouseUp (cyclomatic 16): AreaSelectionOverlayView.handlePrimaryMouseUp 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":4690}}}],"partialFingerprints":{"codehealthFindingId/v1":"a74cbbe920fb52f6ad563410f9272aa368e527ded411534b7172833653808062"}},{"ruleId":"D1","level":"warning","message":{"text":"FrozenAreaCaptureSession.cropCompositeImage (cyclomatic 16): FrozenAreaCaptureSession.cropCompositeImage 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":228}}}],"partialFingerprints":{"codehealthFindingId/v1":"38e26e48dfc3397dbddf2e687ef347380ee6e06cf50cac29da790b2ac789ecd3"}},{"ruleId":"D1","level":"warning","message":{"text":"ScreenRecordingManager.makeContentFilter (cyclomatic 16): ScreenRecordingManager.makeContentFilter 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1957}}}],"partialFingerprints":{"codehealthFindingId/v1":"75a54f004fc558cce12a4215007020a567f68f782dcdfc8ac5031f6f9b596902"}},{"ruleId":"D1","level":"warning","message":{"text":"SnapzyConfigurationImporter.collectQuickAccess (cyclomatic 16): SnapzyConfigurationImporter.collectQuickAccess 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":344}}}],"partialFingerprints":{"codehealthFindingId/v1":"1310553290449d6c315f1fe6ee1947ce01d5819ac5932617566b4485af23537c"}},{"ruleId":"D1","level":"warning","message":{"text":"AnnotateBottomBarView.annotateActionButtons (cyclomatic 16): AnnotateBottomBarView.annotateActionButtons 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"506d0079a818292f9ee9b73dbfec9819f2f609bb60cb745f7fee0429ef9e7d04"}},{"ruleId":"D1","level":"warning","message":{"text":"DrawingCanvasNSView.resizeHandleRects (cyclomatic 16): DrawingCanvasNSView.resizeHandleRects 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":671}}}],"partialFingerprints":{"codehealthFindingId/v1":"48c4ae4fe0ec8cb49942a29b4e7f87e743a6749d79f3ab4c3bc1495c70f63698"}},{"ruleId":"D1","level":"warning","message":{"text":"BlurEffectRenderer.drawCIFilterRegion (cyclomatic 16): BlurEffectRenderer.drawCIFilterRegion 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":415}}}],"partialFingerprints":{"codehealthFindingId/v1":"fbe3bafe38e1436177fdb5371966b1cccb939e6bc84691500c51b0c65665f0e9"}},{"ruleId":"D1","level":"warning","message":{"text":"CloudCredentialFormView.saveAndTest (cyclomatic 16): CloudCredentialFormView.saveAndTest 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":1272}}}],"partialFingerprints":{"codehealthFindingId/v1":"f26ce2ca32ba5cf23ca1cedb24616cf26ca52419b84303103df95b80a9e56ea4"}},{"ruleId":"D1","level":"warning","message":{"text":"VideoEditorClipStripView.bodyGesture (cyclomatic 16): VideoEditorClipStripView.bodyGesture 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorClipStripView.swift"},"region":{"startLine":405}}}],"partialFingerprints":{"codehealthFindingId/v1":"748be8801e6b6eb3d4728893262f85d1298bd4101fa25552bc1ac53c5648dd5e"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureCoordinator.waitForSettledAutoScrollFrame (cyclomatic 16): ScrollingCaptureCoordinator.waitForSettledAutoScrollFrame 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":509}}}],"partialFingerprints":{"codehealthFindingId/v1":"1464bd6d6108fa0fe2fc7d9b7f03f1e35bc081bdc83b95f33baef8543297c420"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureSessionMetrics.recordRefreshSuccess (cyclomatic 16): ScrollingCaptureSessionMetrics.recordRefreshSuccess 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 \u2014 the same kind of value, with no behaviour of its own \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureMetrics.swift"},"region":{"startLine":155}}}],"partialFingerprints":{"codehealthFindingId/v1":"ea7f61ad755cf3f0f6f7746159027460952b4caed74f3e832eef2083588a9bc8"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureStitcher.priorPenalty (cyclomatic 16): ScrollingCaptureStitcher.priorPenalty 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1293}}}],"partialFingerprints":{"codehealthFindingId/v1":"e61b248ed0665363812123f30f22f75cc50dd3717b41f9705075e81b0ffb093b"}},{"ruleId":"D1","level":"warning","message":{"text":"ScrollingCaptureStitcher.isAmbiguous (cyclomatic 16): ScrollingCaptureStitcher.isAmbiguous has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1443}}}],"partialFingerprints":{"codehealthFindingId/v1":"eada211b6ec204ff06a5f98762b72b64bc099d9b7191633579760ea259d69855"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.refreshPreview (cognitive 83): ScrollingCaptureCoordinator.refreshPreview has cognitive complexity 83 (threshold 15). Drivers by points: ternaries 14 (37 pts), if/else 21 (36 pts), boolean chains 7, match/switch 1 (2 pts), error handling 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":761}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc7a877f597e2655bbd5a4197bbacf4b0a9064e8034742066ca1199d2ecdaca4"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.mouseUp (cognitive 82): DrawingCanvasNSView.mouseUp has cognitive complexity 82 (threshold 15). Drivers by points: if/else 27 (63 pts), boolean chains 8, loops 2 (5 pts), match/switch 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 42). To reduce it, flatten the nesting: this score is depth rather than breadth \u2014 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\u0027s 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1313}}}],"partialFingerprints":{"codehealthFindingId/v1":"6201b418d6d4dbd75a987cf4a136b1e28c313a0eefcbf0ae628714771a4497c8"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.startAutoScrolling (cognitive 70): ScrollingCaptureCoordinator.startAutoScrolling has cognitive complexity 70 (threshold 15). Drivers by points: if/else 26 (50 pts), boolean chains 15, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":255}}}],"partialFingerprints":{"codehealthFindingId/v1":"384e792400ba4bb5e9a53328a2861fcb6f473a68e99a5605538e36b04e119e44"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.mouseDragged (cognitive 49): DrawingCanvasNSView.mouseDragged has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 12, loops 2 (4 pts), ternaries 1 (2 pts), match/switch 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1031}}}],"partialFingerprints":{"codehealthFindingId/v1":"e26b0a12eeb7605f3765574ff4e14c9fe317c55b3b6b25b0758ae9e8e41becc6"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.keyDown (cognitive 45): DrawingCanvasNSView.keyDown has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 9, match/switch 1, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":515}}}],"partialFingerprints":{"codehealthFindingId/v1":"e4dfd069b10ecbbc1b7c34b14b8aff2450f960bd618c1405888df32a9d574903"}},{"ruleId":"D2","level":"warning","message":{"text":"CloudCredentialFormView.body (cognitive 45): CloudCredentialFormView.body has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (32 pts), ternaries 4 (8 pts), boolean chains 5 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":816}}}],"partialFingerprints":{"codehealthFindingId/v1":"b1f0f30bd31ec50771531f68d1a3d706e7f706b41a47770809577986e522366f"}},{"ruleId":"D2","level":"warning","message":{"text":"WindowSelectionQueryService.prepareSnapshot (cognitive 44): WindowSelectionQueryService.prepareSnapshot has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (30 pts), ternaries 3 (9 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"3c803d600ae0dc3f89f9c9e78f1c0e461bd02609c52d8449ebf2fc0d1f9e8c9b"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingSession.appendVideoSample (cognitive 41): RecordingSession.appendVideoSample has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 15, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":161}}}],"partialFingerprints":{"codehealthFindingId/v1":"bcd48dabc5a734e64edb7ea8b9edab22576c2038c7ef772d6af78dd0226fd00d"}},{"ruleId":"D2","level":"warning","message":{"text":"KeyboardShortcutManager.loadShortcuts (cognitive 40): KeyboardShortcutManager.loadShortcuts has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 20, if/else 20. 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1201}}}],"partialFingerprints":{"codehealthFindingId/v1":"77a9f064c6caeefacc38dbe3fe41fe273de056a44af6172b34b5f7b058663c22"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateWindow.performKeyEquivalent (cognitive 40): AnnotateWindow.performKeyEquivalent has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 13, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":175}}}],"partialFingerprints":{"codehealthFindingId/v1":"8d08f6719d85c6e211d5c16e00b961ad5369e1999751561823f8bfe5c2eaa51f"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.updatePreviewTruthState (cognitive 40): ScrollingCaptureCoordinator.updatePreviewTruthState has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (22 pts), ternaries 3 (9 pts), boolean chains 8, match/switch 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":1782}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a940e3c4a550014cab5f86f2e49f04d2816d36cb80d17e20091228e446d386e"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureStitcher.append (cognitive 40): ScrollingCaptureStitcher.append has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 14, ternaries 7 (8 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":372}}}],"partialFingerprints":{"codehealthFindingId/v1":"cdac19d104360e4da7023f2c7e7c395c8e9c94417c1c1c04bd81e18992391d3a"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.startFrozenAreaSelection (cognitive 38): ScreenCaptureViewModel.startFrozenAreaSelection has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (25 pts), error handling 2 (6 pts), ternaries 1 (4 pts), match/switch 2, boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1037}}}],"partialFingerprints":{"codehealthFindingId/v1":"a8c42b9f4d60e588efd91277dfd55c795074c3ce001f2b4699d059c7df290caf"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorExporter.exportWithZooms (cognitive 38): VideoEditorExporter.exportWithZooms has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 6, loops 3 (4 pts), error handling 2, ternaries 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":206}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f9ae6cb472aa3a3abf64e668b506b44970cc03bd88720fc6c8b8195279501e5"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.captureOCR (cognitive 36): ScreenCaptureViewModel.captureOCR has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (27 pts), ternaries 3 (6 pts), boolean chains 2, error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2366}}}],"partialFingerprints":{"codehealthFindingId/v1":"86d4f27d96f2ae72665bece438601edc7077ff1a0acc7fad86c71fb11ab8d70b"}},{"ruleId":"D2","level":"warning","message":{"text":"CaptureSettingsView.body (cognitive 34): CaptureSettingsView.body has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (33 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":117}}}],"partialFingerprints":{"codehealthFindingId/v1":"fef8d3f3180117e305c540d69d1fdb69f5075b97bdcf2f85c081d61e98e18daa"}},{"ruleId":"D2","level":"warning","message":{"text":"ShortcutsSettingsView.body (cognitive 33): ShortcutsSettingsView.body has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 7 (20 pts), if/else 10 (13 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":124}}}],"partialFingerprints":{"codehealthFindingId/v1":"c560950117394a31203153209ff29d74aad4beae1ab229377914e43902867eef"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateQuickPropertiesBar.activePropertiesContent (cognitive 32): AnnotateQuickPropertiesBar.activePropertiesContent has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 29, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"a7a3dafc93da830098fba12fdae6f7b05dba10f1b0268c46d8a36f76dff3139d"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.updateAnnotationProperties (cognitive 31): AnnotateState.updateAnnotationProperties has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3679}}}],"partialFingerprints":{"codehealthFindingId/v1":"ecef876df392d493fa1bafb0df95baf07b39e454f66ec33291786e21e27e2d99"}},{"ruleId":"D2","level":"warning","message":{"text":"PostCaptureActionHandler.executeActions (cognitive 31): PostCaptureActionHandler.executeActions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 7 (9 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/PostCaptureActionHandler.swift"},"region":{"startLine":281}}}],"partialFingerprints":{"codehealthFindingId/v1":"22f15f714c3d9ef31a6c5c32f0aff8df341410d7f6b9d622038308b8fc4d4771"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureAccuracyBenchmark.run (cognitive 31): ScrollingCaptureAccuracyBenchmark.run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 12, loops 1, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift"},"region":{"startLine":165}}}],"partialFingerprints":{"codehealthFindingId/v1":"8199fc777519c48dedd7feaaad033477de5dbe3778110527423c82e96e85d2d0"}},{"ruleId":"D2","level":"warning","message":{"text":"SandboxOffDataMigrationService.mergeDirectoryIfPresent (cognitive 30): SandboxOffDataMigrationService.mergeDirectoryIfPresent has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (24 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Migration/SandboxOffDataMigrationService.swift"},"region":{"startLine":277}}}],"partialFingerprints":{"codehealthFindingId/v1":"8c29d09e69b0b25d4d6d84a1f25921c4726b6eb1e88fbbb2f36240ef0dc0b166"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateBottomBarView.handleCloudUpload (cognitive 30): AnnotateBottomBarView.handleCloudUpload has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 4, error handling 2 (4 pts), ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"158bfa4f36c6e5fdfc70361878506bd2880b90b9636571bd08ba4b0a298ec8d7"}},{"ruleId":"D2","level":"warning","message":{"text":"InlineAreaAnnotateRootView.body (cognitive 29): InlineAreaAnnotateRootView.body has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 5, match/switch 1, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":234}}}],"partialFingerprints":{"codehealthFindingId/v1":"8b73f06c31479e16cefc9c7cc459e8f0897a8422fde9c3e6715137e30ff29612"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.applyGestureResize (cognitive 28): DrawingCanvasNSView.applyGestureResize has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (9 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1229}}}],"partialFingerprints":{"codehealthFindingId/v1":"44dc6617cb2817960dffade9e93f89427a93507315ffb3a58b041f10c5fdc7fb"}},{"ruleId":"D2","level":"warning","message":{"text":"QuickAccessCardView.body (cognitive 28): QuickAccessCardView.body has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 11, ternaries 3 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"7e2cccd5d78d317e796d27dec02599768177a8596cfec5ac331baa273a534bc4"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.makeSpeedPreviewItem (cognitive 27): VideoEditorState.makeSpeedPreviewItem has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 3 (4 pts), ternaries 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1484}}}],"partialFingerprints":{"codehealthFindingId/v1":"29d57d1ea6663c3ac40f6e7e364c6898d0e3f437376b19928c49610bcf292e13"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionController.startSelectionSession (cognitive 27): AreaSelectionController.startSelectionSession has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, ternaries 2, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"1ae2657e39b784aa6167a2ec7b89ce65040b4fcc314f9161568d974c0ce9ef37"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionOverlayView.handlePrimaryMouseUp (cognitive 27): AreaSelectionOverlayView.handlePrimaryMouseUp has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (22 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":4690}}}],"partialFingerprints":{"codehealthFindingId/v1":"cd4d6791041056bdf250768de6d4cbe167263dd7d299f4d049d3aa94fbb941ad"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.prepareLazyFrozenDisplay (cognitive 26): ScreenCaptureViewModel.prepareLazyFrozenDisplay has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 1 (3 pts), boolean chains 2, error handling 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1741}}}],"partialFingerprints":{"codehealthFindingId/v1":"8e5b8b66aa39888f02231b04638efe96314726eaca868f751d40b6d544152fae"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionController.runSessionPresentationCheck (cognitive 26): AreaSelectionController.runSessionPresentationCheck has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 5, match/switch 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":836}}}],"partialFingerprints":{"codehealthFindingId/v1":"01d8d9893564c714d5975dc59040a82a00313ea2d3ebb7851f6d3caa39028e6f"}},{"ruleId":"D2","level":"warning","message":{"text":"WindowSelectionQueryService.captureImmediateMenuBarPopoverCaptures (cognitive 26): WindowSelectionQueryService.captureImmediateMenuBarPopoverCaptures has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":176}}}],"partialFingerprints":{"codehealthFindingId/v1":"a385ca52bd8a25e23e507722dcdf1b6eef37321b2447384f34173c9e5fd22a0f"}},{"ruleId":"D2","level":"warning","message":{"text":"S3MultipartUploader.upload (cognitive 26): S3MultipartUploader.upload has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (6 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3MultipartUploader.swift"},"region":{"startLine":47}}}],"partialFingerprints":{"codehealthFindingId/v1":"cf7aa21f8968fd1cb4e84847bbdf6dd7f026c3e71f19e2a189a94a3cc8c9bee3"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.resizeHandleRects (cognitive 26): DrawingCanvasNSView.resizeHandleRects has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (18 pts), if/else 3 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction \u2014 a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":671}}}],"partialFingerprints":{"codehealthFindingId/v1":"a9685ed299e840a603cac1dc7df093a250924ed2cc0485d328b1d0440e3f27c2"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureStitcher.isAcceptable (cognitive 26): ScrollingCaptureStitcher.isAcceptable has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8, ternaries 3 (4 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1397}}}],"partialFingerprints":{"codehealthFindingId/v1":"9146826d3f81be5698f5c937c74c3d4c3bb044a40afe5d98907d341b1f4f58d1"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureManager.captureAllDisplays (cognitive 25): ScreenCaptureManager.captureAllDisplays has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 4 (8 pts), loops 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":673}}}],"partialFingerprints":{"codehealthFindingId/v1":"d6274af5a8389519da2b006183343e5da01f3747295a26b436edb24af23c292d"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenRecordingManager.prepareRecording (cognitive 25): ScreenRecordingManager.prepareRecording has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 5 (6 pts), boolean chains 1, loops 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":790}}}],"partialFingerprints":{"codehealthFindingId/v1":"3dab430046b5c3a50889684b499c098ead7aa1b1542ad53f1a326e7af8f47c1a"}},{"ruleId":"D2","level":"warning","message":{"text":"KeyboardShortcutManager.saveShortcuts (cognitive 25): KeyboardShortcutManager.saveShortcuts has cognitive complexity 25 (threshold 15). Drivers by points: if/else 25. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1127}}}],"partialFingerprints":{"codehealthFindingId/v1":"60695049f217e6121563c1fa0271f918a093c75df81c0e61f3bb38e19ffb76ea"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.mouseDown (cognitive 25): DrawingCanvasNSView.mouseDown has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 6, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":817}}}],"partialFingerprints":{"codehealthFindingId/v1":"265a315d9032334aeaa02a36be138059b90a561fd50129b8fbaed7fde86da5dc"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateWindow.sendEvent (cognitive 25): AnnotateWindow.sendEvent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 2, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction \u2014 a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":364}}}],"partialFingerprints":{"codehealthFindingId/v1":"790c5599fd0454ea0dbd7cad5b28a3e9f8cc7a5c10533915fe7c10ebe3bcae18"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateExporter.renderFlatFinalImage (cognitive 25): AnnotateExporter.renderFlatFinalImage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 6, loops 1, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":403}}}],"partialFingerprints":{"codehealthFindingId/v1":"776c470bd6b0cecd4af3764723655ee51fec9a7c4d66df840e884495fa294cd9"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.applySharedParameterDefaults (cognitive 24): AnnotateState.applySharedParameterDefaults has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 9 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":4586}}}],"partialFingerprints":{"codehealthFindingId/v1":"89145b6edf06379b6f899baebb37c7ee2b2f2c2ac03e5122b40178ef86b01158"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingAudioLevelMeter.rms (cognitive 24): RecordingAudioLevelMeter.rms has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 4 (10 pts), boolean chains 4 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/RecordingAudioLevelMeter.swift"},"region":{"startLine":120}}}],"partialFingerprints":{"codehealthFindingId/v1":"5587e291b35f30141d59fbacd4a0ed34c6a2fa1ce03ec4a26448568a828540b5"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorCameraCPUProbe.main (cognitive 24): VideoEditorCameraCPUProbe.main has cognitive complexity 24 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (9 pts), ternaries 4, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/video-editor-performance/camera-cpu-probe.swift"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"377417ff76c70cb919633bfe283e679bc34f092334119fa4b8150a25d35397c0"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.waitForSettledAutoScrollFrame (cognitive 24): ScrollingCaptureCoordinator.waitForSettledAutoScrollFrame has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 5, loops 2, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":509}}}],"partialFingerprints":{"codehealthFindingId/v1":"510f6c21657fd7a4dccf1f16bd212462c1ec134c4c99cb17439835463ecd9233"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.refreshFrozenDisplaysAfterTransition (cognitive 23): ScreenCaptureViewModel.refreshFrozenDisplaysAfterTransition has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 5, error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1884}}}],"partialFingerprints":{"codehealthFindingId/v1":"0744297c8656a2489dc2934100825b2a0327eb1735d44d6dd52928c8093cfe2b"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingSession.appendMicrophoneSample (cognitive 23): RecordingSession.appendMicrophoneSample has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":319}}}],"partialFingerprints":{"codehealthFindingId/v1":"b34b1958772e60759b80967bf92e723424700fec0391ed9e4f406ff53c36a899"}},{"ruleId":"D2","level":"warning","message":{"text":"GoogleDriveCloudProvider.performResumableUpload (cognitive 23): GoogleDriveCloudProvider.performResumableUpload has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 5, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift"},"region":{"startLine":333}}}],"partialFingerprints":{"codehealthFindingId/v1":"95f2844ed5be0f12143b365b4633394948808d51dc0dbb4a374262daee57bf21"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateCanvasView.body (cognitive 23): AnnotateCanvasView.body has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12, boolean chains 11. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":88}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d9dcc5fbec27db0eb87e17068347df98b35398c46cc07124035f9f488acc63e"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotationFactory.createAnnotation (cognitive 23): AnnotationFactory.createAnnotation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (4 pts), match/switch 2, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"99d3f01536ff54ceb1ad44867fc2fb106e7980d46810bacb4bd9ead22b40629f"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotationRenderer.drawCurrentStroke (cognitive 23): AnnotationRenderer.drawCurrentStroke has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction \u2014 a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":128}}}],"partialFingerprints":{"codehealthFindingId/v1":"cc40cf85b86ce993387e8df2122ed8f9d3d9a688b6f093eb2cd069682872638a"}},{"ruleId":"D2","level":"warning","message":{"text":"LiquidGlassSurface.body (cognitive 23): LiquidGlassSurface.body has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 7, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift"},"region":{"startLine":86}}}],"partialFingerprints":{"codehealthFindingId/v1":"73b0cacc2fcb75c68abb41db1a4dcb65d7a09bcebed34fff1158affcfc3fda0e"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingSession.appendAudioSample (cognitive 22): RecordingSession.appendAudioSample has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":275}}}],"partialFingerprints":{"codehealthFindingId/v1":"c6b73326cebcaa3fe88c7e680761a4060ed9931d3478c0052d53c2237aef1979"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionMagnifier.update (cognitive 22): AreaSelectionMagnifier.update has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 8, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":340}}}],"partialFingerprints":{"codehealthFindingId/v1":"7afe11740c9f6909cb1b9837e72e8203f9b6108ba37c92c2e1e8ea95764d6949"}},{"ruleId":"D2","level":"warning","message":{"text":"SnapzyConfigurationImporter.collectQuickAccess (cognitive 22): SnapzyConfigurationImporter.collectQuickAccess has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":344}}}],"partialFingerprints":{"codehealthFindingId/v1":"ef30472458c232f251f1673fdb2e5d0de6860f10332e5f7377b58a8b8c8b431f"}},{"ruleId":"D2","level":"warning","message":{"text":"KeyboardShortcutManager.unregisterAllShortcuts (cognitive 22): KeyboardShortcutManager.unregisterAllShortcuts has cognitive complexity 22 (threshold 15). Drivers by points: if/else 22. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1808}}}],"partialFingerprints":{"codehealthFindingId/v1":"bcb1fca223ad74887ff1d1b6bfb3bf9e83cd71c84b15b495bf4c5185cfbe30ff"}},{"ruleId":"D2","level":"warning","message":{"text":"HistoryFloatingPanel.performKeyEquivalent (cognitive 22): HistoryFloatingPanel.performKeyEquivalent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanel.swift"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"8cf9cdcf61c2188c5aa792d5b0b3084827a3e2c8b0d0fb2d84ecf650fba9af96"}},{"ruleId":"D2","level":"warning","message":{"text":"LiquidGlassSegmentedControl.body (cognitive 22): LiquidGlassSegmentedControl.body has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 17 (18 pts), boolean chains 3, if/else 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSegmentedControl.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"eaebb61cf7e014264146261bdd7ab2b9e9a35872af32ef248d012ea18110d8c9"}},{"ruleId":"D2","level":"warning","message":{"text":"AppDelegate.presentDatabaseRecoveryFlow (cognitive 21): AppDelegate.presentDatabaseRecoveryFlow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 2 (8 pts), error handling 2 (6 pts), match/switch 2 (6 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/SnapzyApp.swift"},"region":{"startLine":277}}}],"partialFingerprints":{"codehealthFindingId/v1":"499256f28a3641afbf37e891f8f86fa286e600fc66e8b8516dfeeb4e74b515b0"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.updateDefaultAnnotationProperties (cognitive 21): AnnotateState.updateDefaultAnnotationProperties has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":4654}}}],"partialFingerprints":{"codehealthFindingId/v1":"f71bc4c4a4f6b8ba86aaad60466d8346a93b297fcc968943a184c2173bbe3d76"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.startAreaCapture (cognitive 21): ScreenCaptureViewModel.startAreaCapture has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 4, error handling 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":657}}}],"partialFingerprints":{"codehealthFindingId/v1":"7b1e96a03088b31b518ea73a79d362b043f9b3601730160bbdafc0c1de9cf1b1"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.play (cognitive 21): VideoEditorState.play has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1231}}}],"partialFingerprints":{"codehealthFindingId/v1":"7c4dbf109ecce1017f371dbd943678cd3928a99a5122fd4bd97600e40332c270"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.scheduleSpeedPreviewRebuild (cognitive 21): VideoEditorState.scheduleSpeedPreviewRebuild has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1401}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec18e7debb992eb2de7230d803cf6b188b275a3880588e63e8481693bec248e2"}},{"ruleId":"D2","level":"warning","message":{"text":"FrozenAreaCaptureSession.cropCompositeImage (cognitive 21): FrozenAreaCaptureSession.cropCompositeImage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":228}}}],"partialFingerprints":{"codehealthFindingId/v1":"507d6cf7c0c8799cee2692c2b520832c48f516c524ede8eeb9216e8010e6a8b6"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenRecordingManager.makeContentFilter (cognitive 21): ScreenRecordingManager.makeContentFilter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1957}}}],"partialFingerprints":{"codehealthFindingId/v1":"b8593768b45dd3715bf62e52a9581f553f93f30e3007e509f0aba3652c57e0af"}},{"ruleId":"D2","level":"warning","message":{"text":"SimpleTOMLParser.splitArray (cognitive 21): SimpleTOMLParser.splitArray has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SimpleTOMLParser.swift"},"region":{"startLine":135}}}],"partialFingerprints":{"codehealthFindingId/v1":"4483d80b18772fc680aec5777ab170c875e91e44f01c6897fbe24e723e55cb91"}},{"ruleId":"D2","level":"warning","message":{"text":"CaptureHistoryRetentionService.collectTempFilePathsForRecordsToDelete (cognitive 21): CaptureHistoryRetentionService.collectTempFilePathsForRecordsToDelete has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryRetentionService.swift"},"region":{"startLine":116}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d6dc9dc27ee0c3aab3d8206e48f94fa5ffcf6fc4cd501855dd8a2616e2fd6fe"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateSensitiveRedactionService.extractRegions (cognitive 21): AnnotateSensitiveRedactionService.extractRegions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateSensitiveRedactionService.swift"},"region":{"startLine":354}}}],"partialFingerprints":{"codehealthFindingId/v1":"745f9fc986dfe83a7b3c0ac8bb2983ce285596ed2ecfa88c123aadef07bf6292"}},{"ruleId":"D2","level":"warning","message":{"text":"CloudCredentialFormView.saveAndTest (cognitive 21): CloudCredentialFormView.saveAndTest has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10, error handling 3 (7 pts), if/else 2 (4 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":1272}}}],"partialFingerprints":{"codehealthFindingId/v1":"b98ac331c85d19ab7379388138a430abbb2ca80375e17748e7205173a9d9d18f"}},{"ruleId":"D2","level":"warning","message":{"text":"QuickAccessDragMonitorView.continueTracking (cognitive 21): QuickAccessDragMonitorView.continueTracking has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessDraggableView.swift"},"region":{"startLine":329}}}],"partialFingerprints":{"codehealthFindingId/v1":"9b6e1a4317d5ade1e4258140ed93ac2b851911ade17e93024ee4203e56f6747d"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureStitcher.priorPenalty (cognitive 21): ScrollingCaptureStitcher.priorPenalty has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, ternaries 2 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1293}}}],"partialFingerprints":{"codehealthFindingId/v1":"23a5a927812feec4b43a07b554746f489a66bb208639f4728dce9e5536865fdc"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.autoCropToContent (cognitive 20): AnnotateState.autoCropToContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3120}}}],"partialFingerprints":{"codehealthFindingId/v1":"2aa9288c49e362fdb9ec4d5c579c94082d85c3948a6db727873f2822f75672f5"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.annotationPropertiesWillChange (cognitive 20): AnnotateState.annotationPropertiesWillChange has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 10. 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3838}}}],"partialFingerprints":{"codehealthFindingId/v1":"df114c43e6ca3d81168dea8a7b753c8031d200cb60384384aac2effaff4e8552"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.restoreSessionIfNeeded (cognitive 20): VideoEditorState.restoreSessionIfNeeded has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (10 pts) (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1091}}}],"partialFingerprints":{"codehealthFindingId/v1":"f6cf62b910b2ac35b69aee1d001400f7b37813dbeb65efece58b6c73cbef3cbb"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionOverlayView.renderManualSelection (cognitive 20): AreaSelectionOverlayView.renderManualSelection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":4215}}}],"partialFingerprints":{"codehealthFindingId/v1":"169349e8a5910b1db6bf4722160514c7fdae463c30ad8a4b385f39ec5fa604c5"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenRecordingManager.stopRecording (cognitive 20): ScreenRecordingManager.stopRecording has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (6 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1255}}}],"partialFingerprints":{"codehealthFindingId/v1":"c4ee0c6b087921bf15d4815ca98791592f83241082cee6b46ab2369784292590"}},{"ruleId":"D2","level":"warning","message":{"text":"WindowSelectionQueryService.captureImmediateQuickLookCaptures (cognitive 20): WindowSelectionQueryService.captureImmediateQuickLookCaptures has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":266}}}],"partialFingerprints":{"codehealthFindingId/v1":"9c678ef57f86a98d70b3b75109773a553282d6233c306eb01f3af879f81854bb"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateBottomBarView.annotateActionButtons (cognitive 20): AnnotateBottomBarView.annotateActionButtons has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 5, if/else 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"005bff536117fd26e550d8ce8af07282c0d060bf14dba6aad8039a57091ec97b"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateWindowController.performCloudReUploadCopyAndClose (cognitive 20): AnnotateWindowController.performCloudReUploadCopyAndClose has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":1335}}}],"partialFingerprints":{"codehealthFindingId/v1":"0b3c3f87e84312331ea4d68608c8e8503e7c6982581060dd2472376a2066e28c"}},{"ruleId":"D2","level":"warning","message":{"text":"CloudSettingsView.configuredView (cognitive 20): CloudSettingsView.configuredView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":172}}}],"partialFingerprints":{"codehealthFindingId/v1":"a0dee02367ebe9d4860257a6a621524623355cd548aa36fa923b3a38d7bc5fb4"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorSessionStore.persistWrite (cognitive 20): VideoEditorSessionStore.persistWrite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift"},"region":{"startLine":329}}}],"partialFingerprints":{"codehealthFindingId/v1":"6bf6df26d4517e15c487038dbb14f9d7f344713ff596229f129f13326db029a4"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureAutoScrollController.handleCommitResult (cognitive 20): ScrollingCaptureAutoScrollController.handleCommitResult has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureAutoScrollController.swift"},"region":{"startLine":233}}}],"partialFingerprints":{"codehealthFindingId/v1":"fd75b505a0d8b4d4977acb51089ec9b671b64ef1c73f0c4c1782e24f367f882e"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.startLiveRefreshLoopIfNeeded (cognitive 20): ScrollingCaptureCoordinator.startLiveRefreshLoopIfNeeded has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":1358}}}],"partialFingerprints":{"codehealthFindingId/v1":"d484bec5aa90f1b12c72732c1307e7c9dafb5a2948fe03c6c170dc3b9742ea96"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateTextSnapping.resolve (cognitive 19): AnnotateTextSnapping.resolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (6 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateTextSnapping.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"7e450832ea1681c4753d551e8f71b582c1c5f249a8d4eef54b6b65a1e5811489"}},{"ruleId":"D2","level":"warning","message":{"text":"CombineSnapping.resolve (cognitive 19): CombineSnapping.resolve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/CombineSnapping.swift"},"region":{"startLine":5}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a4039baec703ea5ac9c6131e3565854b341c7da6ecf52a5233a233f3eab706a"}},{"ruleId":"D2","level":"warning","message":{"text":"TempCaptureManager.cleanupOrphanedFiles (cognitive 19): TempCaptureManager.cleanupOrphanedFiles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, error handling 1 (2 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/TempCaptureManager.swift"},"region":{"startLine":272}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2c11fca12de3d3ac0f53ece4a6f8da981a5e49501381cff1250381684b00adb"}},{"ruleId":"D2","level":"warning","message":{"text":"ClipboardHelper.writeSingleImageItem (cognitive 19): ClipboardHelper.writeSingleImageItem has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, ternaries 2 (4 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Clipboard/ClipboardHelper.swift"},"region":{"startLine":270}}}],"partialFingerprints":{"codehealthFindingId/v1":"bd048f141afd33997db838194aa11a5ad5d6fda500bb27b217fc98359d7bc128"}},{"ruleId":"D2","level":"warning","message":{"text":"MockupExportViewForAnnotate.backgroundLayer (cognitive 19): MockupExportViewForAnnotate.backgroundLayer has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (7 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction \u2014 a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":1203}}}],"partialFingerprints":{"codehealthFindingId/v1":"aa5af0d78fc5ac84477cae3a33dee90a0a02ac6c82f98e7cd07a655fa724a097"}},{"ruleId":"D2","level":"warning","message":{"text":"ShortcutsView.body (cognitive 19): ShortcutsView.body has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (15 pts), if/else 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingShortcutsView.swift"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"476d9e2bd9a9c416b0400e5b328d03b82e3c8c18387c95a2d36c98d5efc8413e"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorBottomBar.body (cognitive 19): VideoEditorBottomBar.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 4 (7 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"77eef75410b16da568c4d08397624abcfd3ebe286940132d0a8947e4d93e3274"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorClipStripView.bodyGesture (cognitive 19): VideoEditorClipStripView.bodyGesture has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorClipStripView.swift"},"region":{"startLine":405}}}],"partialFingerprints":{"codehealthFindingId/v1":"3dd2d8882071ee31da467f17076bd5c30973cdf6cfa7ad1dfb27892b48bd235d"}},{"ruleId":"D2","level":"warning","message":{"text":"SpeedTimelineTrack.interactionSegment (cognitive 19): SpeedTimelineTrack.interactionSegment has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":527}}}],"partialFingerprints":{"codehealthFindingId/v1":"8b1629d7152f4c3cc027b2e2c43208c760b26587d7e36a9eb675d7a476ff706f"}},{"ruleId":"D2","level":"warning","message":{"text":"ZoomTimelineTrack.interactionSegment (cognitive 19): ZoomTimelineTrack.interactionSegment has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift"},"region":{"startLine":498}}}],"partialFingerprints":{"codehealthFindingId/v1":"00f4af4828579891d03fbb06a40c946f10c8c5c9a9a724afa61fdca22a790325"}},{"ruleId":"D2","level":"warning","message":{"text":"HistoryWindow.performKeyEquivalent (cognitive 18): HistoryWindow.performKeyEquivalent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5 (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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/HistoryWindowController.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"e9b5c67aea11f4955d848355528d7a53c2506abaa3e047e226d1a1f3c456476e"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.recalculateEstimatedFileSize (cognitive 18): VideoEditorState.recalculateEstimatedFileSize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":2890}}}],"partialFingerprints":{"codehealthFindingId/v1":"9e8e5351efe115649db2d12f4280647651bf2af6c52c847608db5b3b63a7f57d"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureManager.scanTransparentFringeBounds (cognitive 18): ScreenCaptureManager.scanTransparentFringeBounds has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), loops 6 (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":2294}}}],"partialFingerprints":{"codehealthFindingId/v1":"05acd3b59da78bbfa995d434e267482a844baf84eb59c93129ae71cdd0533d38"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenRecordingManager.logRecordingFrameDiagnostics (cognitive 18): ScreenRecordingManager.logRecordingFrameDiagnostics has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":2116}}}],"partialFingerprints":{"codehealthFindingId/v1":"bb3a1ac088e02ebe989c8714ec3d411afb61a2fb97f3b9b129627961634bf0c2"}},{"ruleId":"D2","level":"warning","message":{"text":"CaptureHistoryStore.remove (cognitive 18): CaptureHistoryStore.remove has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (4 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryStore.swift"},"region":{"startLine":142}}}],"partialFingerprints":{"codehealthFindingId/v1":"ce7b6d367a9c4c865e8d1667cc85f19a3a71178ded12c373bcaef15b721aa7e9"}},{"ruleId":"D2","level":"warning","message":{"text":"DrawingCanvasNSView.updateCursor (cognitive 18): DrawingCanvasNSView.updateCursor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2116}}}],"partialFingerprints":{"codehealthFindingId/v1":"bdc1eba38f4d326dc530b0e51aa5d89447db20b99fcff16c42f33921ee5dcca8"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateCanvasView.canvasContent (cognitive 18): AnnotateCanvasView.canvasContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 4, boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":224}}}],"partialFingerprints":{"codehealthFindingId/v1":"4ea008fda2cadb5771455bde5030e8bf259da5fe8a94b984a3f24ce7c0099a0a"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateWindowController.performCloudReUploadAndClose (cognitive 18): AnnotateWindowController.performCloudReUploadAndClose has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":1241}}}],"partialFingerprints":{"codehealthFindingId/v1":"740e8e6a906166ed506080df6eacce1c0af19fa42fa13826c08beabb7b0f5fd8"}},{"ruleId":"D2","level":"warning","message":{"text":"QuickAccessPinWindow.updateMousePassthrough (cognitive 18): QuickAccessPinWindow.updateMousePassthrough has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3 (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth \u2014 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\u0027s 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Managers/QuickAccessPinWindow.swift"},"region":{"startLine":188}}}],"partialFingerprints":{"codehealthFindingId/v1":"de2a91157520cbc2b806a0ddab34d66d014ed57734afc7344363fe357ce31aba"}},{"ruleId":"D2","level":"warning","message":{"text":"ThumbnailGenerator.generateFromImage (cognitive 18): ThumbnailGenerator.generateFromImage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Services/QuickAccessThumbnailGenerator.swift"},"region":{"startLine":93}}}],"partialFingerprints":{"codehealthFindingId/v1":"b60e50108bb0d01697c967828bf3d6697650776c9a9bfabc9fc86b01c1dc5935"}},{"ruleId":"D2","level":"warning","message":{"text":"VerticalCJKTextNormalizer.rowBands (cognitive 18): VerticalCJKTextNormalizer.rowBands has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCR/VerticalCJKTextNormalizer.swift"},"region":{"startLine":57}}}],"partialFingerprints":{"codehealthFindingId/v1":"3cc258405284c8dd1032ecf99dd709de9154ae617c2ae2c5a822bf2c83fc8c4e"}},{"ruleId":"D2","level":"warning","message":{"text":"LiquidGlassBarSegment.body (cognitive 18): LiquidGlassBarSegment.body has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (6 pts), if/else 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassActionBar.swift"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb64ed133c96ea7b5e2994beb0de5a1d89fea9e6c6f709f808a1a61b3e1c40f8"}},{"ruleId":"D2","level":"warning","message":{"text":"LiquidGlassButtonSurface.currentSubstrate (cognitive 18): LiquidGlassButtonSurface.currentSubstrate has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 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. This shape REPEATS in the file: one other method here (LiquidGlassButtonSurface.currentTint) has the same decision points, in the same order, at the same nesting depths \u2014 so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift"},"region":{"startLine":99}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d4629d31a17810997ab07fd4f755d10074e746f46df66c497871f96667d3b1a"}},{"ruleId":"D2","level":"warning","message":{"text":"LiquidGlassButtonSurface.currentTint (cognitive 18): LiquidGlassButtonSurface.currentTint has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 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. This shape REPEATS in the file: one other method here (LiquidGlassButtonSurface.currentSubstrate) has the same decision points, in the same order, at the same nesting depths \u2014 so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift"},"region":{"startLine":114}}}],"partialFingerprints":{"codehealthFindingId/v1":"d9683af7c900910f4cc0ad0ffc2cfce6c4856bc5b7c01afb20be23cfd462e56a"}},{"ruleId":"D2","level":"warning","message":{"text":"AppDelegate.ensureSandboxOffDataMigrationReadyForLaunch (cognitive 17): AppDelegate.ensureSandboxOffDataMigrationReadyForLaunch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), error handling 2 (6 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/SnapzyApp.swift"},"region":{"startLine":158}}}],"partialFingerprints":{"codehealthFindingId/v1":"7f5524e3724ef563d9a9213fdff5428f9c965a97e302f2fd74d8575f5127609f"}},{"ruleId":"D2","level":"warning","message":{"text":"AnnotateState.setTextPresentation (cognitive 17): AnnotateState.setTextPresentation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":5034}}}],"partialFingerprints":{"codehealthFindingId/v1":"003631b1d9eea9218ceff2f29db3337379c8d6a65bce89b8aca7aeed066ad113"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingSession.logAudioSampleFormatIfNeeded (cognitive 17): RecordingSession.logAudioSampleFormatIfNeeded has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, match/switch 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":451}}}],"partialFingerprints":{"codehealthFindingId/v1":"101253f6767d0a3e836b9196c38df5a5afa8c1fdd3e93df92e73bf2feb67e7ff"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionController.scheduleRetainedMenuBarPopoverVisibilityRefresh (cognitive 17): AreaSelectionController.scheduleRetainedMenuBarPopoverVisibilityRefresh has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, loops 2 (3 pts), error handling 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":992}}}],"partialFingerprints":{"codehealthFindingId/v1":"4a00f99ce77794b0c5413ddf0031f6cef5efa9a3fa9ae896b5525c5f68b3ee3b"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionController.handleLivePassthroughButton (cognitive 17): AreaSelectionController.handleLivePassthroughButton has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":1894}}}],"partialFingerprints":{"codehealthFindingId/v1":"2af83496a8770e96a30da24a098909629531abcaa254227f0221a03676e64447"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureManager.captureDisplaySnapshotsCore (cognitive 17): ScreenCaptureManager.captureDisplaySnapshotsCore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":430}}}],"partialFingerprints":{"codehealthFindingId/v1":"8d4b3c6e645b36f457fa3b36fddd592f532476ca6cbfdf071c281d0c6bfad098"}},{"ruleId":"D2","level":"warning","message":{"text":"ArrowGeometry.taperedArrowPath (cognitive 17): ArrowGeometry.taperedArrowPath has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 5, boolean chains 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":680}}}],"partialFingerprints":{"codehealthFindingId/v1":"971a483495168ed5758f4f975e4064ad619ef3e72ac7ed6f019ae50ef1f098ce"}},{"ruleId":"D2","level":"warning","message":{"text":"BlurEffectRenderer.drawCIFilterRegion (cognitive 17): BlurEffectRenderer.drawCIFilterRegion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 1. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":415}}}],"partialFingerprints":{"codehealthFindingId/v1":"39ca8197ba38261ae1655ed03d027cdfc84d276e2eb2d8b29343f478b793aa40"}},{"ruleId":"D2","level":"warning","message":{"text":"SnapzyOnboardingBarSegment.body (cognitive 17): SnapzyOnboardingBarSegment.body has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 4, ternaries 3 (4 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyOnboardingActionBar.swift"},"region":{"startLine":96}}}],"partialFingerprints":{"codehealthFindingId/v1":"f9287efedc426548e157b9315b0924e66d5176b158eaad301278ee893db36cda"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureCoordinator.finish (cognitive 17): ScrollingCaptureCoordinator.finish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":600}}}],"partialFingerprints":{"codehealthFindingId/v1":"af8962cb609a3a29903b2ac5cbf5894a5e37f2372abd23732023914d49a9ff2b"}},{"ruleId":"D2","level":"warning","message":{"text":"InlineAreaControlGeometry.splitControlSides (cognitive 16): InlineAreaControlGeometry.splitControlSides has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":1402}}}],"partialFingerprints":{"codehealthFindingId/v1":"757e85f60498f5c2deebdf6768576c915a52a3144ca7d15bcf0af77086e8348c"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.prepareInlineAreaAnnotateFrozenSession (cognitive 16): ScreenCaptureViewModel.prepareInlineAreaAnnotateFrozenSession has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":974}}}],"partialFingerprints":{"codehealthFindingId/v1":"d8a0599e66c35b44616473cb70e2584bdb6310848050d8130b5d238cf80759ba"}},{"ruleId":"D2","level":"warning","message":{"text":"ScreenCaptureViewModel.captureObjectCutout (cognitive 16): ScreenCaptureViewModel.captureObjectCutout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 2 (3 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2696}}}],"partialFingerprints":{"codehealthFindingId/v1":"10c5773f3ad9b8750d2481cc611fab742744a2ae71a10fe27eadc609c2efa655"}},{"ruleId":"D2","level":"warning","message":{"text":"SplashWindowController.showWindow (cognitive 16): SplashWindowController.showWindow has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 3, ternaries 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Splash/SplashWindow.swift"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"ef63bd6a0870cda66312e4aa9f2074e94909fb065f90b9599560425ff26dddc7"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorState.seekPlayerInternally (cognitive 16): VideoEditorState.seekPlayerInternally has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1599}}}],"partialFingerprints":{"codehealthFindingId/v1":"5ca1929d2563e111603858275169a75036f11d3b1009ee319ea7b0cd66acee1c"}},{"ruleId":"D2","level":"warning","message":{"text":"AreaSelectionController.recaptureBackdropsForLuma (cognitive 16): AreaSelectionController.recaptureBackdropsForLuma has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, error handling 1, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":1341}}}],"partialFingerprints":{"codehealthFindingId/v1":"6e5fc8af4157dd9349dedbfd4cd99e12fbec08f9d9e45f636c75ec7e72f285af"}},{"ruleId":"D2","level":"warning","message":{"text":"PostCaptureActionHandler.handleScreenshotCaptures (cognitive 16): PostCaptureActionHandler.handleScreenshotCaptures has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/PostCaptureActionHandler.swift"},"region":{"startLine":63}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc0933218c82d0123e1c34456dca0dc38a5305a43808e40f04c14b0120e086ba"}},{"ruleId":"D2","level":"warning","message":{"text":"SnapzyConfigurationImporter.collectAnnotateTools (cognitive 16): SnapzyConfigurationImporter.collectAnnotateTools has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 5, 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":233}}}],"partialFingerprints":{"codehealthFindingId/v1":"610fcb437a1244c98bcf85c8d3310a3215e6968782b19f51aafa3659b92e67b7"}},{"ruleId":"D2","level":"warning","message":{"text":"BlurEffectRenderer.drawGaussianRegion (cognitive 16): BlurEffectRenderer.drawGaussianRegion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 5, ternaries 1. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":266}}}],"partialFingerprints":{"codehealthFindingId/v1":"6f45135c69762d4f809617d126c8cf3d1fb75ddbc7d6c52873a471f913f0ce86"}},{"ruleId":"D2","level":"warning","message":{"text":"CloudSettingsView.cloudStatsSection (cognitive 16): CloudSettingsView.cloudStatsSection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"9425cc93b378943378c3d247146c0ed75ee9081f2f794308013889fb4ddf3905"}},{"ruleId":"D2","level":"warning","message":{"text":"QuickAccessCardView.handleSwipeEnded (cognitive 16): QuickAccessCardView.handleSwipeEnded has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":293}}}],"partialFingerprints":{"codehealthFindingId/v1":"b3cc7bc1ce767975111ca88f1163b5b629499f15f0e6f64549934f50a00fb833"}},{"ruleId":"D2","level":"warning","message":{"text":"RecordingRegionOverlayView.drawGuidance (cognitive 16): RecordingRegionOverlayView.drawGuidance has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11, boolean chains 3, if/else 2. To reduce it, split the body: this score is breadth rather than depth \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":802}}}],"partialFingerprints":{"codehealthFindingId/v1":"2552c941dc21d9c439c54ade707fa1f7abfa42bf962e8ac5043ed01ddb16b2ad"}},{"ruleId":"D2","level":"warning","message":{"text":"VideoEditorExporter.addAudioTracks (cognitive 16): VideoEditorExporter.addAudioTracks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":732}}}],"partialFingerprints":{"codehealthFindingId/v1":"df8030f086d79d8a4667e7cce2050d8988a4a882aec860a557099d80a777616d"}},{"ruleId":"D2","level":"warning","message":{"text":"ScrollingCaptureStitcher.isAmbiguous (cognitive 16): ScrollingCaptureStitcher.isAmbiguous has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1443}}}],"partialFingerprints":{"codehealthFindingId/v1":"6286da10cdf095a4301c88eeb472f2c6522bfba87a22c0169ad627f40672f63b"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AnnotateState: ClassTooLong \u2014 3759 significant lines (blank, comment-only and punctuation-only lines excluded), 227 methods. The bar is 400 significant lines; this is 3359 over it, 9.40\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"9bef42ac580d65b3eb0317a5cfd5369dea2653b49c02075fb4d8145906944771"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Annotate/AnnotateState.swift: FileTooLong \u2014 3866 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: AnnotateState (16-5726). The bar is 500 significant lines; this is 3366 over it, 7.73\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1d6c288f023d3dd55cb520be6b16e08b57b5849dd42b710d3410073faa4b0322"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AnnotateState: TooManyMethods \u2014 227 methods. The bar is 30 methods; this is 197 over it, 7.57\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"bf1bae2a9ce47e675b75b2f62b0bbf4a73b954c433722e83877c5c2b56352cf7"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Capture/AreaSelectionWindow.swift: FileTooLong \u2014 2998 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2498 over it, 6.00\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"feb4bb566db3237f8e39176918dfa3fc7e44717f6fec0050b5c76c058b5272d6"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: ScreenCaptureViewModel: ClassTooLong \u2014 2033 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 1633 over it, 5.08\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f51df15295ec08f3020e8794955b4d13b49d0cf7fe054a100aa7be4eb346a0a"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: VideoEditorState: ClassTooLong \u2014 2028 significant lines (blank, comment-only and punctuation-only lines excluded), 126 methods. The bar is 400 significant lines; this is 1628 over it, 5.07\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":311}}}],"partialFingerprints":{"codehealthFindingId/v1":"544bf18ff6a4e3e3163673bdcbb5a388e5254635653fe1bf0c16196b720878b2"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ShortcutsSettingsView.body: MethodTooLong \u2014 body runs 507 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 407 over it, 5.07\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":124}}}],"partialFingerprints":{"codehealthFindingId/v1":"e742d469e3ab26e96749ebb970e8a7ac7924ac6a4611bc1e84b2200d31412200"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: ScreenCaptureManager: ClassTooLong \u2014 1831 significant lines (blank, comment-only and punctuation-only lines excluded), 66 methods. The bar is 400 significant lines; this is 1431 over it, 4.58\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec5e6bd41a262470ceeffb758e502bc7e32f96c780a24c4a6713fe7febde5621"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: CaptureSettingsView.body: MethodTooLong \u2014 body runs 455 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 355 over it, 4.55\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":117}}}],"partialFingerprints":{"codehealthFindingId/v1":"0adda7dae83d438ce8495270b963d5d6d00cf7c51efeddb28a7783cb6c6d4935"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: VideoEditor/VideoEditorState.swift: FileTooLong \u2014 2233 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: VideoEditorState (312-3466). The bar is 500 significant lines; this is 1733 over it, 4.47\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5268eb71e17576729769d127041ba9d928aaf9237ad2bd73b4446c6fe45d280b"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: VideoEditorState: TooManyMethods \u2014 126 methods. The bar is 30 methods; this is 96 over it, 4.20\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":311}}}],"partialFingerprints":{"codehealthFindingId/v1":"75025e6ebd8ca86289f0207553ecf027f7c96687d2c8e029b5ffbb56f1baab57"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Capture/CaptureViewModel.swift: FileTooLong \u2014 2051 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: ScreenCaptureViewModel (39-2979). The bar is 500 significant lines; this is 1551 over it, 4.10\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"886a2d882cb1d881d54c9fd73d18ddfc4066e4a7449cc8244dc72772418ad0b3"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Annotate/InlineAreaAnnotateWindow.swift: FileTooLong \u2014 2044 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1544 over it, 4.09\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c6a0d1b5c752f54d270433d14a035889e1b88d8159c41988c0b43ef95cd7b206"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: ScrollingCaptureCoordinator: ClassTooLong \u2014 1566 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 400 significant lines; this is 1166 over it, 3.92\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"b9a944e16d3a1433859cea84aa7d3e00cd1d551bd58edae00cf59b92884f0811"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Capture/ScreenCaptureManager.swift: FileTooLong \u2014 1904 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ScreenCaptureManager (95-2720). The bar is 500 significant lines; this is 1404 over it, 3.81\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"b1c37d7b2f977b5f2ffd7f45f525a2d8ce2ab1f28083627e94667513e82587b7"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: DrawingCanvasNSView: ClassTooLong \u2014 1508 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 1108 over it, 3.77\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":245}}}],"partialFingerprints":{"codehealthFindingId/v1":"5ce4ca65f5fb6f9836f569e08722d99fe502528815da6594ab33c8cfe7448f18"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AreaSelectionController: TooManyMethods \u2014 108 methods. The bar is 30 methods; this is 78 over it, 3.60\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"8471800fcb22ac8206e18c56f9e5d20a026f473810b65c6666190c8bad18ae9c"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AreaSelectionController: ClassTooLong \u2014 1390 significant lines (blank, comment-only and punctuation-only lines excluded), 108 methods. The bar is 400 significant lines; this is 990 over it, 3.48\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"32a7ec768985044468129fabd08470bc7a24dbd64029c83e0583f15aaa63b1d4"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/AnnotateCanvasDrawingView.swift: FileTooLong \u2014 1643 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: DrawingCanvasNSView (245-2540). The bar is 500 significant lines; this is 1143 over it, 3.29\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"404ac8df489e3483dc09087e1361f4cc7b4a97293e7ce4738d1c78beade45047"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AreaSelectionOverlayView: ClassTooLong \u2014 1286 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 400 significant lines; this is 886 over it, 3.22\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":2732}}}],"partialFingerprints":{"codehealthFindingId/v1":"a73718d0bb89930e248a7ecaa5076b4fb76b6e6db44ffc570fa66a171f2af11a"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: ScrollingCapture/ScrollingCaptureCoordinator.swift: FileTooLong \u2014 1604 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: ScrollingCaptureCoordinator (15-2105). The bar is 500 significant lines; this is 1104 over it, 3.21\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"3768e551d4c875b1ab31308879f406bac7880ac90ccea055c91c919200959c95"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Capture/ScreenRecordingManager.swift: FileTooLong \u2014 1581 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: ScreenRecordingManager (684-2257). The bar is 500 significant lines; this is 1081 over it, 3.16\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"178d46ff3ff3ae508d9846c598e7eb598e74d62e750fbc041fd8ad071712ff83"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AreaSelectionOverlayView: TooManyMethods \u2014 89 methods. The bar is 30 methods; this is 59 over it, 2.97\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":2732}}}],"partialFingerprints":{"codehealthFindingId/v1":"550783d4e3ba4c3c525b5139aa077363e7f3ee6d2c6c225e0f705399811bb624"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: CloudCredentialFormView.body: MethodTooLong \u2014 body runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":816}}}],"partialFingerprints":{"codehealthFindingId/v1":"df4e21b781014698a13c4e0d55dd506c4c3378c1ede8e93a9f7dc5f228da6883"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: DrawingCanvasNSView: TooManyMethods \u2014 83 methods. The bar is 30 methods; this is 53 over it, 2.77\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":245}}}],"partialFingerprints":{"codehealthFindingId/v1":"543c2661530a3824c195a0eecb39e404ae68c86cde1de2890762b4e16d6839c4"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: ScreenRecordingManager: ClassTooLong \u2014 1101 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 701 over it, 2.75\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":683}}}],"partialFingerprints":{"codehealthFindingId/v1":"7ec16c081c278f116ab54b252ab85b91c0c22cbc5573c1a7dae3e24c39ef7a73"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: ScrollingCaptureCoordinator: TooManyMethods \u2014 82 methods. The bar is 30 methods; this is 52 over it, 2.73\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"33b7384928ad02d93593aa07515337b6b3eace8fcf565700ee0a8b0e60b41949"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: LiquidGlass/LiquidGlassPreview.swift: FileTooLong \u2014 1358 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: LiquidGlassPlaygroundView (416-1981). The bar is 500 significant lines; this is 858 over it, 2.72\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"bd2aeb1a825fb0fceb15925a9616fe9eb1a91781a5206f39780994cb880c652f"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: LiquidGlassPlaygroundView: ClassTooLong \u2014 1085 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 685 over it, 2.71\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":416}}}],"partialFingerprints":{"codehealthFindingId/v1":"147aa42e378ea4b5429cfe9e2750b08e26727c0baf2697d297ac9fbe8461859c"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Shortcuts/KeyboardShortcutManager.swift: FileTooLong \u2014 1327 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: KeyboardShortcutManager (584-1899). The bar is 500 significant lines; this is 827 over it, 2.65\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"2e9560e87c25ea92ccb6f547e41ceecba1982d5f7313e79d9a946fdd43e245dc"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: QuickAccessManager: ClassTooLong \u2014 1058 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 658 over it, 2.65\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"9bab90a0f5ceb693acc512fbd15292180c378dc167a24b5f57d9032157a17e62"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: ScrollingCapture/ScrollingCaptureStitcher.swift: FileTooLong \u2014 1321 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 821 over it, 2.64\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"76e6e20253fbd92999f4a6a3902d2dfa1ce7f9404b767e529d06d3f8a5d2e229"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/AnnotateQuickPropertiesBar.swift: FileTooLong \u2014 1288 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 788 over it, 2.58\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"94e7593c9b01373620b80bd24e10133faf6b2f2cc7cb83f1c081b77d3d1f733f"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Models/AnnotateAnnotationItem.swift: FileTooLong \u2014 1216 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 716 over it, 2.43\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"cd4db8ef0dec2b0edc7fb5d10c33cf2ee9d2755c37ffcbb351300c4e4f7b656e"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AnnotateQuickPropertiesBar.activePropertiesContent: MethodTooLong \u2014 activePropertiesContent runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"55263481fb8cb1b4dce593e7149971aeb1b4ca90c432082e84102390f1dee32d"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: ShortcutsSettingsView: ClassTooLong \u2014 936 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 536 over it, 2.34\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae1e6d85e53fc5d510b65fb806dabddb2380d201fb905033d8d72cd319763086"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: RecordingCoordinator: ClassTooLong \u2014 932 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 532 over it, 2.33\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"e44c3ff847b7ea30d57fd64ad107ead27d33861ef8b491d666595ff7f3327d00"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScrollingCaptureCoordinator.refreshPreview: MethodTooLong \u2014 refreshPreview runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":761}}}],"partialFingerprints":{"codehealthFindingId/v1":"bb589546db04cda60d8628938cfd6ca7dd0efbd20c69d3e013cbe365998a654e"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenRecordingManager.prepareRecording: MethodTooLong \u2014 prepareRecording runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":790}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec02589078a6740f7c07884dff364922ada4a7d82e20ec73e6c44ee64ae99242"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AnnotateWindowController: ClassTooLong \u2014 887 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 487 over it, 2.22\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"b53d26cc2ff4ead521b4c524d7b6fdda4bee62903ddeccba257668d2e0e6d401"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: KeyboardShortcutManager: ClassTooLong \u2014 887 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 487 over it, 2.22\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":583}}}],"partialFingerprints":{"codehealthFindingId/v1":"42f0393520bf73734dd97a2c0b10b03699514b3d2b79ec6f38c7a7de70f26c7c"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: ScreenCaptureManager: TooManyMethods \u2014 66 methods. The bar is 30 methods; this is 36 over it, 2.20\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"6cfa8389b1bdaefcf0442523282a262f638a97df727e55ad0ce7a751437ea792"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AppStatusBarController: ClassTooLong \u2014 870 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 470 over it, 2.18\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/AppStatusBarController.swift"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"fa4d8bdbd72d90a51f8c087bc0d2e4dd9c75f5ca6063e0d425325f879a8a6249"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScrollingCaptureStitcher.append: MethodTooLong \u2014 append runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":372}}}],"partialFingerprints":{"codehealthFindingId/v1":"210d2deaeb228b0639b5f89d167134777f37e0e15cb644528988ab37ec58c910"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/PreferencesShortcutsSettingsView.swift: FileTooLong \u2014 1078 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: ShortcutsSettingsView (12-1229). The bar is 500 significant lines; this is 578 over it, 2.16\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"2b021054733742d2a9dd24fb4025c758d11fd112fa247908dd13f163379b88cf"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: QuickAccess/QuickAccessManager.swift: FileTooLong \u2014 1075 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: QuickAccessManager (35-1671). The bar is 500 significant lines; this is 575 over it, 2.15\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"86ce24099fcda9280665ef3817f1aaad57a73af634ee2127b871025981cd56c3"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: VideoEditorExporter.exportWithZooms: MethodTooLong \u2014 exportWithZooms runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":206}}}],"partialFingerprints":{"codehealthFindingId/v1":"36cb508c156050146bde8d63adcb487cf80f2763ec6909ba4647aad8136e9e72"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AppStatusBarController.makeMenuItem: MethodTooLong \u2014 makeMenuItem runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/AppStatusBarController.swift"},"region":{"startLine":511}}}],"partialFingerprints":{"codehealthFindingId/v1":"9756782fbcf6bcf69ecadcba87c58a71f25de18dee493466e295e0fb70e2922a"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AppStatusBarController: TooManyMethods \u2014 62 methods. The bar is 30 methods; this is 32 over it, 2.07\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/AppStatusBarController.swift"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"d9fe119054abf7c9554353085f4131999f7d2ec76f69432d3cb910a44c5a4f99"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: QuickAccessManager: TooManyMethods \u2014 60 methods. The bar is 30 methods; this is 30 over it, 2.00\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"204bf8aff40e27a9a489cd8f2bfe4966969f1976021acc88365c888c1c13f8fc"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: RecordingCoordinator: TooManyMethods \u2014 59 methods. The bar is 30 methods; this is 29 over it, 1.97\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"cf8dd98e3d431468465fe10cdda9e4e9c9fdc26a6595d8b328bdf46c754e4ce9"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AnnotateExporter: ClassTooLong \u2014 777 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 377 over it, 1.94\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"658a3cc450992a612f0b59fb9f37e4b063e960bf2def9eeaacb1869aa7cb9156"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/PreferencesCloudSettingsView.swift: FileTooLong \u2014 964 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 464 over it, 1.93\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"59abadbb612b59c7c2f763a429a1b32e1233c91a6f19beff9d9e949502a098a8"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureViewModel.startFrozenAreaSelection: MethodTooLong \u2014 startFrozenAreaSelection runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1037}}}],"partialFingerprints":{"codehealthFindingId/v1":"efded093c096c7bc62e3aa6f6583532e35537a38c212d166f12ee1bdcdae6664"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Recording/RecordingCoordinator.swift: FileTooLong \u2014 949 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: RecordingCoordinator (13-1445). The bar is 500 significant lines; this is 449 over it, 1.90\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"a34ae7a4a6354f29f51f91031c313eac23e14ccecb174cb0a0ac1868e68285ee"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AnnotateWindowController: TooManyMethods \u2014 56 methods. The bar is 30 methods; this is 26 over it, 1.87\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b34a864ed59324962028eef58c6d53e56f723a531badf1a5068e1f8b87e406a"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: CloudManager: ClassTooLong \u2014 741 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 341 over it, 1.85\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"3ae83211730cd2c9c5a56e746583ce2e9cd29305bc9f986a87b31e5b2118ce41"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Managers/AnnotateWindowController.swift: FileTooLong \u2014 908 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: AnnotateWindowController (39-1469). The bar is 500 significant lines; this is 408 over it, 1.82\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6e2847b0867478870774f9dc6ca7325cbadcf4668d2ca08e3b2e2b256f0de9b0"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: ScreenCaptureViewModel: TooManyMethods \u2014 53 methods. The bar is 30 methods; this is 23 over it, 1.77\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"4cc0e9e1ab5b91d7fdaf2012517c2b4bed56102b82cf29fafc407d0f74253302"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: KeyboardShortcutManager: TooManyMethods \u2014 53 methods. The bar is 30 methods; this is 23 over it, 1.77\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":583}}}],"partialFingerprints":{"codehealthFindingId/v1":"76ccf770ba99d39a48ec639392ecbb7d2efcb800bbaec9f3c2dc060ebea59aee"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: App/AppStatusBarController.swift: FileTooLong \u2014 876 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: AppStatusBarController (15-1303). The bar is 500 significant lines; this is 376 over it, 1.75\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/AppStatusBarController.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"b1a578cf14ca67fa9afecda0506acdfb40c319ee948b425c44a618bc9a1a506c"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Services/AnnotateExporter.swift: FileTooLong \u2014 862 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: AnnotateExporter (16-1138). The bar is 500 significant lines; this is 362 over it, 1.72\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7e0469cae911e822d7e69b5d256ee0c22bd7eebb7932a5b1d3c1221be90ae82"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureViewModel.captureOCR: MethodTooLong \u2014 captureOCR runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2366}}}],"partialFingerprints":{"codehealthFindingId/v1":"c8a82b8d08fb37900b5a54c5db25a7cc0057027719e3c0435188923b8ad8e707"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: InlineAreaAnnotateSession: TooManyMethods \u2014 51 methods. The bar is 30 methods; this is 21 over it, 1.70\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateSession.swift"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"abfc622097b86aca7ba18443b973fabdc77dfc300892e64cdba25952995c976a"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: VideoEditorExporter: ClassTooLong \u2014 646 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 246 over it, 1.62\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"d7f24e15434787e48521e81638c332292a62844c07350665818f60b00e66186f"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AnnotateExporter.renderFlatFinalImage: MethodTooLong \u2014 renderFlatFinalImage runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":403}}}],"partialFingerprints":{"codehealthFindingId/v1":"bf950e672e41404cd4b0ef26ffde90e28ce084b3c2b28feb781189029c7e692a"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: CaptureSettingsView: ClassTooLong \u2014 622 significant lines (blank, comment-only and punctuation-only lines excluded), 9 methods. The bar is 400 significant lines; this is 222 over it, 1.56\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"ea97e8b5fab47f5a19e8f84414dcf082060f962ff59f4cdf2eed21a68674ac0b"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: ScreenRecordingManager: TooManyMethods \u2014 45 methods. The bar is 30 methods; this is 15 over it, 1.50\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":683}}}],"partialFingerprints":{"codehealthFindingId/v1":"50e23353aed57d511a4207785cb0380d9ff530667fe0115c81a3d01c4c00e863"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Cloud/CloudManager.swift: FileTooLong \u2014 749 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: CloudManager (20-1063). The bar is 500 significant lines; this is 249 over it, 1.50\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"08e1fb274d3615e09dec2b40dcf7ce33bfb7a5adc6af5080337efd4f28910757"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Services/AnnotateBlurEffectRenderer.swift: FileTooLong \u2014 745 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 245 over it, 1.49\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6d110496877e8f2d066476679df5a20e623d665f6cb8b789d7068d86cd1a82ba"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/PreferencesCloudUploadHistoryView.swift: FileTooLong \u2014 737 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 237 over it, 1.47\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c14135cc97f349dbd348d4fbe293e488e8194f175aa63198908c3f11ad42f3a4"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: HistoryFloatingContentView: ClassTooLong \u2014 587 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 187 over it, 1.47\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryFloatingContentView.swift"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"81909d4553e8e6096aa7870aa023eba06822051bbaac5b911e9456b2ce281571"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: RecordingRegionOverlayView: ClassTooLong \u2014 581 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 181 over it, 1.45\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":184}}}],"partialFingerprints":{"codehealthFindingId/v1":"0754cbb454896f73f3896b7894576ca1af96f9a0c85dbf8184e345ca7bd71b8d"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureViewModel.captureObjectCutout: MethodTooLong \u2014 captureObjectCutout runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2696}}}],"partialFingerprints":{"codehealthFindingId/v1":"5a10a7fc2d603c4ca8472a6990e97be2dafc01a4602725884b170d6e844a1371"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AreaSelectionController.startSelectionSession: MethodTooLong \u2014 startSelectionSession runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"32a508325f0ad8cdb224923937ee1ee8105c44f5261e28cd414e179083cbac8f"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: InlineAreaPropertiesBar.body: MethodTooLong \u2014 body runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":1854}}}],"partialFingerprints":{"codehealthFindingId/v1":"238f21c72b77eeeca136698a2ec1b06355dff095b7ad620dd767ce8607f9fe34"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: VideoEditorWindowController: ClassTooLong \u2014 553 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 153 over it, 1.38\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"935aa2f9bfddb7eddd90181be4495f3fd4530af424c11ec37c948bee96a03515"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScrollingCaptureCoordinator.startAutoScrolling: MethodTooLong \u2014 startAutoScrolling runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":255}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a4625ffad3b317313da547bd7fb92032a2393497911c16d52d5837ba27bfc55"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Managers/RecordingRegionOverlayWindow.swift: FileTooLong \u2014 682 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: RecordingRegionOverlayView (184-1086). The bar is 500 significant lines; this is 182 over it, 1.36\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"20329fdb79a1cf4b3a76d3d8728f475933debdb36ad4147de68daf281597fc9e"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Services/AnnotateAnnotationRenderer.swift: FileTooLong \u2014 655 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 155 over it, 1.31\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"20af9ae66283c8d93d939a709daaf98b421ec818aaaa1575849fa920c1d6f629"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: CloudManager: TooManyMethods \u2014 39 methods. The bar is 30 methods; this is 9 over it, 1.30\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"d99b78ad068ba0e364d0093bc882849ec442bfa0651e05de42eb7107efdca5c0"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Services/VideoEditorExporter.swift: FileTooLong \u2014 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: VideoEditorExporter (13-1000). The bar is 500 significant lines; this is 149 over it, 1.30\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"c6b0792f0571d3156b1f2672a0ee6d8a199ee81107127312feec3ca32ce7a639"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureViewModel.startAreaCapture: MethodTooLong \u2014 startAreaCapture runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":657}}}],"partialFingerprints":{"codehealthFindingId/v1":"8f9330a38917fd1390a3c92873caec2170b235f1a4f6eaf29ddb4f45cd9198da"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/PreferencesCaptureSettingsView.swift: FileTooLong \u2014 644 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: CaptureSettingsView (35-972). The bar is 500 significant lines; this is 144 over it, 1.29\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"114ed7a64b13b15b3c17e523aa2971010b46202ddcdf77b8fc5e3995aa840a13"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScrollingCaptureAccuracyBenchmark.corpus: MethodTooLong \u2014 corpus 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\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift"},"region":{"startLine":24}}}],"partialFingerprints":{"codehealthFindingId/v1":"63f6959d637d3006963a22b768fedd2d10ca9708789b62118439d32e81d36f9b"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ShortcutsView.body: MethodTooLong \u2014 body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingShortcutsView.swift"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"fdec55c28e40600080eb90e6311c8150fb5ba6ad3382009479f592b46d659b4b"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: HistorySettingsView.body: MethodTooLong \u2014 body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesHistorySettingsView.swift"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"f42ab5dc59b0b1b4472e4d87f4988f055abc67330129b257e8f0ac674fa3dade"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: OCRService: ClassTooLong \u2014 499 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 99 over it, 1.25\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCRService.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"6bcbc61812a6c6ed1c11d11fc3cf51a5156135839963393605d0a2bef96c5073"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/QuickAccessCardView.swift: FileTooLong \u2014 622 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: QuickAccessCardView (13-762). The bar is 500 significant lines; this is 122 over it, 1.24\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"52c2eb93657bb4f68f0e6df66b207ab135549043f1b601ccec2f4bd420cc35e4"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/AnnotateSidebarComponents.swift: FileTooLong \u2014 618 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 118 over it, 1.24\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb2120614307f1303163d2faa6d01d034ac78d58b6fedf25e0383bf75bc90d29"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: RecordingRegionOverlayView: TooManyMethods \u2014 37 methods. The bar is 30 methods; this is 7 over it, 1.23\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":184}}}],"partialFingerprints":{"codehealthFindingId/v1":"774f86c939bbf57c7836e4fd0a6ce5c89f733dead03830ec30e75fccbcd3fc29"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: GIFConverter.convert: MethodTooLong \u2014 convert runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/GIFConverter.swift"},"region":{"startLine":41}}}],"partialFingerprints":{"codehealthFindingId/v1":"75e5c8fda266b7c5b35bdc872d27b47091fa5a6e2795c6296ad636d662a563e8"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: InlineAreaAnnotateSession: ClassTooLong \u2014 487 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 87 over it, 1.22\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateSession.swift"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"aecfb4aecf760f2118aa1675e7fbac4bc93dc6039c2c7b1cf9f2d523efac15f3"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: QuickAccessCardView: ClassTooLong \u2014 484 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 84 over it, 1.21\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"51f5a97a327950e67b5f60c292e4b1f85db9d977520cae7ffc685ca1b5e2ecd4"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: View: TooManyMethods \u2014 36 methods. The bar is 30 methods; this is 6 over it, 1.20\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":879}}}],"partialFingerprints":{"codehealthFindingId/v1":"b8c4d08e0d8e63580a7d28755f778fe4508935020207d69b1443468664a68035"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AdvancedSettingsView.body: MethodTooLong \u2014 body 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\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesAdvancedSettingsView.swift"},"region":{"startLine":32}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc1ab3a0596b1221995d7d15174d68d9058d830588e46c7ef176d6ef2dc73760"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/HistoryFloatingContentView.swift: FileTooLong \u2014 589 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: HistoryFloatingContentView (11-895). The bar is 500 significant lines; this is 89 over it, 1.18\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryFloatingContentView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2cf795ea1b144c86cd59b212bece575ad3eb1946016d6538b6bbb943908f33e"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AnnotateExporter: TooManyMethods \u2014 35 methods. The bar is 30 methods; this is 5 over it, 1.17\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"6bfa3269e5a4092df7c98ffb167b21a3b72bf85250eb281baedd8ba7bd0cb027"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: VideoEditorWindowController: TooManyMethods \u2014 35 methods. The bar is 30 methods; this is 5 over it, 1.17\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"485a879d6af88f85548467bafae3202823a1b417f16a5fa2d975ea6a4e6f35e3"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AreaSelectionMagnifier: ClassTooLong \u2014 460 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 60 over it, 1.15\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"36f7259e01778756ab10860344f51f6ccd3cb6be942bb621bd1fcdaa60770623"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: FrozenAreaCaptureSession.cropCompositeImage: MethodTooLong \u2014 cropCompositeImage runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":228}}}],"partialFingerprints":{"codehealthFindingId/v1":"cfc764849d5203a8d9179fb7fea103426af957415e9e84f22cf960ea83463a79"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureManager.makePreparedAreaCaptureContext: MethodTooLong \u2014 makePreparedAreaCaptureContext runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":1897}}}],"partialFingerprints":{"codehealthFindingId/v1":"2cb685ead82a9153505b2c4723397d171923b5ecd9be0ad437858b9764fd12bb"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: KeyboardShortcutManager.registerShortcuts: MethodTooLong \u2014 registerShortcuts runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1495}}}],"partialFingerprints":{"codehealthFindingId/v1":"727b01397d6d31426383fe0f9279e3b435ad145ffa13dc3f6b54d8dfdf51081d"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: ScrollingCaptureStitcher: TooManyMethods \u2014 34 methods. The bar is 30 methods; this is 4 over it, 1.13\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":73}}}],"partialFingerprints":{"codehealthFindingId/v1":"8c30c27d4693b42a3b2649f9a6833a636370bcde2c076d3d947db8aee58d810e"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: SnapzyConfigurationImporter: ClassTooLong \u2014 453 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 53 over it, 1.13\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"8db3ca397502c04e67bc1c78a0c3e54238ddf8d0830f5adb81b8910686ff3ed0"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AnnotateCanvasView.canvasContent: MethodTooLong \u2014 canvasContent runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":224}}}],"partialFingerprints":{"codehealthFindingId/v1":"5ae94db900f7bc361e167e6c0f33106456b15b1dd5907be4bda9b62df37a4e63"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Managers/VideoEditorWindowController.swift: FileTooLong \u2014 564 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: VideoEditorWindowController (30-853). The bar is 500 significant lines; this is 64 over it, 1.13\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"b4744d0f24fdd3a781902e9338977323b65088b977938d0e834c1ab19c318a1c"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: CloudCredentialFormView: ClassTooLong \u2014 451 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 51 over it, 1.13\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":776}}}],"partialFingerprints":{"codehealthFindingId/v1":"1903b588a9e9bbc077da641965bebdb19577357468f87da3c4eb9d659435e6f2"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: CaptureHistoryStore: ClassTooLong \u2014 450 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 50 over it, 1.13\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryStore.swift"},"region":{"startLine":20}}}],"partialFingerprints":{"codehealthFindingId/v1":"1391ca0023384c877de039fc33b67ea80d2a55bd2bedeb98a35156fb09b586d8"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AreaSelectionMagnifier.setupLayersIfNeeded: MethodTooLong \u2014 setupLayersIfNeeded runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":141}}}],"partialFingerprints":{"codehealthFindingId/v1":"29990890947d13634893c5e5b98c8b9db0e2a2bf106e565ff9d391eb5e34bf8a"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/AnnotateSidebarView.swift: FileTooLong \u2014 551 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: AnnotateSidebarView (70-617). The bar is 500 significant lines; this is 51 over it, 1.10\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"25a230c194c90ba9d09a90edda1544892ed5a499d30a7a665fc8a265101779b0"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: OCRService: TooManyMethods \u2014 33 methods. The bar is 30 methods; this is 3 over it, 1.10\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCRService.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"7949f1eda7fc5e0e16cfa229d424ee670d1e4f35e0a7eb17d2b8c8f9310e6b86"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureManager.captureAllDisplays: MethodTooLong \u2014 captureAllDisplays runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":673}}}],"partialFingerprints":{"codehealthFindingId/v1":"020fb2bc6940222a4e71f21b5d1d1a988c26639741b571cc7d161bc5244dae12"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: CloudSettingsView.cloudStatsSection: MethodTooLong \u2014 cloudStatsSection runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"53e8b340845b028770741230f1cc008e783b14edc94035a04927f9872b3ea445"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Components/VideoEditorSpeedTimelineTrack.swift: FileTooLong \u2014 536 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: SpeedTimelineTrack (31-564). The bar is 500 significant lines; this is 36 over it, 1.07\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6f428c112b7e6619a6990646750b6438d9ce93be633b588019049f5a07a3b044"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: AnnotateShortcutManager: TooManyMethods \u2014 32 methods. The bar is 30 methods; this is 2 over it, 1.07\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateShortcutManager.swift"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"76ad1fe7ac792b068062cd2fb3c5df7bd5266e6a854e2043c8c148d060a8110b"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScreenCaptureViewModel.startInlineAreaAnnotateCapture: MethodTooLong \u2014 startInlineAreaAnnotateCapture runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":838}}}],"partialFingerprints":{"codehealthFindingId/v1":"b8d3711921315b811acef5db173bfbfd124ffa48a901c0a9e2b14abab507a5b9"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: SnapzyMockSystemSettingsWindow: ClassTooLong \u2014 418 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 18 over it, 1.05\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"3f2f37324b7d2f16c9e1e4118d101840eb8bf21d00a66406e1244f42b2d97149"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Annotate/InlineAreaAnnotateSession.swift: FileTooLong \u2014 518 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: InlineAreaAnnotateSession (56-833). The bar is 500 significant lines; this is 18 over it, 1.04\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateSession.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"77e635f7f2b5c930e5890e18f884ab186657a190380c977ada1cbef0fbc00c42"}},{"ruleId":"D3","level":"warning","message":{"text":"TooManyMethods: SnapzyConfigurationService: TooManyMethods \u2014 31 methods. The bar is 30 methods; this is 1 over it, 1.03\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationService.swift"},"region":{"startLine":10}}}],"partialFingerprints":{"codehealthFindingId/v1":"6525d2afabc29e4d62ef19d1fbaf0eb90c4e57eadc0e0959dfaeb423f7322349"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Media/OCRService.swift: FileTooLong \u2014 515 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: OCRService (32-794). The bar is 500 significant lines; this is 15 over it, 1.03\u00D7 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 \u2014 the parts that share the same inputs and are named together \u2014 into its own unit in a sibling file, and have the original call them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCRService.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"477719cf8014efec0c05aff01eee3bb5237efce279dd6996933e8b2eb10764bb"}},{"ruleId":"D3","level":"warning","message":{"text":"FileTooLong: Managers/RecordingCameraOverlayWindow.swift: FileTooLong \u2014 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"9860defe7cd3752ec45db0b643d6e133eed4ecdaeda5b764b23ff5cd1d4ad1fb"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AnnotateBottomBarView: ClassTooLong \u2014 411 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 11 over it, 1.03\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":45}}}],"partialFingerprints":{"codehealthFindingId/v1":"583cf254cbbb0cede8e63de44760a1fbcb371201a66e1066b4929222c1f0d19f"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ScrollingCaptureSelectionGuidanceKind.guidance: MethodTooLong \u2014 guidance 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\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureTypes.swift"},"region":{"startLine":121}}}],"partialFingerprints":{"codehealthFindingId/v1":"27657968b285f62111375d5feaffebfe6dadf3f2969b10670808bb8967e65a6b"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ShortcutConfig.keyCodeToString: MethodTooLong \u2014 keyCodeToString 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\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":190}}}],"partialFingerprints":{"codehealthFindingId/v1":"dae2ae2a9601fcdd15e712113abf69651398af804426788f14346113f0435bae"}},{"ruleId":"D3","level":"warning","message":{"text":"ClassTooLong: AdvancedSettingsView: ClassTooLong \u2014 404 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 4 over it, 1.01\u00D7 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesAdvancedSettingsView.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"604485903bcbc2a0f59461e7282fda9838bebe37a38cffd14ffdc66bfe33fe9d"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: QuickAccessSettingsView.body: MethodTooLong \u2014 body runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01\u00D7 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 \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessSettingsView.swift"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"aa8c9c0e52276e5e22b631db9b992fc76c73edf498d71b8e4a067be5fed088d0"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member family (3 members, 17 shared lines): Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:48-77 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:81-108 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:112-139 \u2014 These 3 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members\u0027 grain \u2014 factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift"},"region":{"startLine":48}}}],"partialFingerprints":{"codehealthFindingId/v1":"9420ddcbefd77bdf001b9e8b4ff6c5d0da12db2f0869b2263c39704c330583c1"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member pair (71 shared lines): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:266-353 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:415-505 \u2014 These two members are variants of one another: 71 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members\u0027 grain \u2014 factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":266}}}],"partialFingerprints":{"codehealthFindingId/v1":"c663302c2e9204b8fdedb41129192fba581b17b43ec80e19a4a30477722c71e3"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member pair (48 shared lines): Snapzy/Features/Recording/RecordingCoordinator.swift:692-823 | Snapzy/Features/Recording/RecordingCoordinator.swift:873-965 \u2014 These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members\u0027 grain \u2014 factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":692}}}],"partialFingerprints":{"codehealthFindingId/v1":"3203e2f744cb4b99fbb2fce3a658474e1fba068aff7813826b6d5d6a80e816f4"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member pair (38 shared lines): Snapzy/Shared/Extensions/View\u002BCornerRadius.swift:26-87 | Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:38-103 \u2014 These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members\u0027 grain \u2014 factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Extensions/View\u002BCornerRadius.swift"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"943fb1ca10ed18b6327aceef36976b318712d9c733f63052de2e40111cb0df0d"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member pair (31 shared lines): Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2660-2692 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1250-1282 \u2014 These two members are variants of one another: 31 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members\u0027 grain \u2014 factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":2660}}}],"partialFingerprints":{"codehealthFindingId/v1":"db17fcb01047602274926f87d75fc72ac1b0e488b8d5832d9fc05fc03feb71fd"}},{"ruleId":"D4","level":"warning","message":{"text":"Near-duplicate member pair (29 shared lines): Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2207-2260 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:374-427 \u2014 These two members are variants of one another: 29 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members\u0027 grain \u2014 factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2207}}}],"partialFingerprints":{"codehealthFindingId/v1":"b3ffcc06fbe52464874df21366aa4636a25431e26576aa5e2ed4e3d8d7bd6d7c"}},{"ruleId":"D4","level":"warning","message":{"text":"Edited copy of a member (57 corresponding lines): Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:641-756 | Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:779-865 \u2014 These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below \u2014 the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members\u0027 grain \u2014 factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":641}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae26bcf91e58b7f7f96e0bd82d303bd4e24219ed9f9dc412ea4c4f8cfff5f5cf"}},{"ruleId":"D4","level":"warning","message":{"text":"Edited copy of a member (16 corresponding lines): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1232-1263 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:834-856 \u2014 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 \u2014 the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members\u0027 grain \u2014 factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1232}}}],"partialFingerprints":{"codehealthFindingId/v1":"d074565a4fb692b924ba3bd0c207bfe5c20413100e1a089850a2086aa5f09eec"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (5 members, 50\u002B identical tokens): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:605-663 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:700-776 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:813-866 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:939-986 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:1012-1064 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":605}}}],"partialFingerprints":{"codehealthFindingId/v1":"12edffbfb36b5bd0bfcffbfbd5d4298d63c1cca1c6c6071d33858711b6cbc865"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (5 members, 50\u002B identical tokens): Snapzy/Features/History/Components/HistoryCardView.swift:166-176 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:160-170 | Snapzy/Features/History/Components/HistoryToolbar.swift:121-131 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:514-524 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:908-918 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":166}}}],"partialFingerprints":{"codehealthFindingId/v1":"8cb7ed5b014e042da68c39a1b957b6356f6ba294fb88105702ee82b3737f7394"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (5 members, 50\u002B identical tokens): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:49-141 | Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:58-84 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:15-104 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:47-163 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:73-124 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":49}}}],"partialFingerprints":{"codehealthFindingId/v1":"603be0739c231620ecca12e65b0a018b0b099296d34893455faef2ef1385e3de"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Snapzy/Features/Capture/CaptureViewModel.swift:657-836 | Snapzy/Features/Capture/CaptureViewModel.swift:838-972 | Snapzy/Features/Capture/CaptureViewModel.swift:1979-2062 | Snapzy/Features/Capture/CaptureViewModel.swift:2696-2899 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":657}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc9d54f698191ce4f381e5bfe15593762b70a8bdf53832962ad165fccb1bfdab"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Snapzy/Features/History/Managers/HistoryFloatingPanelController.swift:235-262 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:36-70 | Snapzy/Features/Recording/Components/RecordingAnnotationToolbarContentBuilder.swift:28-62 | Snapzy/Features/Recording/RecordingToolbarWindow.swift:506-544 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanelController.swift"},"region":{"startLine":235}}}],"partialFingerprints":{"codehealthFindingId/v1":"fc576292e2b61529b739629a1bb3e36ecf37b0671a691bc9c071b43daec72c00"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1441-1460 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1568-1587 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1595-1614 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1649-1668 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1441}}}],"partialFingerprints":{"codehealthFindingId/v1":"93af507f8ca3ffe2ba4c70898594a7e2f5b03983c682c6d1f5f65aa05a10323f"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:183-212 | Snapzy/Features/Onboarding/Components/OnboardingDiagnosticsOptInView.swift:17-91 | Snapzy/Features/Onboarding/Components/OnboardingSkipConfirmationView.swift:14-73 | Snapzy/Features/Onboarding/Components/OnboardingSponsorView.swift:16-90 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift"},"region":{"startLine":183}}}],"partialFingerprints":{"codehealthFindingId/v1":"25c610bbbe2d67351ed65db6cb87d6a019db68036c75f50eab8946543ab856dc"}},{"ruleId":"D4","level":"warning","message":{"text":"Members sharing a duplicated core (4 members, 50\u002B identical tokens): Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:32-54 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:15-104 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:23-43 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:199-232 \u2014 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 \u2014 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\u0027 grain \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift"},"region":{"startLine":32}}}],"partialFingerprints":{"codehealthFindingId/v1":"764d62d385bd1345500f27e4cab194ee8beacb24456bc717062a59322d03ef6f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (77 lines \u00D7 2): Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:1242-1318 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:1336-1412 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:1242\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:1415\u0060 calls \u0060copyImage\u0060 and \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:1320\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":1242}}}],"partialFingerprints":{"codehealthFindingId/v1":"dfc8fd0bf2082f1e99bff10ba7cd825536d09b0d4c1b730859d57f6333ae3578"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (57 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:700-756 | Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:801-857 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:700\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:799\u0060 calls \u0060blurEffectValue\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift:697\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":700}}}],"partialFingerprints":{"codehealthFindingId/v1":"575d698df8aeb702d02ce8e4759eb4ccde5191745d1c54e2915ce14ab7ecb9ec"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (54 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:790-843 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2200-2253 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:790\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":790}}}],"partialFingerprints":{"codehealthFindingId/v1":"05c5d19fbb669556778700bf529d1413052f4350d5f71d449ccb2f7e4688cefd"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (54 lines \u00D7 2): Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:306-359 | Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:402-455 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:306\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveOAuthService.swift"},"region":{"startLine":306}}}],"partialFingerprints":{"codehealthFindingId/v1":"cf3d25f2c6792174bceaa6b00eec52f7b8988925f52238ffbf526d4a4b466f32"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (50 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:749-798 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:130-179 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:749\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":749}}}],"partialFingerprints":{"codehealthFindingId/v1":"57c0c09d076f7b4bf5b6e66d0d5dbd7312f79c4e35dfc18d8c626ea68e59654f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (38\u201339 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:251-288 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:90-128 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 127 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:251\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":251}}}],"partialFingerprints":{"codehealthFindingId/v1":"54d3400e101b2397e2e60ba29c6d3d4302c735754ee3cc3f204a2d5d4b62f29c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (36\u201338 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:485-520 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:180-217 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 127 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":485}}}],"partialFingerprints":{"codehealthFindingId/v1":"a18a0803b6d36025934221534aad589f223d2db934cf8f18edbe4e96abae30e1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (33\u201338 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:216-248 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:179-216 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:216\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":216}}}],"partialFingerprints":{"codehealthFindingId/v1":"7618dc81611d3e66f094cf6c6fbcf0f6f1128363ecf69f6633469144beb9b3ca"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (33\u201336 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:676-708 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:52-87 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:676\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":676}}}],"partialFingerprints":{"codehealthFindingId/v1":"055a659363b15161ba67d264bdd538ba644d96f0bb874d896a8d3bfdd7d1946f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (35\u201336 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:443-477 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:141-176 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 127 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:443\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u00606\u0060 in one and \u00604\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:479\u0060 calls \u0060Text\u0060, \u0060font\u0060, \u0060system\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:177\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":443}}}],"partialFingerprints":{"codehealthFindingId/v1":"82a5be726646bb1b755df65cd761ed66fa302d4c396d7b417de043f39928dd48"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (35 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateMockupCanvasView.swift:40-74 | Snapzy/Features/Annotate/Services/AnnotateMockupExporter.swift:157-191 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateMockupCanvasView.swift"},"region":{"startLine":40}}}],"partialFingerprints":{"codehealthFindingId/v1":"930caa80cc002e3cfef2ca2efcf9c1301a68be069ae8c607287bddb889b012c6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (34 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:896-929 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2306-2339 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:896\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":896}}}],"partialFingerprints":{"codehealthFindingId/v1":"535d13236ffd767a65aa0c0eb585dc526752dc6f24ffbda901209751d17c6335"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (33 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:627-659 | Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift:163-195 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":627}}}],"partialFingerprints":{"codehealthFindingId/v1":"56529aa5f31247bb84104248b5f96db05ad0b253d503eed8458155463498a224"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (32 lines \u00D7 2): Snapzy/Features/History/Components/HistoryCardView.swift:51-82 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:59-90 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/Components/HistoryCardView.swift:51\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"268d535a9bbd392e088a153a4c63d69ccf5f50924e2a96b373fa09d46158919f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (30 lines \u00D7 2): Snapzy/Features/QuickAccess/QuickAccessManager.swift:260-289 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:335-364 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":260}}}],"partialFingerprints":{"codehealthFindingId/v1":"269fb3a6ae4146e2144a96ecfcd9cb360a7f1e45daade23e1f37cdb34ac23b46"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (28\u201330 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateMockupPresetBar.swift:73-102 | Snapzy/Features/Annotate/Components/AnnotateMockupPresetBarInline.swift:67-94 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateMockupPresetBar.swift"},"region":{"startLine":73}}}],"partialFingerprints":{"codehealthFindingId/v1":"c8d5cea3cabceca5e273705e09a8b26851d80cfe57dabe8d6dff98b5ca9970ca"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (28\u201329 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateState.swift:2265-2293 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:343-370 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:343\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":2265}}}],"partialFingerprints":{"codehealthFindingId/v1":"7ead8202fdb8dbea5af0eeb33377b032a6924188f6cfa43ed01216c6aa36acd2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (29 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:325-353 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:477-505 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:325\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":325}}}],"partialFingerprints":{"codehealthFindingId/v1":"4e032fd94e62a878660f95c0f5b058b62a18e9abd9b1d3d30e0c780d4f7590dc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (27\u201328 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:307-333 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:448-475 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:307\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:334\u0060 calls \u0060restoreGraphicsState\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:476\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":307}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc5f7f25666adc5c3fc63ef4c6b5055a5cfd78d5ad46e9ba435275d75c798f07"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (27 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1104-1130 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2445-2471 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1104}}}],"partialFingerprints":{"codehealthFindingId/v1":"55aa28635fa31e0a4e8f14efa145998c6a755a30354c3920945792ddca7523e1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24\u201327 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:765-791 | Snapzy/Features/Recording/RecordingCoordinator.swift:919-942 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:765\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:794\u0060 calls \u0060setupClickHighlightOverlay\u0060, \u0060setupKeystrokeOverlay\u0060 and \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:943\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":765}}}],"partialFingerprints":{"codehealthFindingId/v1":"c2607f62173b6d0bd184bb824f1e1b42cc984dc27c3f88df5952c232295e5ec5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (27 lines \u00D7 2): Snapzy/Shared/Localization/AppLanguageManager.swift:144-170 | scripts/swift-tools/ocr/ocr-readme-benchmark.swift:61-87 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Localization/AppLanguageManager.swift"},"region":{"startLine":144}}}],"partialFingerprints":{"codehealthFindingId/v1":"b78d198dfaf730d302317491262bc9f87e3debb6693970582fa0d7d71af523b2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26\u201327 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:669-694 | Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift:199-225 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:669\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":669}}}],"partialFingerprints":{"codehealthFindingId/v1":"c38e1db08363740fa55c65120ff399c3c18d37aee20958094de881269d70adf8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26\u201327 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateMockup3DRenderer.swift:31-57 | Snapzy/Features/Annotate/Services/AnnotateMockupExporter.swift:107-132 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateMockup3DRenderer.swift:31\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateMockupExporter.swift:106\u0060 calls \u0060frame\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateMockup3DRenderer.swift:30\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateMockup3DRenderer.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"98a7280eed0bb5823d2da2c7af9a60cc4252b7ece5ac04935721616c8dd3d6d9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (25\u201327 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift:137-161 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassWindowBackdrop.swift:20-46 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift:137\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift"},"region":{"startLine":137}}}],"partialFingerprints":{"codehealthFindingId/v1":"05f58eb67d010d636157899df1dd75301113aca6c223213fa6bb0140f28d1635"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (27 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:310-336 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:271-297 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:310\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":310}}}],"partialFingerprints":{"codehealthFindingId/v1":"1c64ba1fdb18767c9b65997b2e48af68c5450c94863bce00f9d7fbb18fca7664"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:796-821 | Snapzy/Features/Capture/CaptureViewModel.swift:899-924 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:796\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":796}}}],"partialFingerprints":{"codehealthFindingId/v1":"59c1699056fcd82f4e3c8ec8c192ed8f174cde272b61831f4c7987a970bc4ae6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26 lines \u00D7 2): Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift:254-279 | Snapzy/Services/Configuration/SnapzyConfigurationShortcutCodec.swift:69-94 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift:254\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift"},"region":{"startLine":254}}}],"partialFingerprints":{"codehealthFindingId/v1":"2b949362a0e4cf7d728d3bf6f769085e2d30d85134bd9dc5e05beca070d19bc3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (26 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:295-320 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:442-467 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":295}}}],"partialFingerprints":{"codehealthFindingId/v1":"621bd98e98b4e71dc128333f7f61b3e6406183ad6e39049df7b2f2234b6e222e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (25 lines \u00D7 2): Snapzy/Services/Capture/AreaSelectionWindow.swift:4013-4037 | Snapzy/Services/Capture/AreaSelectionWindow.swift:4067-4091 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/AreaSelectionWindow.swift:4013\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":4013}}}],"partialFingerprints":{"codehealthFindingId/v1":"108439e58e02e7b8ceb073631f1cf39ec23e7a00f3b564495eae2c01322fb534"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24 lines \u00D7 2): Snapzy/Features/History/HistoryWindowController.swift:19-42 | Snapzy/Features/History/Managers/HistoryFloatingPanel.swift:61-84 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/HistoryWindowController.swift\u0060 and \u0060Snapzy/Features/History/Managers/HistoryFloatingPanel.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/HistoryWindowController.swift:19\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/HistoryWindowController.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"a3b7280f46c863847d1adfe1ca31bfd8454a2dc7a614239ef7a85ecb7f90f134"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:93-116 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:271-294 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:93\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:270\u0060 calls \u0060cornerRadius\u0060 and \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:92\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":93}}}],"partialFingerprints":{"codehealthFindingId/v1":"af8602e7fe9bff850d0a972d77aef1f2ba2f411cdd14885d86550fcf7c5c1de7"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:375-398 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:341-364 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":375}}}],"partialFingerprints":{"codehealthFindingId/v1":"9425ca4b3826d8faf424c0186799d7eeff32ad6a6aef9f741873c50662c5a510"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (23 lines \u00D7 3): Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:106-128 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:140-162 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:215-237 \u2014 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 \u2014 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 \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:106\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":106}}}],"partialFingerprints":{"codehealthFindingId/v1":"7b63a7fd82873bad61022f7f74aa967df97303d64dd1ee2cb263c154721af01c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (23 lines \u00D7 3): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:708-730 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:947-969 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:1020-1042 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":708}}}],"partialFingerprints":{"codehealthFindingId/v1":"b562fbfa21085283dcf2df38207006d2a9ad742c36e65b4953a4385ca27ad8c5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20\u201323 lines \u00D7 2): Snapzy/Services/Capture/WindowSelectionQueryService.swift:210-232 | Snapzy/Services/Capture/WindowSelectionQueryService.swift:277-296 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/WindowSelectionQueryService.swift:210\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":210}}}],"partialFingerprints":{"codehealthFindingId/v1":"1b92f6e0dac162a26ffe1c94ae2657d49cd25e6c7019963149d07616d95b042b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (23 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:148-170 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:199-221 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:148\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":148}}}],"partialFingerprints":{"codehealthFindingId/v1":"24b0adfdd9fa8a0c4cee1cc0a13eee5624d2c5c03bd008d313943ba42e3cd5b3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201322 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:660-681 | Snapzy/Features/Capture/CaptureViewModel.swift:839-857 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:660\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":660}}}],"partialFingerprints":{"codehealthFindingId/v1":"810956c85168e1ab91f6882eeef4014e0d2c8f6ce7877601be5b088ad75f7040"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201322 lines \u00D7 2): Snapzy/Features/QuickAccess/QuickAccessManager.swift:373-394 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:1447-1465 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/QuickAccess/QuickAccessManager.swift:373\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":373}}}],"partialFingerprints":{"codehealthFindingId/v1":"da9097ef37aaf7c40aaffeba8d35aed4bdefbf278e360cc287035e19aafdfdc0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (22 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:751-772 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:794-815 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:751\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":751}}}],"partialFingerprints":{"codehealthFindingId/v1":"0060b90cb7cabdb1a9ac3ea3fca5af63edca175e82389bff86e32246dcc4e7d5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (22 lines \u00D7 2): Snapzy/Features/History/Components/HistoryToolbar.swift:40-61 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:432-453 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryToolbar.swift\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/Components/HistoryToolbar.swift:40\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryToolbar.swift"},"region":{"startLine":40}}}],"partialFingerprints":{"codehealthFindingId/v1":"c2246fd773b9cbe1478f03c231df2a67ab100938732d4ccfc5430e8f29996ac0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201321 lines \u00D7 2): Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift:238-258 | scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-support.swift:144-162 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-support.swift:144\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":238}}}],"partialFingerprints":{"codehealthFindingId/v1":"522bf22d6a5509ad25761703e2525a00ce8d8a61a496183e3e747f0e5283fb89"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (21 lines \u00D7 2): Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:78-98 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:188-208 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:78\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":78}}}],"partialFingerprints":{"codehealthFindingId/v1":"deb5bd2219cac66c13dca732164316b8de0961ddd736ad7993efbbec6d060b96"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20\u201321 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:347-366 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:529-549 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:347\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:345\u0060 calls \u0060CGRect\u0060, \u0060drawCanvasShadow\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:529\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":347}}}],"partialFingerprints":{"codehealthFindingId/v1":"10a2af95d92ce47b838e7b3ab31bf973c582a77368beaff69a489cf8996e039a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201320 lines \u00D7 3): Snapzy/Features/QuickAccess/QuickAccessManager.swift:901-920 | Snapzy/Features/QuickAccess/Services/QuickAccessThumbnailGenerator.swift:119-137 | Snapzy/Features/QuickAccess/Services/QuickAccessThumbnailGenerator.swift:188-207 \u2014 there are 3 copies across 2 file(s) \u2014 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 \u0060Snapzy/Features/QuickAccess/QuickAccessManager.swift:901\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":901}}}],"partialFingerprints":{"codehealthFindingId/v1":"33b6f0d88c90f07f6963829d8fdca2031536f96fa95caa79d0a902c275cc8e65"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/App/MenuBarIconRenderer.swift:52-71 | Snapzy/App/MenuBarIconRenderer.swift:115-134 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/App/MenuBarIconRenderer.swift:52\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/MenuBarIconRenderer.swift"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"0622f7b3426aabca0317450e632b641577595d5a12f86fe6c85e73b747490b03"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1132-1151 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2473-2492 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1132}}}],"partialFingerprints":{"codehealthFindingId/v1":"ba31e08711fb0299d75af713820b824fd8c64035774f3f5798a8b07feb4ec769"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1297-1316 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2707-2726 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1297\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1297}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc0418b70f461cf4a510337b4970bac833f077c57fcc35b38a522edb99005180"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19\u201320 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:2376-2395 | Snapzy/Features/Capture/CaptureViewModel.swift:2730-2748 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:2376\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2376}}}],"partialFingerprints":{"codehealthFindingId/v1":"c23041b00330cc6b59c5f3afadcba56b2ce81789267b6880851d10dc85dd7b9b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:2397-2416 | Snapzy/Features/Capture/CaptureViewModel.swift:2750-2769 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:2397\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2397}}}],"partialFingerprints":{"codehealthFindingId/v1":"4231f31b8821879372a5245fb261e5f324bea15ae3df842909be3b19dc9af412"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1679-1698 | Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1723-1742 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1679\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1674\u0060 calls \u0060shouldRegisterNow\u0060 and \u0060Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1720\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1679}}}],"partialFingerprints":{"codehealthFindingId/v1":"ca6bd17d1b04e656d46c23bda882b62e2708672bb22f25819e4a545cf28de602"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (20 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:203-222 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:254-273 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift"},"region":{"startLine":203}}}],"partialFingerprints":{"codehealthFindingId/v1":"5a3a439588c0120f9ee48f451a5e19b42e2991ee174af9c3010605c4bbb10aad"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11\u201320 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:501-511 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:463-482 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":501}}}],"partialFingerprints":{"codehealthFindingId/v1":"3c70602f2177f655f61ba02ebc07c9068b6c5c5143ae4eaaedbb5e2bd1637e1b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17\u201319 lines \u00D7 3): Snapzy/Services/Capture/ScreenCaptureManager.swift:2258-2274 | Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift:89-107 | Snapzy/Services/Media/ForegroundCutoutService.swift:281-298 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:2258\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":2258}}}],"partialFingerprints":{"codehealthFindingId/v1":"0f4028bae7726dd6c1f1aa1a63fe4eecddcc1ebc44511b322a8b3b4621b1f686"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:656-674 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:557-575 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:656\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:576\u0060 calls \u0060offset\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:675\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":656}}}],"partialFingerprints":{"codehealthFindingId/v1":"89e60de3a278d61ad51f98599b5c219cacb0fbc806ff3ac04460fab5cdc229b2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17\u201318 lines \u00D7 3): Snapzy/Features/Capture/CaptureViewModel.swift:662-679 | Snapzy/Features/Capture/CaptureViewModel.swift:839-855 | Snapzy/Features/Capture/CaptureViewModel.swift:2711-2728 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":662}}}],"partialFingerprints":{"codehealthFindingId/v1":"0f803357373e47a582aa778db70db817f43a16ab931fe7a48d83843dc71df299"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201318 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:1220-1235 | Snapzy/Features/Capture/CaptureViewModel.swift:1259-1276 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:1220\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1220}}}],"partialFingerprints":{"codehealthFindingId/v1":"d3ebfcd1384e2a9a69fc0413d8207c2a4818c86ff6b02994be16218e624ba114"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:1985-2002 | Snapzy/Features/Capture/CaptureViewModel.swift:2707-2724 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:1985\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Capture/CaptureViewModel.swift:2706\u0060 calls \u0060play\u0060 and \u0060Snapzy/Features/Capture/CaptureViewModel.swift:1985\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1985}}}],"partialFingerprints":{"codehealthFindingId/v1":"d1675aaa16d5b9ce59c50c319bee24ca24cd6e78f49d064b3ea193f04e170b56"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Services/Capture/ScreenRecordingManager.swift:1208-1225 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1235-1252 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1208\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1208}}}],"partialFingerprints":{"codehealthFindingId/v1":"ea5a339820e60aec73616c09b5766f42bed3efc121c30c39ea84ad7c7830b897"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Services/Cloud/CloudManager.swift:845-862 | Snapzy/Services/Cloud/CloudManager.swift:915-932 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/CloudManager.swift:845\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":845}}}],"partialFingerprints":{"codehealthFindingId/v1":"8114a4b5d5245ad25067e7993ffc386b651748588ee607dcb354f7de7c282cd3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15\u201318 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:1308-1322 | Snapzy/Shared/Components/ShortcutRecorderView.swift:131-148 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:1308\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":1308}}}],"partialFingerprints":{"codehealthFindingId/v1":"37a102e02df016edac92b014d05fc71a3960606e048f47e5461ef839d6cb8de3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Features/Annotate/Models/AnnotateAnnotationToolType.swift:51-68 | Snapzy/Features/Annotate/Models/AnnotateAnnotationToolType.swift:72-89 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationToolType.swift"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"1f8bd53a6fe351126dee0b6ec246f47d723634310a21e4b6e6d3debcf712b70c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Features/History/Components/HistoryCardView.swift:97-114 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:105-122 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/Components/HistoryCardView.swift:97\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":97}}}],"partialFingerprints":{"codehealthFindingId/v1":"c6cf4fcfdfdde8c161fc5ccc6d9789d7be88666718898c20ea26354f0480a7bc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:357-374 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:380-397 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:357\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift"},"region":{"startLine":357}}}],"partialFingerprints":{"codehealthFindingId/v1":"70b9595f3243e23cab48e7b84813c759de3920a6a2be7344239ccb3dff33b596"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11\u201318 lines \u00D7 2): Snapzy/Features/QuickAccess/Models/QuickAccessActionKind.swift:148-165 | Snapzy/Services/Configuration/SnapzyConfigurationShortcutsExporter.swift:174-184 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Models/QuickAccessActionKind.swift"},"region":{"startLine":148}}}],"partialFingerprints":{"codehealthFindingId/v1":"480ed8c82f76e0aa1f617d73772c9be372398653bb709962721d254e875aa5a5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201317 lines \u00D7 3): Snapzy/Features/Recording/RecordingCoordinator.swift:633-649 | Snapzy/Features/Recording/RecordingCoordinator.swift:766-782 | Snapzy/Features/Recording/RecordingCoordinator.swift:920-935 \u2014 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 \u2014 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 \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:633\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":633}}}],"partialFingerprints":{"codehealthFindingId/v1":"8bd710523415ff3ff9d15937be1d5a246c482a29ff717ae337760be15326314a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 3): Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:642-658 | Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift:726-742 | Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift:178-194 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":642}}}],"partialFingerprints":{"codehealthFindingId/v1":"d5bc91157c96da88792e0f4d073b9fb90ec056d51067c9fd9703dd1fca7afa56"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201317 lines \u00D7 3): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:314-330 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:456-472 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:1073-1088 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:334\u0060 calls \u0060restoreGraphicsState\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:476\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":314}}}],"partialFingerprints":{"codehealthFindingId/v1":"01feac4a80f0d56ca796753b21e37a5e8224aeb4fd9e8fc7729b8ab9e96a24b8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 3): Snapzy/Features/History/Components/HistoryCardView.swift:65-81 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:73-89 | Snapzy/Features/History/Components/HistoryItemView.swift:124-140 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/Components/HistoryCardView.swift:65\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":65}}}],"partialFingerprints":{"codehealthFindingId/v1":"46df16e8c3c13bc902cd368ebd4b341991d73648f2c07b9582ff3ffec0c3f15d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1208-1224 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2618-2634 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1208\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1208}}}],"partialFingerprints":{"codehealthFindingId/v1":"1edf628531699ba024e6bbb911808f715405b3c702636ebc47602f21d404052a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:1098-1114 | Snapzy/Features/Capture/CaptureViewModel.swift:1320-1336 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:1098\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1098}}}],"partialFingerprints":{"codehealthFindingId/v1":"9348c7f770065e1da841d5d423003eda458fdcbd162727af268275f198365aa8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:1511-1527 | Snapzy/Features/Capture/CaptureViewModel.swift:1586-1602 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:1511\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":1511}}}],"partialFingerprints":{"codehealthFindingId/v1":"4e270d8fe440f2fee6714db55b2d05c0e99132fc5bba45484cc53c47cb7fe4c0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Features/History/HistoryWindowController.swift:41-57 | Snapzy/Features/History/Managers/HistoryFloatingPanel.swift:92-108 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/HistoryWindowController.swift\u0060 and \u0060Snapzy/Features/History/Managers/HistoryFloatingPanel.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/HistoryWindowController.swift:41\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/HistoryWindowController.swift"},"region":{"startLine":41}}}],"partialFingerprints":{"codehealthFindingId/v1":"dcec488b51bf32bd3943002b6a850a06092344cf60fdc213d2b408075edae703"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:2453-2469 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1851-1867 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":2453}}}],"partialFingerprints":{"codehealthFindingId/v1":"b941db1f929dfba00f8f8b59d8e6f9188762b3bdca3db4ffa0584b75939dde56"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (2\u201317 lines \u00D7 3): Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:474-475 | Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:141-157 | Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:562-578 \u2014 there are 3 copies across 2 file(s) \u2014 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 \u0060Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:141\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:581\u0060 calls \u0060signingFailed\u0060 and \u0060Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:159\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift"},"region":{"startLine":474}}}],"partialFingerprints":{"codehealthFindingId/v1":"c8953be27dbaadd8ee8252cd48776d3a4e9a47c72fb408ab32f020cf031db0e3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201317 lines \u00D7 2): Snapzy/Services/Configuration/SimpleTOMLParser.swift:77-93 | Snapzy/Services/Configuration/SimpleTOMLParser.swift:142-157 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Configuration/SimpleTOMLParser.swift:77\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SimpleTOMLParser.swift"},"region":{"startLine":77}}}],"partialFingerprints":{"codehealthFindingId/v1":"39490592773437895294166ad69f74883cb8b71b2122a06e7df0ab3ebb55d977"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:26-42 | scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:47-63 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:26\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift"},"region":{"startLine":26}}}],"partialFingerprints":{"codehealthFindingId/v1":"e8eab6758ceb4bdd3a824e639564ed0b0fbc89c3a0ad57795b267f92ac0cb716"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift:71-87 | Snapzy/Features/Preferences/Components/PreferencesCloudCredentialImportSheet.swift:53-69 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift:71\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"0a9f838a1e44bbe9df8af8373ef3d9301d612dcded374c50204a6ac4f3f61456"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 4): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:606-621 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:701-716 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:940-955 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:1013-1028 \u2014 all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:606\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":606}}}],"partialFingerprints":{"codehealthFindingId/v1":"48d073070016a0895062175cc24af34ae44997c9037f15484d6780cfa9dc887f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:986-1001 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2521-2536 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:986\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":986}}}],"partialFingerprints":{"codehealthFindingId/v1":"e88a069acc1805e9441464216375f50b32b0a1706c99697b3f0c5cd99ad1fd02"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1226-1241 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2636-2651 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1226\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1226}}}],"partialFingerprints":{"codehealthFindingId/v1":"130641a986b020e15550c7c7007a5e8ab0739daa92dda2a4169cef3aa65b92b5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14\u201316 lines \u00D7 2): Snapzy/Features/Preferences/PreferencesWindowController.swift:125-140 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPlaygroundWindowController.swift:74-87 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/PreferencesWindowController.swift"},"region":{"startLine":125}}}],"partialFingerprints":{"codehealthFindingId/v1":"988569d5b3b5e9327de078d703f478ec7734fc720f90b128624361a9f7e0522b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:114-129 | Snapzy/Services/Capture/ScreenshotLastAreaStore.swift:32-47 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:114\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":114}}}],"partialFingerprints":{"codehealthFindingId/v1":"d6b3927189c3460f53f6800b34dd11974624155fc4c03a082b2f00b186957b93"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:808-823 | Snapzy/Features/Recording/RecordingCoordinator.swift:950-965 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:808\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:949\u0060 calls \u0060log\u0060 and \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:806\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":808}}}],"partialFingerprints":{"codehealthFindingId/v1":"74ba1a13e9df62f5dfeb5975c8a802c2cd69df441c8545d40a368e21601e1db8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13\u201316 lines \u00D7 2): Snapzy/Features/Recording/Components/RecordingAnnotationToolbarContentBuilder.swift:43-55 | Snapzy/Features/Recording/RecordingToolbarWindow.swift:520-535 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Components/RecordingAnnotationToolbarContentBuilder.swift"},"region":{"startLine":43}}}],"partialFingerprints":{"codehealthFindingId/v1":"ee76764e5ddf0aeb14bc62c34a6b0d568787ff5d5d3c6fc3a34f996fed91bd81"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15\u201316 lines \u00D7 2): Snapzy/Services/Capture/AXElementSnapshot.swift:139-153 | Snapzy/Services/Capture/ActiveWindowResolver.swift:112-127 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AXElementSnapshot.swift"},"region":{"startLine":139}}}],"partialFingerprints":{"codehealthFindingId/v1":"c079e21d064666a9d9ec27e6e2a0e8a24feed70b3547bd7fae59d47f315becb4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15\u201316 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:188-203 | Snapzy/Services/Cloud/S3CloudProvider.swift:347-361 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/S3CloudProvider.swift:188\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":188}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a9bcf63720b1ac6e4ff4039a5eb11a3adc44cb47a16bb5fd4cd09be4bc51df6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Services/Media/OCRService.swift:148-163 | Snapzy/Services/Media/OCRService.swift:186-201 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Media/OCRService.swift:148\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCRService.swift"},"region":{"startLine":148}}}],"partialFingerprints":{"codehealthFindingId/v1":"8cc19b25cef90497be4a12c7c85bb91f12e47297d9a960894f285f389769a4cb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:732-747 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:113-128 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:732\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":732}}}],"partialFingerprints":{"codehealthFindingId/v1":"fba13356c744dd720582754720c94fa492f544ae7ec0de12e85a4ae6486c6652"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:273-288 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:423-438 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:273\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":273}}}],"partialFingerprints":{"codehealthFindingId/v1":"f143d5a91b3ce1cef2b99e0cbe746a8a69820eee09cd2ff6acc18b4e7b7ab57e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:308-323 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:64-79 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:308\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u00608\u0060 in one and \u006010\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":308}}}],"partialFingerprints":{"codehealthFindingId/v1":"32d7074091cc31d83a290b0fc16180e16a4ad500d9cb34275cd90d16658e6d4e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 4): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:716-730 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:829-843 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:955-969 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:1028-1042 \u2014 all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:716\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":716}}}],"partialFingerprints":{"codehealthFindingId/v1":"caad17e1c069cc2c98370dab8a08d1ec8d795b6757e336250e8bb85b0feb5f16"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 3): Snapzy/Services/Cloud/S3CloudProvider.swift:185-199 | Snapzy/Services/Cloud/S3CloudProvider.swift:255-269 | Snapzy/Services/Cloud/S3CloudProvider.swift:344-358 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":185}}}],"partialFingerprints":{"codehealthFindingId/v1":"e535d2927fedc1f5b9be25020ca81345be7ede5dd061f711224178f8c32b9201"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:486-500 | Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:528-542 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:486\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":486}}}],"partialFingerprints":{"codehealthFindingId/v1":"40e8c9ee261d537e554a1e54978e746136a9fb65248da4d1f342ea42f100d763"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Services/Cloud/AWSV4Signer.swift:68-84 | Snapzy/Services/Cloud/AWSV4Signer.swift:156-170 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/AWSV4Signer.swift:68\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/AWSV4Signer.swift"},"region":{"startLine":68}}}],"partialFingerprints":{"codehealthFindingId/v1":"8b37940ec64e393c75840b8500955a1196d1e4d80e8f4543eb3eb299d74e6632"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Services/Cloud/CloudKeychainStore.swift:392-406 | Snapzy/Services/Cloud/CloudManager.swift:1048-1062 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudKeychainStore.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"4ca75a8cad6faf6c77addbf564b73c1a62416baf0a8552c30d08baa7b87539c5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1446-1460 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1654-1668 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1446\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1446}}}],"partialFingerprints":{"codehealthFindingId/v1":"1b0dc745f11649f86c164427838dd70f85e215343cf75c18113881c227fb4f3e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1573-1587 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1600-1614 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1573\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1573}}}],"partialFingerprints":{"codehealthFindingId/v1":"5d8a99509685bee9b3d42835efe794983699ec3e49e31cf10a075170a4daa78e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1704-1718 | Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:277-291 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1704}}}],"partialFingerprints":{"codehealthFindingId/v1":"4d46457e4b548d31b11536696dd4188c671e028069deb0467692f854be3857b6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:774-788 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:817-831 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:774\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":774}}}],"partialFingerprints":{"codehealthFindingId/v1":"de42605b62d922f53cec41d8f4551a70e29b60718232780e9196e2f2d53efee9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:147-161 | Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:173-187 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:147\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift"},"region":{"startLine":147}}}],"partialFingerprints":{"codehealthFindingId/v1":"8cd7ecdcaabbf3aa7894887656344d4bbe78358ae7c213a8af9d1847f932852d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift:1093-1107 | Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift:1143-1157 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift:1093\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureStitcher.swift"},"region":{"startLine":1093}}}],"partialFingerprints":{"codehealthFindingId/v1":"71e8d5ff86bab4cb32e5069576c3af2e12939ba97a62ab568985508c0606ebcd"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 3): Snapzy/Features/QuickAccess/QuickAccessManager.swift:294-307 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:370-383 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:1444-1457 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":294}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae1c2d4cc71f0c0d0a56700781fce0c40919751ea990f30ad446373527d5e7e6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201314 lines \u00D7 4): scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:92-105 | scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:106-119 | scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:120-128 | scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:134-146 \u2014 all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 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 \u0060scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift:92\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/scrolling-capture-accuracy/scrolling-capture-accuracy-benchmark.swift"},"region":{"startLine":92}}}],"partialFingerprints":{"codehealthFindingId/v1":"2aa474c6decb3087d617bfb73293dd9205fa644547e2ec58064e0a4dbc2dd5a0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateManager.swift:238-251 | Snapzy/Features/Annotate/AnnotateManager.swift:263-276 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Annotate/AnnotateManager.swift:235\u0060 calls \u0060log\u0060 and \u0060Snapzy/Features/Annotate/AnnotateManager.swift:261\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateManager.swift"},"region":{"startLine":238}}}],"partialFingerprints":{"codehealthFindingId/v1":"e31a63cd113695ca9037490c38e5e9cb56da14337b9db6d3b31f7d43cf4c875a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:853-866 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2263-2276 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":853}}}],"partialFingerprints":{"codehealthFindingId/v1":"d433df430dedb8e9941021e92b27b904d67525bc555d3191dbcdc27bd766cd6c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:556-569 | Snapzy/Services/Capture/ScreenCaptureManager.swift:1099-1112 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:556\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":556}}}],"partialFingerprints":{"codehealthFindingId/v1":"10c1611e065f4de4cff11da34f29b7fb286585ad7ef81cf545e8e7fb13dcb457"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:282-295 | Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:343-356 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift"},"region":{"startLine":282}}}],"partialFingerprints":{"codehealthFindingId/v1":"d81c915437f2d8747b6270a242723bed159a2688be4fd73eb27f05beaff83bf8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Services/History/CaptureHistoryStore.swift:164-177 | Snapzy/Services/History/CaptureHistoryStore.swift:216-229 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/History/CaptureHistoryStore.swift:164\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Services/History/CaptureHistoryStore.swift:178\u0060 calls \u0060refreshRecords\u0060 and \u0060Snapzy/Services/History/CaptureHistoryStore.swift:230\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryStore.swift"},"region":{"startLine":164}}}],"partialFingerprints":{"codehealthFindingId/v1":"3c2a07a42b78f1271fed6d36544d0b5da69548edf0a6af6af8e82189281b6e68"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13\u201314 lines \u00D7 2): scripts/swift-tools/ocr/ocr-readme-benchmark.swift:193-205 | scripts/swift-tools/ocr/ocr-readme-benchmark.swift:207-220 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060scripts/swift-tools/ocr/ocr-readme-benchmark.swift:193\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/swift-tools/ocr/ocr-readme-benchmark.swift"},"region":{"startLine":193}}}],"partialFingerprints":{"codehealthFindingId/v1":"c09819b78bd75d94b3a42ed57e722da1cd47b851a6d0b23a4abf18e034b98cea"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2207-2220 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:374-387 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2207\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2207}}}],"partialFingerprints":{"codehealthFindingId/v1":"1ed6ae80d5bfe28e62b99fecd4acfda4be8776a1eb4caaf3530cd358b2f09b66"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12\u201314 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift:245-258 | Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift:276-287 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift:245\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":245}}}],"partialFingerprints":{"codehealthFindingId/v1":"0d40016ec79f3afe9709006084bbe61ed858f55fdf65e965989d53f4259e1650"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1680-1693 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1784-1797 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1680\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1680}}}],"partialFingerprints":{"codehealthFindingId/v1":"f5c3af04ae34ac53e04817edc7ef8f030150e387afa6e34f06a92f9f5306c839"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:82-95 | Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:157-170 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":82}}}],"partialFingerprints":{"codehealthFindingId/v1":"d7decf5da64ed624b1cc1896d6b86f496c202adf3910bad7465bfc638c6a4a45"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): Snapzy/Features/History/Components/HistoryFloatingContentView.swift:666-679 | Snapzy/Features/History/Components/HistoryToolbar.swift:106-119 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/History/Components/HistoryFloatingContentView.swift:666\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryFloatingContentView.swift"},"region":{"startLine":666}}}],"partialFingerprints":{"codehealthFindingId/v1":"1f2d84389c5163e40ccb611104be807e3802bcac3b21730843b265dbb5985f35"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 3): Snapzy/Features/History/Components/HistoryCardView.swift:252-264 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:242-254 | Snapzy/Features/History/Components/HistoryItemView.swift:195-207 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/History/Components/HistoryCardView.swift:266\u0060 calls \u0060relativeTimeString\u0060, \u0060localizedString\u0060, \u0060Date\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:256\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":252}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae2bcd6cf0c1f471024ff1322c0b8a372062d0b0a3fab13cf1ab664baf5fc7f5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 3): Snapzy/Features/Recording/Components/RecordingToolbarStyles.swift:58-70 | Snapzy/Features/Recording/Components/RecordingToolbarStyles.swift:76-88 | Snapzy/Features/Recording/Components/RecordingToolbarStyles.swift:123-135 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Components/RecordingToolbarStyles.swift"},"region":{"startLine":58}}}],"partialFingerprints":{"codehealthFindingId/v1":"4ca5a604f01e3e61e70dc5f79e8c3981e4eed9f8004c107e3b94db87165f9843"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/App/SnapzyApp.swift:229-241 | Snapzy/App/SnapzyApp.swift:345-357 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/App/SnapzyApp.swift:229\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060note\u0060 to \u0060String? = nil\u0060 in one and \u0060String?\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/SnapzyApp.swift"},"region":{"startLine":229}}}],"partialFingerprints":{"codehealthFindingId/v1":"bcde063bd361e2a1e841c76acdcd6ee36d5a4c138aab79b1836c09abfc3eb94e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateState.swift:135-147 | Snapzy/Features/Annotate/Models/PersistedAnnotationSessionConversion.swift:76-88 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/AnnotateState.swift:135\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":135}}}],"partialFingerprints":{"codehealthFindingId/v1":"de72be75de4d4c2ce3fc7076502197380b9ac318af1820a40903ed8a18d62aea"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1270-1282 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2680-2692 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1270\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1270}}}],"partialFingerprints":{"codehealthFindingId/v1":"3f3cc1b670dbec7f751b84881ccae4caa0ae0ed8fa7abcb8a8e4d5ce984420ba"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:247-259 | Snapzy/Services/Capture/AreaSelectionWindow.swift:1504-1516 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Capture/CaptureViewModel.swift:247\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":247}}}],"partialFingerprints":{"codehealthFindingId/v1":"e4721f2efb5c69beabf9612a4de0dc8f44c9ed42545195f0c03e80145e7a1565"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u201313 lines \u00D7 2): Snapzy/Features/Capture/CaptureViewModel.swift:2019-2026 | Snapzy/Features/Capture/CaptureViewModel.swift:2746-2758 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Capture/CaptureViewModel.swift:2019\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":2019}}}],"partialFingerprints":{"codehealthFindingId/v1":"4680b9af28de69785966861fb47eba22ef906622757d330a0a99efc2e52a95cb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12\u201313 lines \u00D7 2): Snapzy/Features/Preferences/PreferencesView.swift:184-195 | Snapzy/Features/Preferences/PreferencesWindowController.swift:69-81 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/PreferencesView.swift:184\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/PreferencesView.swift"},"region":{"startLine":184}}}],"partialFingerprints":{"codehealthFindingId/v1":"ff0beab6438b4f476527fd49b6a20967eab5c98f7edd4f39ad6dd83c21791260"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u201313 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:707-719 | Snapzy/Features/Recording/RecordingCoordinator.swift:886-893 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":707}}}],"partialFingerprints":{"codehealthFindingId/v1":"9a5b3a4006b5526a6b9d14683f5310c16be889eab9f565f97bb4dc2367f6df0c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10\u201313 lines \u00D7 2): Snapzy/Services/Capture/ScreenRecordingManager.swift:1380-1389 | Snapzy/Services/Capture/TempCaptureManager.swift:153-165 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1380\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1380}}}],"partialFingerprints":{"codehealthFindingId/v1":"5d47e6b7eae203e49b71472d88d042dd88e26c9afec7fdc3262ce4e4790d92fc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/QuickAccess/Models/QuickAccessItem.swift:138-150 | Snapzy/Services/History/CaptureHistoryRecord.swift:54-66 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Models/QuickAccessItem.swift"},"region":{"startLine":138}}}],"partialFingerprints":{"codehealthFindingId/v1":"b68f1a50784a0fe1db1bb2025db9b360962c4e5480e9d1630ea5eb049c4ba70d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1687-1699 | Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:260-272 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1687}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d189fa04f5ef1b67d3885230ac269d0ed006a1fcee18065599fa68cdb56877e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:265-277 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:127-139 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:265\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:264\u0060 calls \u0060lineLimit\u0060 and \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:126\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":265}}}],"partialFingerprints":{"codehealthFindingId/v1":"269ca991c39847f9342b9f24d562797077adcd2ebec7d12a376c61d4348c2aeb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:425-437 | Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:530-542 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:425\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":425}}}],"partialFingerprints":{"codehealthFindingId/v1":"9bbed3a9d49e1ee16a40a6f333a3b384313e334a99f9343479a05fe778a295e9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 3): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1489-1500 | Snapzy/Features/QuickAccess/Components/QuickAccessDraggableView.swift:237-248 | Snapzy/Features/VideoEditor/Models/VideoEditorSessionData.swift:47-58 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1489\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1489}}}],"partialFingerprints":{"codehealthFindingId/v1":"09070357656b7393146a7c34df945d7ca2bdb06610c2de1279ed950c54543676"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 3): Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:119-130 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:274-285 | Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:424-435 \u2014 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 \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift:119\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateBlurEffectRenderer.swift"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"f1d106ac317f2b317e86634af48daeedf6e2ce892b1cb4d97c6971125c63150e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:767-778 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2177-2188 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:767\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":767}}}],"partialFingerprints":{"codehealthFindingId/v1":"7314d4bc0bc0766ae2c4bd3f3e281d30ec0b652a1887857716f9b7a927b20859"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1257-1268 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2667-2678 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1257\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1257}}}],"partialFingerprints":{"codehealthFindingId/v1":"1fcdfcc2733fe0b850a801e028e4fcee5e7ca0e3168acdddcb5cc79cf3b94a0e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/Capture/AreaSelectionWindow.swift:4279-4290 | Snapzy/Services/Capture/AreaSelectionWindow.swift:4479-4490 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/AreaSelectionWindow.swift:4279\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Services/Capture/AreaSelectionWindow.swift:4278\u0060 calls \u0060hideSizeIndicator\u0060 and \u0060Snapzy/Services/Capture/AreaSelectionWindow.swift:4478\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":4279}}}],"partialFingerprints":{"codehealthFindingId/v1":"85f2f3321f4d0ca9ffafd4534365ce43af042de7fa33c4ea9837943f4fc242f9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:660-671 | Snapzy/Services/Capture/ScreenCaptureManager.swift:1171-1182 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:660\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":660}}}],"partialFingerprints":{"codehealthFindingId/v1":"e1cd8b8db5c8cf684bcfd54c6f656a051c9b71945264413c73ea5a40d8c3c49d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/Cloud/CloudUsageService.swift:75-86 | Snapzy/Services/Cloud/CloudUsageService.swift:137-148 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUsageService.swift"},"region":{"startLine":75}}}],"partialFingerprints":{"codehealthFindingId/v1":"9072d00e84ac5ee2070350d05cbc6c1f08dbd2d5402ad4aaeaffa9b6d800fcfa"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/History/CaptureHistoryStore.swift:213-227 | Snapzy/Services/History/CaptureHistoryStore.swift:267-278 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/History/CaptureHistoryStore.swift:213\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryStore.swift"},"region":{"startLine":213}}}],"partialFingerprints":{"codehealthFindingId/v1":"c8f87f7d98f2fd58ccffdba65be5ccca988dc662ed1eab98c96e99c65435076e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/Shortcuts/ShortcutValidationService.swift:37-48 | Snapzy/Services/Shortcuts/ShortcutValidationService.swift:152-163 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Shortcuts/ShortcutValidationService.swift:37\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/ShortcutValidationService.swift"},"region":{"startLine":37}}}],"partialFingerprints":{"codehealthFindingId/v1":"6f4f4d515249523a6f546c57736b916175fdf74d5bc1746450555678b426c5e9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:92-103 | Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift:103-114 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorBottomBar.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift:92\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":92}}}],"partialFingerprints":{"codehealthFindingId/v1":"9a5f534a92524db5756cae4523a688826ce2d3cb72dacb0c950e3a3fc9554d53"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1546-1557 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1741-1752 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1546\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1546}}}],"partialFingerprints":{"codehealthFindingId/v1":"f30c21ccc735657c5d07d700aec0039eb93b256fec6dc278d6b28b165280ffc6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:579-590 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:257-268 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:579\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":579}}}],"partialFingerprints":{"codehealthFindingId/v1":"1bc64a8efce24b0de748331730c4cf70ee3c0ff61c0f63fa8c13376ce9586d6d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:605-616 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:286-297 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:605\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060orientation\u0060 to \u0060state.aspectRatioOrientation\u0060 in one and \u0060aspectRatioOrientation\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":605}}}],"partialFingerprints":{"codehealthFindingId/v1":"13e62c70cb104f5836f4c36a1652dc58f016a8a20817562fd10306fc5f794a9a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:861-872 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:900-911 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:861\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":861}}}],"partialFingerprints":{"codehealthFindingId/v1":"a62f40aeb3dc0d0621959f655c355fa8ce95a769e2fe539209c7c1fa15d68560"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201312 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotationSessionStore.swift:299-307 | Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:388-399 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotationSessionStore.swift:299\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotationSessionStore.swift"},"region":{"startLine":299}}}],"partialFingerprints":{"codehealthFindingId/v1":"201210f53d595c998f5ca64912596af95995e1ecf7198bdcf05e4beba6e3f1b1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesMenuBarSettingsView.swift:369-380 | Snapzy/Features/Preferences/Components/PreferencesQuickAccessActionCustomizationView.swift:105-116 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesMenuBarSettingsView.swift:369\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesMenuBarSettingsView.swift"},"region":{"startLine":369}}}],"partialFingerprints":{"codehealthFindingId/v1":"4453936125cceeee4072e929b009f70eb29c170b4522b255c224e898bed30bdc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:191-202 | Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:237-248 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":191}}}],"partialFingerprints":{"codehealthFindingId/v1":"359ddc130d9145ba99968a0f351c4c6194356e43805e8b219a794176e7af0cf0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorEmptyStateView.swift:150-161 | Snapzy/Features/VideoEditor/Components/VideoEditorEmptyStateView.swift:188-199 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorEmptyStateView.swift"},"region":{"startLine":150}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f64cf168a20aaa3070b3a5c48a72e00f01cac0a72c39387df0fb4f3eeab1854"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:153-164 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:134-147 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:153\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":153}}}],"partialFingerprints":{"codehealthFindingId/v1":"169c89f80e39c3a4c87289fa83420b7e4ed98cc26f17662d44b53e653e20f204"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u201312 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorZoomCompositor.swift:372-379 | Snapzy/Features/VideoEditor/Services/VideoEditorZoomCompositor.swift:623-634 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorZoomCompositor.swift"},"region":{"startLine":372}}}],"partialFingerprints":{"codehealthFindingId/v1":"bd7d1a2295f7c6f835d854aaaae9e8f8f928405ba05f088d0c1abf6bd7783c43"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 5): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:153-163 | Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:384-394 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:204-214 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:350-360 | Snapzy/Features/Onboarding/Mockups/SnapzyMockShortcutsView.swift:74-84 \u2014 there are 5 copies across 3 file(s) \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:153\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":153}}}],"partialFingerprints":{"codehealthFindingId/v1":"589f61b3b2ad959a88693eb29f408b558621c0f167cd974a08fd1e611d7b49a0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 3): Snapzy/Services/Cloud/S3CloudProvider.swift:148-158 | Snapzy/Services/Cloud/S3CloudProvider.swift:253-263 | Snapzy/Services/Cloud/S3CloudProvider.swift:342-352 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":148}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc927f28efb064f867dbde63c56e81bf47948a6e11c195e0ae7d2e7da2b87172"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 3): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:867-877 | Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1689-1699 | Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:262-272 \u2014 there are 3 copies across 2 file(s) \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":867}}}],"partialFingerprints":{"codehealthFindingId/v1":"49e2fc494a6ae3f18a10519582023e1c639eff96f5278c892cebfd78ca8c0cde"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 3): Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:202-212 | Snapzy/Features/Onboarding/Components/OnboardingDiagnosticsOptInView.swift:61-71 | Snapzy/Features/Onboarding/Components/OnboardingSponsorView.swift:59-69 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:202\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Onboarding/Components/OnboardingSponsorView.swift:70\u0060 calls \u0060buttonStyle\u0060 and \u0060Snapzy/Features/Onboarding/Components/OnboardingDiagnosticsOptInView.swift:72\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift"},"region":{"startLine":202}}}],"partialFingerprints":{"codehealthFindingId/v1":"94ed14f7c35a4ca4752974d6f1a8227928b2abd1e08faffaa5a15629b43fe619"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 3): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:123-133 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:135-145 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:147-157 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":123}}}],"partialFingerprints":{"codehealthFindingId/v1":"273509fbc1e51fc9c35ae36dab28a483204f440597c45b76f5b46faee440f924"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/QuickAccess/QuickAccessManager.swift:1103-1113 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:1164-1175 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":1103}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a4713878cf2e63fbc4a64f50b5c9045c91adab00fa065272b211183304bfb21"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10\u201311 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:1963-1973 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1790-1799 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:1963\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":1963}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb66a325842020ac07d6fef47aaaa8d8556769cc4f3f5ba77d9b7822d5cc9154"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Services/Clipboard/ClipboardHelper.swift:68-78 | Snapzy/Services/Clipboard/ClipboardHelper.swift:110-120 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Clipboard/ClipboardHelper.swift"},"region":{"startLine":68}}}],"partialFingerprints":{"codehealthFindingId/v1":"24fb913278ec138d82945f8869e2a18c64b9ba65daabe65ec256b0d45360080f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Services/Cloud/CloudUploadHistoryStore.swift:134-144 | Snapzy/Services/History/CaptureHistoryStore.swift:671-681 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Services/Cloud/CloudUploadHistoryStore.swift:134\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUploadHistoryStore.swift"},"region":{"startLine":134}}}],"partialFingerprints":{"codehealthFindingId/v1":"26b621febd4cf2b5adf92caaa2d68f2e2f2667932091e4c39d78bd2319c20d5e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10\u201311 lines \u00D7 2): Snapzy/Services/Cloud/CloudUsageService.swift:457-467 | Snapzy/Services/Cloud/CloudUsageService.swift:491-500 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/CloudUsageService.swift:457\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUsageService.swift"},"region":{"startLine":457}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2ff5f621576bc279f719b2fe48e88eac76d9688e651ea15d7b0b3a4fac0402e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10\u201311 lines \u00D7 2): Snapzy/Services/History/CaptureHistoryStore.swift:64-73 | Snapzy/Services/History/CaptureHistoryStore.swift:78-88 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/History/CaptureHistoryStore.swift:64\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryStore.swift"},"region":{"startLine":64}}}],"partialFingerprints":{"codehealthFindingId/v1":"b73100d96ec4a1009dfa157526b963b3b5156d3f3409fd1d3a7c0e114c4c3741"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockPrerecordToolbar.swift:111-121 | Snapzy/Features/Onboarding/Mockups/SnapzyMockRecordingStatusBar.swift:98-108 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockPrerecordToolbar.swift:111\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockPrerecordToolbar.swift"},"region":{"startLine":111}}}],"partialFingerprints":{"codehealthFindingId/v1":"b8a9524394c259e3efa059c910f35a96b2c1442d4bd6b122e254a3c3645f4ca1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:890-900 | Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:974-984 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:890\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":890}}}],"partialFingerprints":{"codehealthFindingId/v1":"4440e4f1409f8259277903863bad82a7e86b2d6e72c5734aacde6618b4ce065a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift:68-78 | Snapzy/Features/Recording/Models/RecordingMicrophoneDevice.swift:61-71 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift:68\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift"},"region":{"startLine":68}}}],"partialFingerprints":{"codehealthFindingId/v1":"83852e22f3567a812c0a967061d211315c8ba6d237e8432f1d7535cfcba6c7f6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:543-553 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:514-524 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:543\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":543}}}],"partialFingerprints":{"codehealthFindingId/v1":"9e9dc788afcf4dc2219f1dcd0e940b7340bc3c6e844d0d51ad5ff117f05549f0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:297-307 | Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:353-363 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift:297\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":297}}}],"partialFingerprints":{"codehealthFindingId/v1":"e9fa10ae1b5405724c37d3627d58f0585059f29984ca0dec8ae8507b66d1c337"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201311 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:99-109 | Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:597-605 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:99\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":99}}}],"partialFingerprints":{"codehealthFindingId/v1":"d0269133097428a6bc149ccdd17c66af1f8989817233f6844ae6d0e7b3c8d139"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:515-525 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:825-835 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:515\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":515}}}],"partialFingerprints":{"codehealthFindingId/v1":"39a64004eb103a9c8679c08f129bbaa055270024abfcc3c27540cc40db1153be"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift:183-193 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift:213-223 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift:183\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassSurface.swift"},"region":{"startLine":183}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a479325e329ba4425f56cd23bc5f98f40e4b5bf35d56334c272cd7a270f297e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 5): Snapzy/Features/History/Components/HistoryCardView.swift:167-176 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:161-170 | Snapzy/Features/History/Components/HistoryToolbar.swift:122-131 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:515-524 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:909-918 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/History/Components/HistoryCardView.swift:163\u0060 calls \u0060rect\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:160\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":167}}}],"partialFingerprints":{"codehealthFindingId/v1":"adef6bb0792ac750eccd59db7a41d5d487e5a0d9b52c0cc92d6135401f3e7fad"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 4): Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:202-211 | Snapzy/Features/Onboarding/Components/OnboardingDiagnosticsOptInView.swift:61-70 | Snapzy/Features/Onboarding/Components/OnboardingSkipConfirmationView.swift:46-55 | Snapzy/Features/Onboarding/Components/OnboardingSponsorView.swift:59-68 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:202\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift:200\u0060 calls \u0060Spacer\u0060 and \u0060Snapzy/Features/Onboarding/Components/OnboardingSkipConfirmationView.swift:44\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingCompletionView.swift"},"region":{"startLine":202}}}],"partialFingerprints":{"codehealthFindingId/v1":"9c9a468d71206309264d0673311265314543c3066a84f48d47d76c1083a60318"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (4\u201310 lines \u00D7 5): Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2212-2221 | Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2236-2239 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:1644-1651 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:379-388 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:403-406 \u2014 there are 5 copies across 3 file(s) \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2212\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2212}}}],"partialFingerprints":{"codehealthFindingId/v1":"36239bf95fc8a73c30971638803b49f66091f379098911eefa9be36896e07f89"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 3): Snapzy/Services/Cloud/S3MultipartUploader.swift:162-171 | Snapzy/Services/Cloud/S3MultipartUploader.swift:239-248 | Snapzy/Services/Cloud/S3MultipartUploader.swift:265-274 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3MultipartUploader.swift"},"region":{"startLine":162}}}],"partialFingerprints":{"codehealthFindingId/v1":"bf9c89b2649ed61fc8adcb748a2b687ee914ede7b64c86d863444a7537d23cbb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 3): Snapzy/Features/History/Components/HistoryFloatingContentView.swift:347-356 | Snapzy/Features/History/Components/HistoryToolbar.swift:45-54 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:437-446 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryToolbar.swift\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/Components/HistoryFloatingContentView.swift:347\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryFloatingContentView.swift"},"region":{"startLine":347}}}],"partialFingerprints":{"codehealthFindingId/v1":"461179af580cb399a749eb78729ec24ac03d24201aeac4dcbfecb0beca25688c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201310 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateState.swift:3681-3689 | Snapzy/Features/Annotate/AnnotateState.swift:3840-3849 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3681}}}],"partialFingerprints":{"codehealthFindingId/v1":"7ccb0c0ddeadee16a7a66f11e5a9a59ededdb6e75007121f7aaa275f5dccfade"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/CrashReport/ZipArchiveWriter.swift:31-40 | Snapzy/Features/CrashReport/ZipArchiveWriter.swift:46-55 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/CrashReport/ZipArchiveWriter.swift:44\u0060 calls \u0060appendUInt32LE\u0060 and \u0060Snapzy/Features/CrashReport/ZipArchiveWriter.swift:56\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/CrashReport/ZipArchiveWriter.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"61043e2fbec8d8c6c17fcbf9be7b2bcad768d1cb9955880b7025676c0a195360"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:61-70 | Snapzy/Shared/Extensions/View\u002BCornerRadius.swift:45-54 \u2014 before extracting anything, compare \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift\u0060 and \u0060Snapzy/Shared/Extensions/View\u002BCornerRadius.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:61\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"1ae07272e24bb69af38f220902fd5e37b3ac1e549821d8f9b618aaa26800bf0b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:73-82 | Snapzy/Shared/Extensions/View\u002BCornerRadius.swift:57-66 \u2014 before extracting anything, compare \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift\u0060 and \u0060Snapzy/Shared/Extensions/View\u002BCornerRadius.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:73\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift"},"region":{"startLine":73}}}],"partialFingerprints":{"codehealthFindingId/v1":"290f442655b7e67a7425fc31d964feffe3a7f7fbb78bb7bf4cd2837f66953853"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:85-94 | Snapzy/Shared/Extensions/View\u002BCornerRadius.swift:69-78 \u2014 before extracting anything, compare \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift\u0060 and \u0060Snapzy/Shared/Extensions/View\u002BCornerRadius.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:85\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"555f9e62fc5d9515e9388ea1a75ca0c18ef2dc9e2d0de25e900bf86939311468"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateDragHandleView.swift:123-132 | Snapzy/Features/QuickAccess/Components/QuickAccessPinDragHandleView.swift:130-139 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateDragHandleView.swift"},"region":{"startLine":123}}}],"partialFingerprints":{"codehealthFindingId/v1":"62f89b85b90692779ee388d9cace3baf3da15f2595821b3599178349218e4b18"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:800-809 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:181-190 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":800}}}],"partialFingerprints":{"codehealthFindingId/v1":"a64bdf00f435f7a1b0867eca4d9fa588680b213cf8b57c326f5cbc7676dfb6f0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:161-170 | Snapzy/Features/Recording/Services/RecordingAnnotationFactory.swift:55-64 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:161\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":161}}}],"partialFingerprints":{"codehealthFindingId/v1":"c2b26916afec6d0019ee7a763532273051eec793592b6e169ad30ac5906aaa43"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:874-883 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:913-922 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:874\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":874}}}],"partialFingerprints":{"codehealthFindingId/v1":"038984b95869ced9eac865be2a4207252aabf1b73e3dc2cc06b11b9ed873e02a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Onboarding/Components/OnboardingShortcutsView.swift:509-518 | Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:1366-1375 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Onboarding/Components/OnboardingShortcutsView.swift:509\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingShortcutsView.swift"},"region":{"startLine":509}}}],"partialFingerprints":{"codehealthFindingId/v1":"c21c30faeba0a4914d777cf9f13ab3174bd131df68c1e66bcb36817ec423373d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift:113-122 | Snapzy/Features/Preferences/Components/PreferencesQuickAccessSwipeZoneView.swift:160-169 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift:113\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift"},"region":{"startLine":113}}}],"partialFingerprints":{"codehealthFindingId/v1":"48f66bcbd46429c2d7db1956db753ae3c32ee6798a64a05767987ab6b756753b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/QuickAccess/Components/QuickAccessDraggableView.swift:537-546 | Snapzy/Features/QuickAccess/Components/QuickAccessPinDragHandleView.swift:119-128 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/QuickAccess/Components/QuickAccessPinDragHandleView.swift:130\u0060 calls \u0060convert\u0060 and \u0060Snapzy/Features/QuickAccess/Components/QuickAccessDraggableView.swift:548\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessDraggableView.swift"},"region":{"startLine":537}}}],"partialFingerprints":{"codehealthFindingId/v1":"9560200f60eaf301062588087b7148420b5d3d1e5d02b0d4e854747a84d0a81a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:135-144 | Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:574-583 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":135}}}],"partialFingerprints":{"codehealthFindingId/v1":"a70f17f17f6a1ef52a699696183e4b7237449bf6ee5c5c1bc3523b13018e9c57"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 3): Snapzy/Features/QuickAccess/QuickAccessManager.swift:1103-1111 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:1164-1172 | Snapzy/Features/QuickAccess/QuickAccessManager.swift:1195-1203 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/QuickAccessManager.swift"},"region":{"startLine":1103}}}],"partialFingerprints":{"codehealthFindingId/v1":"7263305539c55027b1bdebc713ceedaa6d463b9d41d27c530d6960cee2b5e856"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 3): Snapzy/Services/Capture/ScreenRecordingManager.swift:1384-1392 | Snapzy/Services/Capture/TempCaptureManager.swift:155-169 | Snapzy/Services/Capture/TempCaptureManager.swift:435-449 \u2014 there are 3 copies across 2 file(s) \u2014 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 \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1384\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1384}}}],"partialFingerprints":{"codehealthFindingId/v1":"6b684be01cb4b1fa2320174d353280a0b94c02e239ea570e371108fa6f43d078"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 3): Snapzy/Services/Diagnostics/AppToastManager.swift:40-48 | Snapzy/Services/Diagnostics/AppToastManager.swift:50-58 | Snapzy/Services/Diagnostics/AppToastManager.swift:60-68 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Diagnostics/AppToastManager.swift"},"region":{"startLine":40}}}],"partialFingerprints":{"codehealthFindingId/v1":"3092bfb909961a01a47a0a951c07ab763e9b15a9fbf1331a0560cb43de38636a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/Recording/RecordingSession.swift:288-296 | Snapzy/Features/Recording/RecordingSession.swift:332-340 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingSession.swift"},"region":{"startLine":288}}}],"partialFingerprints":{"codehealthFindingId/v1":"5425cda412d8e29f75c843087b07a1659e7b962dd4c9877d82f95680cd5a92c4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Capture/AXElementSnapshot.swift:119-127 | Snapzy/Services/Capture/ActiveWindowResolver.swift:92-100 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AXElementSnapshot.swift"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"a34eb6ed8098e9ef94849fdcf6f1e11a4be585d1aca4fbdb246a9e4e525a9990"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Capture/AXElementSnapshot.swift:129-137 | Snapzy/Services/Capture/ActiveWindowResolver.swift:102-110 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AXElementSnapshot.swift"},"region":{"startLine":129}}}],"partialFingerprints":{"codehealthFindingId/v1":"f71e896601d5ea9422811fe7fb14789fa0ccd78321233c4a65741b43cf0430a3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u20139 lines \u00D7 2): Snapzy/Services/Capture/ActiveWindowResolver.swift:81-88 | Snapzy/Services/Capture/WindowSelectionQueryService.swift:386-394 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Capture/ActiveWindowResolver.swift:81\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ActiveWindowResolver.swift"},"region":{"startLine":81}}}],"partialFingerprints":{"codehealthFindingId/v1":"f31a4cdf8fd28ca8c6f59dc3182794013aed28c2234722a9c5e4d935af0aff23"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u20139 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:951-958 | Snapzy/Services/Capture/CaptureOutputNaming.swift:131-139 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift:951\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":951}}}],"partialFingerprints":{"codehealthFindingId/v1":"bdbf41f9b7d0ec5837d38987a3480b7b6dec5d4d627a9845312459742d6381c3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Capture/PostCaptureActionHandler.swift:266-274 | Snapzy/Services/Capture/PostCaptureActionHandler.swift:330-338 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/PostCaptureActionHandler.swift:266\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/PostCaptureActionHandler.swift"},"region":{"startLine":266}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b8dd6fd00267bd0e1d149fd42cb8e9bdeb40b0cf1835fceebba983bf8d42c7e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Capture/ScreenRecordingManager.swift:1004-1012 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1023-1033 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1004\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1035\u0060 calls \u0060deletingPathExtension\u0060 and \u0060Snapzy/Services/Capture/ScreenRecordingManager.swift:1014\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":1004}}}],"partialFingerprints":{"codehealthFindingId/v1":"ebc2f762511974aa5b138a78d9310b410d406cfa38e466c24babeb31532de053"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Cloud/CloudKeychainStore.swift:254-262 | Snapzy/Services/Security/OCRKeychainStore.swift:134-142 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Services/Cloud/CloudKeychainStore.swift:254\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudKeychainStore.swift"},"region":{"startLine":254}}}],"partialFingerprints":{"codehealthFindingId/v1":"b6c7de361a37d0cfd808fbd0ce291604abadd2477b4ca5b32caeef794b841a3a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Cloud/CloudUsageService.swift:470-478 | Snapzy/Services/Cloud/CloudUsageService.swift:506-514 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/CloudUsageService.swift:470\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUsageService.swift"},"region":{"startLine":470}}}],"partialFingerprints":{"codehealthFindingId/v1":"30bdc7e79cc66405be006fbf4b2674935890865d060ef180226c7d550e0168f7"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:319-327 | Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:411-419 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:407\u0060 calls \u0060Int64\u0060, \u0060progress\u0060, \u0060Double\u0060 and \u0060Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:317\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift"},"region":{"startLine":319}}}],"partialFingerprints":{"codehealthFindingId/v1":"75db5bf51247e9dea5e2cae00d9c8204a8f044ecb1e61c4b9cd8a9b9c4f2c714"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:126-134 | Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:545-553 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/GoogleDriveOAuthService.swift:126\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveOAuthService.swift"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a04bc6af6580976202ea4921e20e3575cef890cccdc0cfd1cce0823333ebebe"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:446-454 | Snapzy/Services/Cloud/S3MultipartUploader.swift:372-380 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":446}}}],"partialFingerprints":{"codehealthFindingId/v1":"50311ba7a75286c2b193f5fccaf71e6fee46203047a9e03bfce0b7a0ef851c83"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:202-210 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:1057-1065 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:202\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift"},"region":{"startLine":202}}}],"partialFingerprints":{"codehealthFindingId/v1":"482e3d5843bc12794d01bfb8eafcaf761466e2f8f024c5757338af2a6e9b7099"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:246-254 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:110-118 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":246}}}],"partialFingerprints":{"codehealthFindingId/v1":"e0eabf45e9e0ff54f6a58166b96c95f5aee4be14f380a3a874f59a0be8081ba0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8\u20139 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:84-91 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:111-119 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u00603\u0060 in one and \u00606\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift"},"region":{"startLine":84}}}],"partialFingerprints":{"codehealthFindingId/v1":"a2d2a00f99e2681eed136a9ebfbd495c8e971759ad2d27f4bc4eded7e7b27cc0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:270-278 | Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:288-296 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:279\u0060 calls \u0060add\u0060 and \u0060Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:298\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift"},"region":{"startLine":270}}}],"partialFingerprints":{"codehealthFindingId/v1":"7f6c2a69a484cd194f551abd2efd5b0e3d5e7ad8d469cfd914d0eb481bcf3965"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:259-267 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:228-236 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:259\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":259}}}],"partialFingerprints":{"codehealthFindingId/v1":"b79e5a252a1f0d5952794c7066d6db737014c2a1680cc7f4d42caa8e4caa5a06"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorAutoFocusEngine.swift:308-316 | Snapzy/Features/VideoEditor/Services/VideoEditorAutoFocusEngine.swift:354-362 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Services/VideoEditorAutoFocusEngine.swift:308\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorAutoFocusEngine.swift"},"region":{"startLine":308}}}],"partialFingerprints":{"codehealthFindingId/v1":"635facd1c069a0f01edad4de9366a29f6f1a5db45cbde002337de6fbad07b201"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7\u20139 lines \u00D7 2): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1477-1483 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1743-1751 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1477\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u006010\u0060 in one and \u00600\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":1477}}}],"partialFingerprints":{"codehealthFindingId/v1":"e3b21397f58d7c6b7b47e000a4890bc5c8cd496f6eb58bb3bcf9f77d1feee721"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Services/Configuration/SnapzyConfigurationShortcutsExporter.swift:46-54 | Snapzy/Services/Configuration/SnapzyConfigurationShortcutsExporter.swift:135-143 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Configuration/SnapzyConfigurationShortcutsExporter.swift:46\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationShortcutsExporter.swift"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"fa1f741edd976a52219d54b4c7d0e9b25a662c3ad74740059a2e8c7df3727e7f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7\u20138 lines \u00D7 4): Snapzy/Features/History/Managers/HistoryFloatingPanelController.swift:250-257 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:54-61 | Snapzy/Features/Recording/Components/RecordingAnnotationToolbarContentBuilder.swift:46-52 | Snapzy/Features/Recording/RecordingToolbarWindow.swift:525-531 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanelController.swift"},"region":{"startLine":250}}}],"partialFingerprints":{"codehealthFindingId/v1":"fdb36c976209dc32a70257557188f431dd217fb0bd27b545d7aff258520ca041"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 4): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1443-1450 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1570-1577 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1597-1604 | Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1651-1658 \u2014 all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1443\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1443}}}],"partialFingerprints":{"codehealthFindingId/v1":"ab06bbc12999d3a5cfc347807a5338abb97be0af150c060498ddc0fe72d546eb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 3): Snapzy/Features/History/Components/HistoryCardView.swift:243-250 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:233-240 | Snapzy/Features/History/Components/HistoryItemView.swift:186-193 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":243}}}],"partialFingerprints":{"codehealthFindingId/v1":"ca7dd2e8cf1a95f04a46404b89750425cb438f60fae9923777825dc00a08e15f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 3): Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift:71-78 | Snapzy/Features/Preferences/Components/PreferencesCloudCredentialImportSheet.swift:53-60 | Snapzy/Features/Preferences/Components/PreferencesCustomOCRModelSheet.swift:97-104 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift:71\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060alignment\u0060 to \u0060.leading\u0060 in one and \u0060.top\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Preferences/Components/PreferencesCustomOCRModelSheet.swift:105\u0060 calls \u0060fixedSize\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift:79\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudCredentialExportSheet.swift"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"5f3ab1437298eebf6be5e4ba10dfdc916b7a28bec78b3b98234d93b17668aa12"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 3): Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:409-416 | Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:448-455 | Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift:527-534 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":409}}}],"partialFingerprints":{"codehealthFindingId/v1":"f95ed4a2164d8a774532b0846049bbc97513550504ba33bf5643fe1cd542bec0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): tools/localization/CatalogTool.swift:399-406 | tools/localization/CatalogTool.swift:409-416 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/localization/CatalogTool.swift"},"region":{"startLine":399}}}],"partialFingerprints":{"codehealthFindingId/v1":"f38471ed57b73ed60bf738e92d582420ecb8d5feb8e9574310758225d45bd735"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateState.swift:776-785 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:1016-1023 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/AnnotateState.swift:776\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":776}}}],"partialFingerprints":{"codehealthFindingId/v1":"6d1135c33eb38d9d9c69a598ccaf6555416f998fa38337b189eefdae100c089a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7\u20138 lines \u00D7 2): Snapzy/Features/VideoEditor/VideoEditorState.swift:297-304 | Snapzy/Features/VideoEditor/VideoEditorState.swift:3291-3297 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/VideoEditorState.swift:3291\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":297}}}],"partialFingerprints":{"codehealthFindingId/v1":"04ee8d96ff88cdd9a91c947bcbbd77463a44f6fcd8d97b6a00e6ea5257983cc3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/VideoEditor/VideoEditorState.swift:1512-1519 | Snapzy/Features/VideoEditor/VideoEditorState.swift:1541-1548 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/VideoEditorState.swift:1512\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1512}}}],"partialFingerprints":{"codehealthFindingId/v1":"34065c651a520acfb33b70dd62cd962a731d639b201c4d2945689ad69b11dcc6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/CloudManager.swift:474-481 | Snapzy/Services/Cloud/CloudManager.swift:982-989 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/CloudManager.swift:474\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":474}}}],"partialFingerprints":{"codehealthFindingId/v1":"da2cc693b1802b1832fbc9be8ca7758799e64ae27d44c8acb50a20924f36755a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/CloudManager.swift:492-499 | Snapzy/Services/Cloud/CloudManager.swift:1000-1007 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/CloudManager.swift:492\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudManager.swift"},"region":{"startLine":492}}}],"partialFingerprints":{"codehealthFindingId/v1":"18390e1d9abccb7e918ffaa5e4ab47b1187640b7ffd7cd4854eca4de35052848"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:296-303 | Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:359-366 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:357\u0060 calls \u0060setValue\u0060 and \u0060Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift:295\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/GoogleDriveCloudProvider.swift"},"region":{"startLine":296}}}],"partialFingerprints":{"codehealthFindingId/v1":"cceb6033396812a36b3fdab57f15fb31b9ce8470f458ab27cdb9a85892577a1a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:327-334 | Snapzy/Services/Cloud/S3CloudProvider.swift:361-368 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/S3CloudProvider.swift:327\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":327}}}],"partialFingerprints":{"codehealthFindingId/v1":"03edf3024e9ca67f78ed03796721bc60ca082b80a6f20563eaa3e92014d8202b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:400-407 | Snapzy/Services/Cloud/S3MultipartUploader.swift:310-317 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Cloud/S3CloudProvider.swift:400\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":400}}}],"partialFingerprints":{"codehealthFindingId/v1":"012069b16c27995c3dac148cabae72a9b424ed2b8fcce751fbff782b49f00276"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Media/ForegroundCutoutService.swift:79-86 | Snapzy/Services/Media/ForegroundCutoutService.swift:121-128 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Media/ForegroundCutoutService.swift:79\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/ForegroundCutoutService.swift"},"region":{"startLine":79}}}],"partialFingerprints":{"codehealthFindingId/v1":"b7b2c118343364531b8f820fc034aa99ac671812a2876a332c583ca799e94fbb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Media/OCRService.swift:581-588 | Snapzy/Services/Media/QRCodeService.swift:91-98 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Media/OCRService.swift:581\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Media/OCRService.swift"},"region":{"startLine":581}}}],"partialFingerprints":{"codehealthFindingId/v1":"91d899a19c454c9e6c7842407e3bd90f500da844a69b515f76fde57e6034607b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:51-58 | Snapzy/Shared/Extensions/View\u002BCornerRadius.swift:35-42 \u2014 before extracting anything, compare \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift\u0060 and \u0060Snapzy/Shared/Extensions/View\u002BCornerRadius.swift\u0060 as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift:51\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyUnevenRoundedRectangle.swift"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"81131f27e7544ba31d325c9732474b19479f9593bd0396152a8e632e4b4982f5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:19-26 | Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:455-462 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:19\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"18097e28a48c66f670720981e85797e1c54fe55065ab5710a6fb7e65d2bf4b75"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1256-1263 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:849-856 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1256\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1256}}}],"partialFingerprints":{"codehealthFindingId/v1":"09f8a4cfebe9786f0097bc0afdfb96f42535bf410ad3e5ed199fc66c17ac498e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/Components/OnboardingVSDesignSystem.swift:169-176 | Snapzy/Features/Onboarding/Components/OnboardingVSDesignSystem.swift:205-212 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Components/OnboardingVSDesignSystem.swift:169\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingVSDesignSystem.swift"},"region":{"startLine":169}}}],"partialFingerprints":{"codehealthFindingId/v1":"d7c8debe3cf69b94b342f896ef517307092256cd9f034aa1745fc64d9be231a2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:92-99 | Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:117-124 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u00603\u0060 in one and \u00603.5\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":92}}}],"partialFingerprints":{"codehealthFindingId/v1":"2de696d8539cd02530dbe410b3a69ba81a769edf1993115ac4119943164905e3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:120-127 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:198-205 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:120\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessView.swift:196\u0060 calls \u0060foregroundStyle\u0060 and \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:119\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":120}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7b3420922f52ddffd2aaf18a38eb3f445d271afbf3aaef45e75e8e658596b1e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessCard.swift:114-121 | Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessCard.swift:159-166 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessCard.swift:114\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockQuickAccessCard.swift"},"region":{"startLine":114}}}],"partialFingerprints":{"codehealthFindingId/v1":"3894127e3360d8acb0cfe6fcb33b1a0d8286aec4b6a2ef8de955b96391b8f736"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:295-302 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:307-314 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift"},"region":{"startLine":295}}}],"partialFingerprints":{"codehealthFindingId/v1":"734ff18685abc538ac628b6e431e835edc89d4da8ccc9bbcf3bace7f1f0f32f4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesAboutFeatureCard.swift:42-49 | Snapzy/Features/Preferences/Components/PreferencesAboutLinkCard.swift:42-49 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesAboutFeatureCard.swift:42\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Preferences/Components/PreferencesAboutLinkCard.swift:51\u0060 calls \u0060buttonStyle\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesAboutFeatureCard.swift:50\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesAboutFeatureCard.swift"},"region":{"startLine":42}}}],"partialFingerprints":{"codehealthFindingId/v1":"6648478920de19086d9f2876be95ef15f2ae6a6e12f9cd0bf8d9bdd43a0332f4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift:69-76 | Snapzy/Features/Preferences/Components/PreferencesQuickAccessSwipeZoneView.swift:24-31 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift:69\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift:77\u0060 calls \u0060opacity\u0060, \u0060help\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessSwipeZoneView.swift:32\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewSlotViews.swift"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"9ce30799c2d73134988230830bf8fe941ed1e424eebcf225ee19e1c153d0f695"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:814-821 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:669-676 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:814\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":814}}}],"partialFingerprints":{"codehealthFindingId/v1":"81417bbb48fc7afb98b23c36aaeb23fd5118c69fc46e5c6d43ff1e62df39972e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:352-359 | Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:387-394 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift"},"region":{"startLine":352}}}],"partialFingerprints":{"codehealthFindingId/v1":"aeedb933cefb87e19fe65dd9376a2555e7049f3a519e8c8075345a51c6ec4393"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 3): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:176-182 | Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:315-321 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:71-77 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from all 3 call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":176}}}],"partialFingerprints":{"codehealthFindingId/v1":"eb8d4fb1a4e2c5d0417db009b5bb1edf8c366bdd8a1da4abe7baa3ebbd1a8b95"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/App/MenuBarCustomizationStore.swift:67-73 | Snapzy/Features/QuickAccess/Models/QuickAccessActionConfigurationStore.swift:82-88 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/MenuBarCustomizationStore.swift"},"region":{"startLine":67}}}],"partialFingerprints":{"codehealthFindingId/v1":"2e087ba2f33d14af176176a25167ddbcc88c0397d8626811f1b845d80a24e742"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateState.swift:3146-3152 | Snapzy/Features/Annotate/AnnotateState.swift:3162-3168 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/AnnotateState.swift:3146\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3146}}}],"partialFingerprints":{"codehealthFindingId/v1":"f0ac111b8e625bf00036781f318f65011fa632366c80c853c2c45721095d23f2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/History/HistoryWindowController.swift:59-65 | Snapzy/Features/History/Managers/HistoryFloatingPanel.swift:110-116 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/HistoryWindowController.swift\u0060 and \u0060Snapzy/Features/History/Managers/HistoryFloatingPanel.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/History/HistoryWindowController.swift:59\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/HistoryWindowController.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"cff7f97070b3500662f413eff5710cba1a485621ac3862fe0680c0733e8f2728"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Services/Capture/RecordingMetadata.swift:236-242 | Snapzy/Services/Capture/RecordingMetadata.swift:649-655 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/RecordingMetadata.swift"},"region":{"startLine":236}}}],"partialFingerprints":{"codehealthFindingId/v1":"45653bf7442bcd32b3154517351c1eb08d653020a2930b274514d73d7f965441"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Services/Capture/ScreenRecordingManager.swift:396-402 | Snapzy/Services/Capture/ScreenRecordingManager.swift:405-411 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 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 \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":396}}}],"partialFingerprints":{"codehealthFindingId/v1":"e6ed2e05ae98e8a3f38a179cbe57db645fa3a9873767cfb81bc1ba3f9da26109"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Services/History/CaptureHistoryRetentionService.swift:67-73 | Snapzy/Services/History/CaptureHistoryStore.swift:494-500 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryRetentionService.swift"},"region":{"startLine":67}}}],"partialFingerprints":{"codehealthFindingId/v1":"5166bf6bd9b87e6674dde65bef2e368f0b6e3fcf2a37298777f58e8d2749a985"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:98-108 | Snapzy/Features/Recording/Services/RecordingAnnotationFactory.swift:38-44 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift:98\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":98}}}],"partialFingerprints":{"codehealthFindingId/v1":"17f4260543b425335dbe8568e46df76c4ee78c5f4f436b5c3a0eca4a8b20e359"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateExporter.swift:56-62 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:79-85 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:56\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:63\u0060 calls \u0060play\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateExporter.swift:86\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"484aca70abe48f554d29821dec5a3c111cc40d9475058f39fa8515c5b41c8cd3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/History/Components/HistoryCardView.swift:90-96 | Snapzy/Features/History/Components/HistoryItemView.swift:36-42 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/History/Components/HistoryCardView.swift:90\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":90}}}],"partialFingerprints":{"codehealthFindingId/v1":"0ac2aacfaa747e9dc60a9cb18123517acf556db7c4b899d41c6fbd64f0d5109c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:178-184 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:78-84 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:178\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"dfd1d6a983c2df2240010f68167bba5f8f5896129ee05597df401230f8bf2a2e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:15-21 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:47-53 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:15\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"ddd41cc549f360da4a60cc5b3ed401b06edac64d77bfd29ae0862b3b2f6c6a56"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (2\u20137 lines \u00D7 5): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:55-57 | Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:64-65 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:23-24 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:55-61 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:79-85 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from all 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:55\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 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 \u0060spacing\u0060 to \u00606\u0060 in one and \u00605\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"bed912c9bcf4dbe8460813295f5311f541007310b0101226e23619ad86951fff"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesAboutSettingsView.swift:174-180 | Snapzy/Features/Preferences/Components/PreferencesUpdateChannelSection.swift:21-27 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesAboutSettingsView.swift"},"region":{"startLine":174}}}],"partialFingerprints":{"codehealthFindingId/v1":"aa76294d7f4e62e43b3942b4260ce4953ac0f9b3807479a8c29934aa3a58f0c2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:154-160 | Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:170-176 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:154\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:177\u0060 calls \u0060opacity\u0060, \u0060allowsHitTesting\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:161\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift"},"region":{"startLine":154}}}],"partialFingerprints":{"codehealthFindingId/v1":"acd829cb1195a88446c16a9145edd3f4585ec88cd45b2498d7eea71cdb90fdea"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:231-237 | Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:248-254 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:231\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:255\u0060 calls \u0060padding\u0060 and \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift:238\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessPreviewCard.swift"},"region":{"startLine":231}}}],"partialFingerprints":{"codehealthFindingId/v1":"5a39318086234f7a5e8da597ec52aa8f8c857e1d46444316dff550a5a2690df1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 4): Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:47-52 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:97-102 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:36-41 | Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:225-230 \u2014 there are 4 copies across 3 file(s) \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:47\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:224\u0060 calls \u0060background\u0060 and \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockSystemSettingsWindow.swift:35\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift"},"region":{"startLine":47}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a80308cf16f12b439676a923cdd883009d2ee15eb8d007ca5ac994203c70a2f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:53-58 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:83-88 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:117-122 \u2014 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 \u2014 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 \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:53\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:115\u0060 calls \u0060padding\u0060 and \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:82\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"a501392f77bdca92f6cd2c68ebed949c29b35d6b080d2817ad5aeedf130d2616"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:66-71 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:96-101 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:130-135 \u2014 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 \u2014 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 \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:66\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:73\u0060 calls \u0060padding\u0060 and \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:137\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift"},"region":{"startLine":66}}}],"partialFingerprints":{"codehealthFindingId/v1":"7be5302fee61adedf974b7ba06d9f63e082ee3a4b3d0293ad300719002f90b4c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:317-322 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:73-78 | Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:84-89 \u2014 there are 3 copies across 2 file(s) \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift:317\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:83\u0060 calls \u0060italic\u0060 and \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockNotesWindow.swift:72\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAreaCaptureView.swift"},"region":{"startLine":317}}}],"partialFingerprints":{"codehealthFindingId/v1":"6f1ee2e7528fa3a3893b35c2fed4b989014f8221ecfe3b9415f31ddba2f44be9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1250-1255 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2660-2665 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1250\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1250}}}],"partialFingerprints":{"codehealthFindingId/v1":"7bf4658664a196a4c9842cc8f83327f41bba4d539ee9fa63915fe5c3c4aa3e00"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Onboarding/SnapzyOnboardingState.swift:196-201 | Snapzy/Features/Onboarding/SnapzyOnboardingState.swift:292-297 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/SnapzyOnboardingState.swift:196\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/SnapzyOnboardingState.swift"},"region":{"startLine":196}}}],"partialFingerprints":{"codehealthFindingId/v1":"17dea8e661c47b0a2f57466bb6831a27c850d196988dfc47b6adad065a45a6a7"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:589-594 | Snapzy/Features/Recording/RecordingCoordinator.swift:725-730 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Recording/RecordingCoordinator.swift:589\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":589}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb4e67f18404cf8d08019cfb846451a14c53c947272b23049c20ef6abdd3124c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift:650-655 | Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift:665-670 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift:650\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":650}}}],"partialFingerprints":{"codehealthFindingId/v1":"847b1844e092919b682503935f38e5cdb8ba09cd262c68b4cd20e76e3a9b367b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (4\u20136 lines \u00D7 5): Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2229-2234 | Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2243-2246 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:1656-1659 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:396-401 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:410-413 \u2014 there are 5 copies across 3 file(s) \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2229\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:416\u0060 calls \u0060withAlphaComponent\u0060, \u0060setStroke\u0060, \u0060stroke\u0060 and \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:2249\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":2229}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f52912813f60ee7e37fdab9a37d804909952d3f3ff0f4d6323586c7cb68298e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1249-1254 | Snapzy/Features/Annotate/Services/AnnotateExporter.swift:842-847 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift:1249\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Models/AnnotateAnnotationItem.swift"},"region":{"startLine":1249}}}],"partialFingerprints":{"codehealthFindingId/v1":"77edf74f2236e18bdfceed2cff628abb986aab2cec0c16640e01c2cf7219f7ae"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/History/Components/HistoryCardView.swift:20-25 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:18-23 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":20}}}],"partialFingerprints":{"codehealthFindingId/v1":"969bf28dd1cb15c7412328d5d7429c3ba6e7641d69f18861b480d2de06003de3"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:492-497 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:454-459 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any \u0060return\u0060 inside it is the body\u0027s own exit and keeps its meaning in the moved unit."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":492}}}],"partialFingerprints":{"codehealthFindingId/v1":"a9689a5e9c51db1a91b24c8027d92bd1e42d617f0cefc16f15303ac36d65b029"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:676-681 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:578-583 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:676\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:576\u0060 calls \u0060offset\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:674\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":676}}}],"partialFingerprints":{"codehealthFindingId/v1":"d9ace64f9070878716a1d2e5f786a3f8e6cb444253e3828d781e04e813ef7ce6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift:99-104 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift:114-119 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift:99\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassButtonSurface.swift"},"region":{"startLine":99}}}],"partialFingerprints":{"codehealthFindingId/v1":"c1e75a37edfbe0851e658aa20c533a18ae803366cf92d108a06b721baea7195c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5\u20136 lines \u00D7 3): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1091-1096 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1099-1104 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1105-1109 \u2014 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 \u2014 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 \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1091\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 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 \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1090\u0060 calls \u0060frame\u0060, \u0060overlay\u0060, \u0060Text\u0060 and \u0060Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:1105\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":1091}}}],"partialFingerprints":{"codehealthFindingId/v1":"80d168c4e4e8252628549bddf23f64c4e06a690e330602ad0d961ec09854985a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:385-391 | Snapzy/Services/Capture/ScreenCaptureManager.swift:2454-2458 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1852-1856 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:385\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":385}}}],"partialFingerprints":{"codehealthFindingId/v1":"715a8705a506835b17618783573b74fe89eec68363f871edc12b801a8bf5d37c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Services/Clipboard/ClipboardHelper.swift:71-75 | Snapzy/Services/Clipboard/ClipboardHelper.swift:113-117 | Snapzy/Services/Clipboard/ClipboardHelper.swift:164-168 \u2014 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 \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Clipboard/ClipboardHelper.swift"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"4c511e9eeaba26cf2e2855064f4020bc29748ae0db256881ad6b50f25c5a125e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:59-63 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:89-93 | Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:123-127 \u2014 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 \u2014 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 \u0060Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift:59\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/SnapzyCurvedHintArrow.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"7ca7852270672a7acbd21a96d220bd94fcacdd12aad01399ad6c89b8bf2eb68c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:38-42 | Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:202-206 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:56-60 \u2014 there are 3 copies across 2 file(s) \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:38\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:37\u0060 calls \u0060background\u0060, \u0060Color\u0060 and \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:201\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"c6084f86dc87d1407a2571461d5212e43eb1b6a07ae249e35546d5527398eb51"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Features/Onboarding/Mockups/SnapzyMockDesktopCanvas.swift:36-40 | Snapzy/Features/Onboarding/Mockups/SnapzyMockDesktopCanvas.swift:45-49 | Snapzy/Features/Onboarding/Mockups/SnapzyMockDesktopCanvas.swift:54-58 \u2014 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 \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockDesktopCanvas.swift:36\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockDesktopCanvas.swift"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"6506104cc7b345f8df409145f76cfc7fba7c747b384b8f840afb4f6004f0eee1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): tools/localization/CatalogTool.swift:350-354 | tools/localization/CatalogTool.swift:383-387 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060tools/localization/CatalogTool.swift:350\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"tools/localization/CatalogTool.swift"},"region":{"startLine":350}}}],"partialFingerprints":{"codehealthFindingId/v1":"3682906b345fcefed8630ab67cd0215865054719dc3fd17620219e93e97188f6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1291-1295 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2701-2705 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1291\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1291}}}],"partialFingerprints":{"codehealthFindingId/v1":"9b2a1504f4f5c3be344400459ee1f68e36d6d5c6322c00ff21b0ad067862a8d9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:1656-1660 | Snapzy/Services/Capture/ScreenCaptureManager.swift:1671-1675 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:1656\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":1656}}}],"partialFingerprints":{"codehealthFindingId/v1":"fbbc1062bd08a5845368edeee724d59707d812b595299327e8075d28a4925e57"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Capture/ScreenCaptureManager.swift:1986-1990 | Snapzy/Services/Capture/ScreenRecordingManager.swift:1828-1833 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Services/Capture/ScreenCaptureManager.swift:1986\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":1986}}}],"partialFingerprints":{"codehealthFindingId/v1":"aaeeac694f5bcb0df743baa87affd29613798d959a97f4eb3e8c094d76f5c74f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:49-53 | Snapzy/Features/Onboarding/Mockups/SnapzyMockVideoEditorWindow.swift:73-77 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 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 \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift:49\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockAnnotateWindow.swift"},"region":{"startLine":49}}}],"partialFingerprints":{"codehealthFindingId/v1":"c527ffffb50109466c09e26ec872754eab73ed276f35a54893b37876a68984f1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:121-125 | Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:136-141 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift:121\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060spacing\u0060 to \u00603\u0060 in one and \u00606\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockFinderWindow.swift"},"region":{"startLine":121}}}],"partialFingerprints":{"codehealthFindingId/v1":"328b4f92c76af3ee3ca531fb54f3c6b4353372d3a230a24794a7cf69dde40fa7"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:53-57 | Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:207-211 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:53\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"555e04ffc79352dffebed24ff160a0ca7b20407a4cafc08bd1d3b3fa2474d00e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:162-166 | Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:283-287 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift:162\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 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\u0027 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 \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationShortcutsImporter.swift"},"region":{"startLine":162}}}],"partialFingerprints":{"codehealthFindingId/v1":"89a145fcec295ad8ce1d62eba048b1ec13e3709309cc9c29bc1d8ed31e4458e9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Annotate/AnnotateManager.swift:334-338 | Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift:373-377 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateManager.swift"},"region":{"startLine":334}}}],"partialFingerprints":{"codehealthFindingId/v1":"21c49dd3dfd55379287bde2dfb9349129e177676eca49eb4169008093ce02a6f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 3): Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:173-177 | Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:105-109 | Snapzy/Services/Capture/SmartElement/SmartElementOverlayWindow.swift:67-71 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 3 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":173}}}],"partialFingerprints":{"codehealthFindingId/v1":"d503d0b9c2371b4acc41fa85b18cd1410dcd0d18a5112b7b6126945e77e35308"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1093-1102 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2434-2443 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1093}}}],"partialFingerprints":{"codehealthFindingId/v1":"ae1490931ebb088fbd2011bc8afe1fb469cefde492588491867ae484685bb370"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1165-1176 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2506-2517 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1165}}}],"partialFingerprints":{"codehealthFindingId/v1":"09a9a945d0038ee1140da2438d477f6673346ece4f85447e3cebedcd1be24c8d"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1021-1031 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2556-2566 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1021}}}],"partialFingerprints":{"codehealthFindingId/v1":"f5f6e9351e4a43aab6ed65b453b75071009e9ac0456f85d71be0a3458de008d9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1033-1047 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2568-2582 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1033}}}],"partialFingerprints":{"codehealthFindingId/v1":"3ac0a0374051eb18f9d82a7f587536d60f6284364db44df7452d51d17fd836dd"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:1189-1201 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2599-2611 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1189}}}],"partialFingerprints":{"codehealthFindingId/v1":"f786442a753902cff9d89b517bafbaac43f5c634a46820bd7ab221196b692a0b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Capture/OCRLinkPromptManager.swift:144-150 | Snapzy/Services/Diagnostics/AppToastManager.swift:396-402 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/OCRLinkPromptManager.swift"},"region":{"startLine":144}}}],"partialFingerprints":{"codehealthFindingId/v1":"06d572e6214371ee7969eab1f70294fb7c9b7f4bd7e156bb9dd023489f08ea9f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/Recording/RecordingCoordinator.swift:275-284 | Snapzy/Services/Capture/AreaSelectionWindow.swift:1578-1587 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":275}}}],"partialFingerprints":{"codehealthFindingId/v1":"83266912df8318c38457a0b3a360ef63989246fd18731bc851bdb9e48a65c5d4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 4): Snapzy/Features/History/Managers/HistoryFloatingManager.swift:521-531 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:120-130 | Snapzy/Features/Shortcuts/ShortcutOverlayManager.swift:88-97 | Snapzy/Services/Capture/SmartElement/SmartElementCaptureController.swift:185-194 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 4 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingManager.swift"},"region":{"startLine":521}}}],"partialFingerprints":{"codehealthFindingId/v1":"ce3f6f995c25dae296106b77960669627b335900f5ca94a55f6d7840e75b316f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift:238-246 | Snapzy/Services/Capture/AreaSelectionWindow.swift:3036-3044 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":238}}}],"partialFingerprints":{"codehealthFindingId/v1":"3640d6dc96ac1b0cf3386239c9a40b1414ace6f9ec97157f009c966c22b9c06f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): Snapzy/Services/Capture/CaptureEventTapController.swift:169-180 | Snapzy/Services/Capture/SmartElementQueryService.swift:125-136 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/CaptureEventTapController.swift"},"region":{"startLine":169}}}],"partialFingerprints":{"codehealthFindingId/v1":"03e84c1de01e80ef3e63ced80513c92f0158730c4df7353ef1d456a64b7918eb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Cloud/CloudUploadHistoryStore.swift:128-132 | Snapzy/Services/History/CaptureHistoryStore.swift:665-669 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUploadHistoryStore.swift"},"region":{"startLine":128}}}],"partialFingerprints":{"codehealthFindingId/v1":"3743ad534a15d228573b3b35099f4612f52e7e4a44b185b621406282109684ca"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:420-427 | Snapzy/Services/Cloud/S3MultipartUploader.swift:346-353 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":420}}}],"partialFingerprints":{"codehealthFindingId/v1":"edbd5089132d75d5749d3b1feee9f4d64e3f79504e7dc9b719a00a32e7311573"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): Snapzy/Services/Cloud/S3CloudProvider.swift:429-439 | Snapzy/Services/Cloud/S3MultipartUploader.swift:355-365 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/S3CloudProvider.swift"},"region":{"startLine":429}}}],"partialFingerprints":{"codehealthFindingId/v1":"20be122a91310259ebc5a4b69138aefb70dfe11e8617ce35e5018f2bd79d2ac9"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Configuration/SnapzyConfigurationService.swift:29-33 | Snapzy/Services/FileAccess/SandboxFileAccessManager.swift:29-33 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationService.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"e2933ae3b2828a25381a64d9ff01d618861daa0c0365a68ae913431e2c93a430"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Shared/Components/ShortcutRecorderView.swift:162-171 | Snapzy/Shared/Components/SingleKeyRecorderView.swift:161-170 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Components/ShortcutRecorderView.swift"},"region":{"startLine":162}}}],"partialFingerprints":{"codehealthFindingId/v1":"fb17d0c0a31678dd0b78c88f22e039c7f99151485cdc1e3f3f9a61ecca00d063"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 3): Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift:1347-1357 | Snapzy/Shared/Components/ShortcutRecorderView.swift:173-183 | Snapzy/Shared/Components/SingleKeyRecorderView.swift:172-182 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 3 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":1347}}}],"partialFingerprints":{"codehealthFindingId/v1":"b1be82080d87c8fb057935f4ef8872afdae9c15d6f6173caa5f2e7ffcb43b174"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:32-39 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:29-36 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":32}}}],"partialFingerprints":{"codehealthFindingId/v1":"110e1f737d2ddac44c227db146be6a2da9ab4a6d5dc183ee6147a1cc8f146e7f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 3): Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:327-335 | Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:710-718 | Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift:89-97 \u2014 before extracting anything, compare \u0060Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSidebarComponents.swift\u0060 as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":327}}}],"partialFingerprints":{"codehealthFindingId/v1":"162f4fafaea02c5e28963021fb8c60ce6e14ea942b320c609dbca8ed948d71d8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:98-103 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:150-155 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift"},"region":{"startLine":98}}}],"partialFingerprints":{"codehealthFindingId/v1":"c65ba317a53cbb7f5d6b85b122e1c5a87dc86b67aff6b6d0c86dbda353bd99a5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/Annotate/Managers/AnnotateWindow.swift:69-77 | Snapzy/Features/VideoEditor/Managers/VideoEditorWindow.swift:26-34 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"5410cd883b05b39bfc8583b14b3ccf99705b09e11a6e6f5aee8727616328af4c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Annotate/Managers/AnnotateWindow.swift:102-108 | Snapzy/Features/VideoEditor/Managers/VideoEditorWindow.swift:64-70 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":102}}}],"partialFingerprints":{"codehealthFindingId/v1":"680cba5db49517728ef5d41a78c3b48cf977678ac2dcb49ced43b0d5b4155413"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotationSessionStore.swift:231-236 | Snapzy/Features/VideoEditor/Services/VideoEditorSessionStore.swift:428-436 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotationSessionStore.swift"},"region":{"startLine":231}}}],"partialFingerprints":{"codehealthFindingId/v1":"c4b1b6918ebffbe1a38456a07d57b4d190ebea4c52be07fbc62b488e3ce12c7a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): Snapzy/Features/History/Components/HistoryCardView.swift:231-236 | Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift:221-226 | Snapzy/Features/History/Components/HistoryItemView.swift:174-179 \u2014 before extracting anything, compare \u0060Snapzy/Features/History/Components/HistoryCardView.swift\u0060 and \u0060Snapzy/Features/History/Components/HistoryExpandedCaptureCardView.swift\u0060 as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 110 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryCardView.swift"},"region":{"startLine":231}}}],"partialFingerprints":{"codehealthFindingId/v1":"346c11e009818e0609ba61374480449944d957abb6396144017e759c064da19b"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/History/Components/HistoryFloatingContentView.swift:541-546 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:779-784 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Components/HistoryFloatingContentView.swift"},"region":{"startLine":541}}}],"partialFingerprints":{"codehealthFindingId/v1":"0dfc229ca48b4ced03b4cab97e5bcd0c4bf65380a9b205f8ac3200b0a6fa047c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/History/Managers/HistoryFloatingPanel.swift:16-24 | Snapzy/Features/Preferences/Components/PreferencesCloudUploadHistoryView.swift:149-157 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice. The matched lines also register a scope-exit action (a \u0060defer\u0060-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead \u2014 before the caller uses what it releases \u2014 so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanel.swift"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"7e44581c1b75ea8f979364bb614fb4a4bdf7af7541fae2d234ac7526ca182c75"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Onboarding/Components/OnboardingPermissionsView.swift:276-280 | Snapzy/Features/Preferences/Components/PreferencesPermissionsSettingsView.swift:266-270 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Components/OnboardingPermissionsView.swift"},"region":{"startLine":276}}}],"partialFingerprints":{"codehealthFindingId/v1":"523b70d1934938a5e486718e0df0484a46f392bf51283ec4c62893eee2b73108"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift:39-45 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassVibrancy.swift:16-22 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift"},"region":{"startLine":39}}}],"partialFingerprints":{"codehealthFindingId/v1":"83a93dbaeb778be3c32b0c417f0010325d90bf4294459819eeea98a34b2b72d1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift:47-51 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassVibrancy.swift:24-34 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/DesignSystem/SnapzyGlassSurface.swift"},"region":{"startLine":47}}}],"partialFingerprints":{"codehealthFindingId/v1":"ad97d4376482eca39e4a7341f2bfe663bb036c3b50ced4668f29c26839b6456c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Onboarding/Mockups/SnapzyMockPrerecordToolbar.swift:141-146 | Snapzy/Features/Onboarding/Mockups/SnapzyMockRecordingStatusBar.swift:124-129 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Onboarding/Mockups/SnapzyMockPrerecordToolbar.swift"},"region":{"startLine":141}}}],"partialFingerprints":{"codehealthFindingId/v1":"e981a8ee91c82f73246895b5cfff2ce5c035778e46a31961e1268466a538837c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/Recording/Components/RecordingToolbarCameraToggleButton.swift:126-133 | Snapzy/Features/Recording/Components/RecordingToolbarMicToggleButton.swift:90-97 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Components/RecordingToolbarCameraToggleButton.swift"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"0ddd26499d9de1c0f961caafa2c70cbc264a6aac32928718654a45ef9748686f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 3): Snapzy/Features/Recording/Managers/KeystrokeOverlayWindow.swift:36-44 | Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:35-43 | Snapzy/Features/Recording/Managers/RecordingAnnotationOverlayWindow.swift:69-79 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from all 3 call sites, so a change lands once. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060Snapzy/Features/Recording/Managers/KeystrokeOverlayWindow.swift:31\u0060 calls \u0060setupBadgeView\u0060 and \u0060Snapzy/Features/Recording/Managers/MouseClickHighlightWindow.swift:30\u0060 does not \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/KeystrokeOverlayWindow.swift"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"60a16534cf1c1d987aa625ea0c5a741b13131914339690a4b3b25a8013824cbb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:542-546 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:243-247 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 127 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":542}}}],"partialFingerprints":{"codehealthFindingId/v1":"6e62d538915e58cd60e64991545d8cd0f466f0644aef14ba1a695ddf5ab16c38"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:131-138 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:110-117 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":131}}}],"partialFingerprints":{"codehealthFindingId/v1":"d60258b94176891a00ff4594d425f333cdbed7a147cbe5f5c1371eb34153394a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:296-308 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:256-269 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":296}}}],"partialFingerprints":{"codehealthFindingId/v1":"f0e15af5365c534d5654e85d1d0bdc42ed717115a212452b105fa7b9da3b6345"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:732-738 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:628-634 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":732}}}],"partialFingerprints":{"codehealthFindingId/v1":"ab254deac75f54bc845e13b5f4c0fddaf9b3f99f90a629c85934c1cc56afec9a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/VideoEditor/Models/VideoEditorSpeedSegment.swift:107-115 | Snapzy/Features/VideoEditor/Models/VideoEditorZoomSegment.swift:150-158 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Models/VideoEditorSpeedSegment.swift"},"region":{"startLine":107}}}],"partialFingerprints":{"codehealthFindingId/v1":"1640e2e71612863c558e1b91eb6b4ee72a0d43e63a63f499f8fcb76ee6e5ad30"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 3): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:868-877 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2278-2287 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2289-2298 \u2014 there are 3 copies across 2 file(s) \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":868}}}],"partialFingerprints":{"codehealthFindingId/v1":"086f7f2684b654ac102a34c6a67f289b9776eb828989df9e73df95599beff876"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (13 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift:931-943 | Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift:2341-2353 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":931}}}],"partialFingerprints":{"codehealthFindingId/v1":"6d241a60477c279a35cf5b3f0a4dd7dc740e6aec04bc63540470f03ba3f7aa9c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 3): Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:433-440 | Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:442-449 | Snapzy/Features/Recording/RecordingCoordinator.swift:1274-1281 \u2014 there are 3 copies across 2 file(s) \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift"},"region":{"startLine":433}}}],"partialFingerprints":{"codehealthFindingId/v1":"f2b1aeb59bfd555a198c934aaee12bdb17b5da94ed0b240702b162cd08fe602e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/Annotate/Services/AnnotateMockupExporter.swift:82-88 | Snapzy/Services/Clipboard/ClipboardHelper.swift:363-369 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateMockupExporter.swift"},"region":{"startLine":82}}}],"partialFingerprints":{"codehealthFindingId/v1":"85bbe9858680ff288682f397b28b970dee81fcadc12fee29201c8f4751b63028"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 3): Snapzy/Features/Annotate/Services/AnnotateShortcutManager.swift:275-281 | Snapzy/Features/Annotate/Services/AnnotateShortcutManager.swift:310-316 | Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:1324-1330 \u2014 there are 3 copies across 2 file(s) \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateShortcutManager.swift"},"region":{"startLine":275}}}],"partialFingerprints":{"codehealthFindingId/v1":"d138fccd72d6ad273856db922c19f29690beffb1addf3c7cb686f74483e30637"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:91-96 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:157-162 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift"},"region":{"startLine":91}}}],"partialFingerprints":{"codehealthFindingId/v1":"cac384402eecae4eba531d6b81f35144262e7dce6d486f163dbab568e227b51e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 4): Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:105-110 | Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:124-129 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:164-169 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:171-176 \u2014 there are 4 copies across 2 file(s) \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift"},"region":{"startLine":105}}}],"partialFingerprints":{"codehealthFindingId/v1":"1a7a7c20430ac84f616e65ef8327a763e8287dec94d5e50d813581bb7959588c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 3): Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift:200-205 | Snapzy/Features/Annotate/Components/AnnotateSidebarView.swift:482-487 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoBackgroundSidebarView.swift:202-207 \u2014 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 \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 3 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarSections.swift"},"region":{"startLine":200}}}],"partialFingerprints":{"codehealthFindingId/v1":"a5405aa948cbc5167bf94d9fed352db123de6c77671ea6e30b8986bbc7e80802"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift:52-57 | Snapzy/Features/Recording/Models/RecordingMicrophoneDevice.swift:45-50 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"b77c47f57d7ca3580d0ecd6b4aec9b18116cbbd634cf968214f1f3c108c41d5a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift:140-144 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift:119-123 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomTimelineTrack.swift\u0060 as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 192 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 \u2014 extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorSpeedTimelineTrack.swift"},"region":{"startLine":140}}}],"partialFingerprints":{"codehealthFindingId/v1":"c215388cd30e76762fa10409d577efc2e1ac19b4ded5397745e08b8d7f02c6dc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorToolbarView.swift:27-36 | Snapzy/Features/VideoEditor/Components/VideoEditorVideoControlsView.swift:148-157 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorToolbarView.swift"},"region":{"startLine":27}}}],"partialFingerprints":{"codehealthFindingId/v1":"d4285d8e6235b885cbbbe2f20b327a984a04ab8098878ea42fe68968cb4e24f6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (7 lines \u00D7 2): Snapzy/Features/VideoEditor/Models/VideoEditorSpeedSegment.swift:98-104 | Snapzy/Features/VideoEditor/Models/VideoEditorZoomSegment.swift:141-147 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Models/VideoEditorSpeedSegment.swift"},"region":{"startLine":98}}}],"partialFingerprints":{"codehealthFindingId/v1":"fd4dc66f1c15fbe42c37dfa0f58d1e6e5f492ee47952b06e8cb33a9fa52ffe65"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Features/Annotate/InlineAreaMagnifierHostView.swift:159-164 | Snapzy/Services/Capture/AreaSelectionWindow.swift:3869-3874 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Features/Annotate/InlineAreaMagnifierHostView.swift:159\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. The \u0060return\u0060 at the foot of the matched lines is the enclosing body\u0027s own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that \u0060return\u0060 occupied \u2014 no decision has to be handed back and re-acted on."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaMagnifierHostView.swift"},"region":{"startLine":159}}}],"partialFingerprints":{"codehealthFindingId/v1":"3311f2111ababdbbbb9699f4bc57581a94dabaa11f6608faa1beeb7fab70b18f"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Capture/AreaSelectionMagnifier.swift:521-525 | Snapzy/Services/Capture/AreaSelectionMagnifier.swift:530-534 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/AreaSelectionMagnifier.swift:521\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":521}}}],"partialFingerprints":{"codehealthFindingId/v1":"d2ffd260fe91d0daee267545abdd70dbcebd53e9008892be1a25e4c94d4bee89"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift:69-74 | Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:155-160 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 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 \u0060Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift:69\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/CaptureOverlayShortcutSettings.swift"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7a338c1df4565232de13a1c89d07e7335fe8affc067d6e048b8ec980c185b64"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6 lines \u00D7 2): Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:174-179 | Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:307-312 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/FrozenAreaCaptureSession.swift:174\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/FrozenAreaCaptureSession.swift"},"region":{"startLine":174}}}],"partialFingerprints":{"codehealthFindingId/v1":"7053fb1feaf32651edfa9a275b5236b0e780c2b3f5a7fa481a03bed09ae1a416"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (8 lines \u00D7 2): Snapzy/Services/Cloud/DatabaseManager.swift:183-190 | Snapzy/Services/Cloud/DatabaseManager.swift:207-214 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Cloud/DatabaseManager.swift:183\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/DatabaseManager.swift"},"region":{"startLine":183}}}],"partialFingerprints":{"codehealthFindingId/v1":"83d33707bf0cfe757784ad05aa3fa7b09a46afb0cac5cbbfc231e57e58381f0c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:126-130 | Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:141-145 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"c197b10667b0cecb8c5c680ef1a1809514f03f44834e82d87421875a83f628d4"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:180-184 | Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift:388-392 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":180}}}],"partialFingerprints":{"codehealthFindingId/v1":"4b7ca21bb4d9eb71d22334bcd36ca2aae2b7c57bba8e1d6626223f591590a7a1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:687-691 | Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:719-723 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift:687\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":687}}}],"partialFingerprints":{"codehealthFindingId/v1":"c5a7cdda1ff53b66dd03bd5193a2a6f105e99ccc2e1f6272c1ffe91da5711fff"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:749-753 | Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift:788-792 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateSidebarComponents.swift"},"region":{"startLine":749}}}],"partialFingerprints":{"codehealthFindingId/v1":"862f4962a1761017a3d71e66166510431ecd3d5a8e771527d539a93012ca0805"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift:528-536 | Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift:227-235 \u2014 before extracting anything, compare \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomSettingsPopover.swift\u0060 as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 127 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 \u2014 extracting one helper per block leaves the fork in place."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":528}}}],"partialFingerprints":{"codehealthFindingId/v1":"188b5b86066a3cc07f647f851136dbc3ba00e7d94fcd31e7e0c5e8a3e87dd9a8"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift:1265-1269 | Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift:1295-1299 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift:1265\u0060 it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureCoordinator.swift"},"region":{"startLine":1265}}}],"partialFingerprints":{"codehealthFindingId/v1":"d3d9e544e255d1d3b13049f7f59fb1060ca10d465aefcee6b9855f237fc6b1f0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:49-53 | Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift:55-59 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/DesignSystem/LiquidGlass/LiquidGlassPreview.swift"},"region":{"startLine":49}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f702b6df0b75dee6e997041f04844d175733debd8276bf485b78f99fd0d2316"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (5 lines \u00D7 2): scripts/generate_dmg_background.py:328-332 | scripts/generate_dmg_background.py:337-341 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"scripts/generate_dmg_background.py"},"region":{"startLine":328}}}],"partialFingerprints":{"codehealthFindingId/v1":"81bac60112bb8a8b98d7b50ebe6dfd3096e7be84d64917a5a25bd6b318825873"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: UpdaterManager (LCOM4 9): UpdaterManager\u0027s methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable \u2014 your repository\u0027s bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Updates/UpdaterManager.swift"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"55c632f4f34bcd70648b2ffbd4e56c5bf347fcee53ae6d09d98456bef72ff9c4"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: SmartElementOverlayView (LCOM4 7): SmartElementOverlayView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/SmartElement/SmartElementOverlayView.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"b0c34da8eb2aec16b0a59216135beafe26ff9e3a5d6de9df6ffff9da602c27b6"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: AreaSelectionOverlayView (LCOM4 6): AreaSelectionOverlayView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":2732}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a15854d6548572edf9ac395891553f2333fa5d5f3135afeed0a06b8ae665b8b"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: AnnotateWindowController (LCOM4 6): AnnotateWindowController\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindowController.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"925312937cfb07694d5390b24463b5468dc87f4ca46ff1129cfe05b39a127233"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: RecordingRegionOverlayView (LCOM4 6): RecordingRegionOverlayView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":184}}}],"partialFingerprints":{"codehealthFindingId/v1":"5895fde63435f1c3f798c57712c30d9ca1a2a369c47e0eb2d43f4ccc5d7c1664"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: VideoEditorWindowController (LCOM4 6): VideoEditorWindowController\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindowController.swift"},"region":{"startLine":29}}}],"partialFingerprints":{"codehealthFindingId/v1":"042b7bbe48dd71769aa40a52a94bf582a7fbf7f7c5387c845e1d26ad20ed90aa"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: VideoEditorState (LCOM4 5): VideoEditorState\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":311}}}],"partialFingerprints":{"codehealthFindingId/v1":"f79d8bafedcd70d6d616ceea674a58becda943af128ea3932bf2622d6eb2e689"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: DesktopIconManager (LCOM4 5): DesktopIconManager\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Wallpaper/DesktopIconManager.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"caa02e3159388e58e18b796fe2953a31eaa6e2bbfa826399d14a510072d37b97"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: DragHandleNSView (LCOM4 5): DragHandleNSView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateDragHandleView.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"5d131dbc76158fc9d02b7bcf3fe8e2bee4dffe24af50bd0d7c8e7c91c07c8b4f"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: RecordingCameraPreviewView (LCOM4 5): RecordingCameraPreviewView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingCameraOverlayWindow.swift"},"region":{"startLine":566}}}],"partialFingerprints":{"codehealthFindingId/v1":"515eb6ce6919ec00ee486da5efac6642f8a5e90dd5363719581d893a2b13db6c"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: VideoEditorWindow (LCOM4 5): VideoEditorWindow\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Managers/VideoEditorWindow.swift"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"eb477d0cf7cd466df38d85b1a485ebe727be28ca47ca5feab0fa8300528fa37e"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: SplashWindow (LCOM4 4): SplashWindow\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Splash/SplashWindow.swift"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"6bf8772532a1fd09df1dbe621d7d599d9b38cfd7d59804303b3c31677e9d30be"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: ScreenCaptureManager (LCOM4 4): ScreenCaptureManager\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenCaptureManager.swift"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"a3c33ba51ff3e41f1775fbffcf0daf309b2245bdf15f694d63099a5462eee4e0"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: AppLanguageManager (LCOM4 4): AppLanguageManager\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Localization/AppLanguageManager.swift"},"region":{"startLine":33}}}],"partialFingerprints":{"codehealthFindingId/v1":"f5028d17fb33c22f0ed06fdca01a74ee5ccbeffc96da743950e55200db23cf96"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: UndoIsolatedTextView (LCOM4 4): UndoIsolatedTextView\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateTextEditOverlay.swift"},"region":{"startLine":293}}}],"partialFingerprints":{"codehealthFindingId/v1":"242bf3d8f4a20dc46e5827c2cc5e333afb80bd56b0d13e628fc0776a3cc5b145"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: AnnotateWindow (LCOM4 4): AnnotateWindow\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Managers/AnnotateWindow.swift"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"289e30f1f9c9db06b2feaad0ffba39f92e2bff17e11640b3403b441279250ce7"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: HistoryFloatingPanel (LCOM4 4): HistoryFloatingPanel\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanel.swift"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"e4a652c37381acbd086c8ffad2cd76dd34d9f6d1203f7bc71e7675cee323591d"}},{"ruleId":"D6","level":"warning","message":{"text":"Low cohesion: RecordingRegionOverlayWindow (LCOM4 4): RecordingRegionOverlayWindow\u0027s 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 \u2014 your repository\u0027s 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 \u2014 and which would otherwise dominate this list \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/Managers/RecordingRegionOverlayWindow.swift"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"804ce49fcde9cef21e03470baf55a42790695314118061f9eff6d91a2dfffdfc"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testRenderLiquidGlassComparisonSnapshots: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Shared/LiquidGlassSnapshotRenderTests.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"4b14375088c7139a2fcfc9372551eb39a33d8b8be89803174d40157aa0cc402b"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testToggleSwitchesGlassSurfaceRenderingLive: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Shared/LiquidGlassToggleRenderTests.swift"},"region":{"startLine":25}}}],"partialFingerprints":{"codehealthFindingId/v1":"b6911fb7519a8121b06f7759067901bd22275b47193a1cd7e5116db9aca1de14"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testApplyBackgroundCutoutStartsProcessingOnSupportedOS: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotateBackgroundRedactionTests.swift"},"region":{"startLine":160}}}],"partialFingerprints":{"codehealthFindingId/v1":"0b98e8607cce1cfce606f47644da636e02591af192bdc151870de7d251b74c76"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testAutoCropToContentVisionFallbackTightensAroundSoftSubject: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotateCropTests.swift"},"region":{"startLine":416}}}],"partialFingerprints":{"codehealthFindingId/v1":"1bbebc69c595669cf2a0f061ff01836c44a508a4f34f97b86cfb045d81672b1a"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testTopCenterPositionsAtTopWithPadding: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/History/HistoryPanelPositionTests.swift"},"region":{"startLine":23}}}],"partialFingerprints":{"codehealthFindingId/v1":"eea68b313813c1eb73dd7829cfe6aea3fdf9d7839745bdabc277913c220711f0"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testBottomCenterPositionsAtBottomWithPadding: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/History/HistoryPanelPositionTests.swift"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"f1672bf76584e6795ec7c33907217ef46436a0e3c7f726cd1bfe33013e25d062"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testCenterPositionsAtVerticalCenter: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/History/HistoryPanelPositionTests.swift"},"region":{"startLine":47}}}],"partialFingerprints":{"codehealthFindingId/v1":"cdb60cb9bad66afeddf5258508db4e686a61425dcb3c4aa2fd69277d2af33e17"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testCalculateOriginIgnoresPaddingForCenterCase: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/History/HistoryPanelPositionTests.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"eca815dbe75d1f54fd94bba421f46a2701bbdff8fe1c462997e54ebe5d041792"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testRenderPermissionRowStates: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Onboarding/PermissionRowSnapshotRenderTests.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"c9068769af2499be661a73c5d738582a27801362e800de268f2022856f91a96f"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testPreferenceSwitchesActionBarBetweenNativeAndFallbackRendering: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Onboarding/SnapzyOnboardingActionBarTests.swift"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"9284a98d9acf0fba7e14061d2214d25ca92543d2c63a4bfefba4ea20937bd301"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testMicrophoneAudioCapturerStartStopRealMicrophoneIntegration: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/MicrophoneAudioCapturerTests.swift"},"region":{"startLine":74}}}],"partialFingerprints":{"codehealthFindingId/v1":"b70e931ac41162745a4db1bdac471f7f03b130a235813bf226ac1a17fdd9b801"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testScreenRect_flipsAxTopLeftToAppKitBottomLeft_onPrimaryDisplay: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AXElementInspectorTests.swift"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"9e0a9e9fefe72f9c63e350cb00db50df58bd9ce7ae50d67444929e3338a6755f"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testLivePassthroughDrag_pastThreshold_overHoveredWindow_stillStartsManualSelection: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionLivePassthroughWindowDetectionTests.swift"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"4d7aa3e069cfb00f921e6e5cc2ddeeb1209d48caabdd7202505398c5798e7634"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testLivePassthroughClick_onHoveredWindow_selectsIt: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionLivePassthroughWindowDetectionTests.swift"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"8c4016814293675f351809b4c0413401170277bcebed44c41e5463d242d734c7"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testHiddenWindowSession_restore_postsSyntheticMouseMovedEvent: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionModelsTests.swift"},"region":{"startLine":79}}}],"partialFingerprints":{"codehealthFindingId/v1":"87164dfa8d81e8566b000dda8d50ded3f20900f71baccf5639d2b72dd15976cf"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testIsPresenting_falseAfterCompletion: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionModelsTests.swift"},"region":{"startLine":196}}}],"partialFingerprints":{"codehealthFindingId/v1":"52615ec16a7963dfd58d942c1c9c4ebe92d36542d39850cf6a9c64d63f0b1728"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testCompleteSelection_reentrantCancelInsideCompletion_firesOnce: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionSessionLifecycleTests.swift"},"region":{"startLine":56}}}],"partialFingerprints":{"codehealthFindingId/v1":"60d212f706f5cdd636fde84cef40dee4eb8144c4925e21459ba01d0cd3c1612b"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testScreenParameterChange_midSession_keepsWindowsVisible: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionSessionLifecycleTests.swift"},"region":{"startLine":151}}}],"partialFingerprints":{"codehealthFindingId/v1":"0e273dca0df56537b2a85ea4e057a9b82b6835c644393f3a146e35c170499cb3"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testRecreatePooledWindow_swapsPoolEntryAndPresentsReplacement: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionSessionLifecycleTests.swift"},"region":{"startLine":200}}}],"partialFingerprints":{"codehealthFindingId/v1":"75a73977864f82f2f52dfbd33a41b18e285832cbd688aef6bb5776c8cbf90918"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testQueryElement_dedupesIdenticalRect: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/SmartElementQueryServiceTests.swift"},"region":{"startLine":45}}}],"partialFingerprints":{"codehealthFindingId/v1":"9dd49d697bc738522c1171fa4cee4135dbc8ad4084af5786e5c2be1a8ea43ce4"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testCancelPendingQueries_emitsNil_andResetsDedup: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/SmartElementQueryServiceTests.swift"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"64125516cae74d250b12ad4b5307b17aebbe1c45a3f8961f385ba271927577e3"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testDebounce_collapsesRapidUpdatesIntoOneQuery: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/SmartElementQueryServiceTests.swift"},"region":{"startLine":97}}}],"partialFingerprints":{"codehealthFindingId/v1":"156189ce84d586a2f3a46662616d5482d85409069ecab7568bb1572bd9665c51"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testSuggestedConfigURLUsesAccountHomeDirectory: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Configuration/SnapzyConfigurationPathsTests.swift"},"region":{"startLine":60}}}],"partialFingerprints":{"codehealthFindingId/v1":"ff0911b4bca7b2444bf0a45a3d330e41cb2a83938f52728471bb10337f68c4b1"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testVietnameseOCR_preservesDiacriticsForShortIssuePhrase: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/OCRRecognitionTests.swift"},"region":{"startLine":43}}}],"partialFingerprints":{"codehealthFindingId/v1":"4894a6134af47fd829110374dfb470c4694ab346e82739379074314c9fe0f322"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testVietnameseOCR_preservesDiverseDiacriticsForCommonPhrases: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/OCRRecognitionTests.swift"},"region":{"startLine":59}}}],"partialFingerprints":{"codehealthFindingId/v1":"02c8e6e9a55292c6d129e6272fb321c2fb32aaf392a28ff70ee2565e33e112ce"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testVietnameseOCR_reflowsSameRowWordFragments: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/OCRRecognitionTests.swift"},"region":{"startLine":87}}}],"partialFingerprints":{"codehealthFindingId/v1":"675700626b006f3fd6597e389cc38411df4c278773d5b4289da1c9924009681d"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testOCR_recognizesReadmeSupportedLanguageSamples: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/OCRRecognitionTests.swift"},"region":{"startLine":104}}}],"partialFingerprints":{"codehealthFindingId/v1":"9c22df086678b074b9be67d07ef3b7bdcf7e3a163111d5e7dbf2e9e736d1e9dd"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testSimplifiedChineseOCR_recognizesVerticalStreetSignText: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/OCRRecognitionTests.swift"},"region":{"startLine":140}}}],"partialFingerprints":{"codehealthFindingId/v1":"755640ebdf2ba73a0b6cba94c47d8c9af470cc06a1ad9df4b87ee1e558c72427"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testDisablingShortcutFreesCarbonRegistration: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/HotkeyUnregistrationTests.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"2d5e9d4c1bb38d985a25794365b93e9de2b384fafdc86504777016956908f960"}},{"ruleId":"D10","level":"warning","message":{"text":"Skipped test: testDisabledComboCanBeReassignedToAnotherKind: Skipped \u2014 throws XCTSkip"},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/HotkeyUnregistrationTests.swift"},"region":{"startLine":100}}}],"partialFingerprints":{"codehealthFindingId/v1":"059578d511a2591b3dd5be3aecefefb7b45a3001da8e3aab2df60b6978390d05"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testThemeManager_preferredAppearanceMutation_publishesObjectWillChange: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/WindowSurfacePaletteTests.swift"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"230fda3b9a5866fdba05b4a51bef35ed0b49bb32f8b3b10257d99dd0e1458ff8"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testPrimaryAnnotationColorAppliesAcrossToolDefaults: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotateCoreTests.swift"},"region":{"startLine":2409}}}],"partialFingerprints":{"codehealthFindingId/v1":"770ca55172e2f3b304f414b6e8514be67ef56da0f48d2297361fce3b485e204c"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testPrimaryAnnotationColorPersistsAcrossAnnotateStateInstances: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotateCoreTests.swift"},"region":{"startLine":2426}}}],"partialFingerprints":{"codehealthFindingId/v1":"3770798600fa93cefde155fd41cbe5c289aedabc1820b04d36f4eb73e39fe1a8"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testRectangleMakesPositiveDragSquare: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":9}}}],"partialFingerprints":{"codehealthFindingId/v1":"3cdae7832778fa2a26caca298167a2c990d2ab1d901b1b04408966c2053433e9"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testRectanglePreservesNegativeQuadrant: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"78a5018204f084ca959fa72745ebdca9107e60d3e3f16bb75508fa8e159be902"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testRectangleVerticalDownUsesPositiveHorizontalDirection: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":21}}}],"partialFingerprints":{"codehealthFindingId/v1":"95f73af24731fe21acd4e32bf21c931abd9f5c21d50eeb45ec9f0819cb466631"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testOvalMakesSquareBounds: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":27}}}],"partialFingerprints":{"codehealthFindingId/v1":"3479a1361ef01ea7bb8c645da909d90f680e47c1a58898a66e4d5d824465a0ea"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testOvalHorizontalLeftUsesNegativeVerticalDirection: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":33}}}],"partialFingerprints":{"codehealthFindingId/v1":"ffd18d8cf8083eee84e788e09246fec41c865463322061945ab54809dd248ac3"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testFilledRectangleMakesSquareBounds: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":39}}}],"partialFingerprints":{"codehealthFindingId/v1":"768015d67450ea14eb6b49e0cd8bc845ad75e9e03418639aa09fa9780800c1c5"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testZeroLengthRectangleDragRemainsAtStart: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":45}}}],"partialFingerprints":{"codehealthFindingId/v1":"38e320c6bfe4f0f731953f699103cc02f395da6db86d4d4d50a674cae2d6adf7"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testRectangleStopsAtRightBoundaryWithoutChangingAxisDirections: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"36c6018984a3811bbec2179835366d570f369bed5207c627edbda308c1af27cb"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testFilledRectangleStopsAtLeftBoundary: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"cbbc7ddbb1feca98f94c9ff60a76ad60480386075000057b4b58d50cddd2520a"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testOvalStopsAtTopBoundary: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":73}}}],"partialFingerprints":{"codehealthFindingId/v1":"8f161db923ca26cbda382bb54972723d9c2901bf8660778aab35c601b09f9f70"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testOvalStopsAtBottomBoundary: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":84}}}],"partialFingerprints":{"codehealthFindingId/v1":"9d57f9924c9f09b74a09f5da3123123f3b52d3dcccbde5f5077a0f48042d0cb3"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testZeroLengthLineDragRemainsAtStart: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":113}}}],"partialFingerprints":{"codehealthFindingId/v1":"4802e0ec0335f347b0714935908ec28883432b65c884024eaf92762cd04127fc"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testLineTrimsDiagonalAtRightBoundary: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":119}}}],"partialFingerprints":{"codehealthFindingId/v1":"b760bb87ec840cab205ae3e147c01c6e030cfebd89c305017734812ad97673cc"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStraightArrowTrimsDiagonalAtTopBoundary: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":139}}}],"partialFingerprints":{"codehealthFindingId/v1":"c115975f3f46f27305740c04643a4e92caef5269e7349df59849ebcd95860ca4"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCurvedArrowDoesNotChange: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":151}}}],"partialFingerprints":{"codehealthFindingId/v1":"6d5adc14d7b5019c09c3c5d1322a96e9ec8a308a49597945efe52caf5fd35786"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testShiftNotHeldDoesNotChangeEndPoint: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/AnnotationDragConstraintTests.swift"},"region":{"startLine":163}}}],"partialFingerprints":{"codehealthFindingId/v1":"2619e4024898fc96c23d4563645ead996a99c28dface3252d0c8e15730b44948"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testHorizontalEdgesAreFlippedToBottomLeftOrigin: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/CropContentAnalyzerTests.swift"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"c29b7a398e264c74d074a49f767a7daef367f8d01bc931c6f65d4ebae0c9a3ec"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testRetinaPointMappingHalvesEdgePositions: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/CropContentAnalyzerTests.swift"},"region":{"startLine":100}}}],"partialFingerprints":{"codehealthFindingId/v1":"a1a09bf1e87bfecae628453c13af18db02c80e022dbeb102799e0841bc0ab8cc"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testDownscaledAnalysisKeepsBorderPositions: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Annotate/CropContentAnalyzerTests.swift"},"region":{"startLine":107}}}],"partialFingerprints":{"codehealthFindingId/v1":"01b958a6335144051f514b48178405dea68c6023204fc719d88017dcfbccd18b"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStartStopCleanupTimer_noCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/RecordingAnnotationStateTests.swift"},"region":{"startLine":97}}}],"partialFingerprints":{"codehealthFindingId/v1":"d005e76e78448549df09775030d429fbc1156f0c38f7fc675167f18a17dbb06e"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testSetOnFirstVideoFrame_doesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/RecordingSessionTests.swift"},"region":{"startLine":57}}}],"partialFingerprints":{"codehealthFindingId/v1":"72146d82242bcdb8981151e9d1ecf27726ff75118570d30937f3a386653bfeb2"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testConfigureExpectedVideoDimensions_doesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/RecordingSessionTests.swift"},"region":{"startLine":63}}}],"partialFingerprints":{"codehealthFindingId/v1":"5f957cb6aff182abf99301ff3a05f48942fae3b01498612d792f9ec8bad9edf7"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testSetAccumulatedPauseOffset_doesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/RecordingSessionTests.swift"},"region":{"startLine":67}}}],"partialFingerprints":{"codehealthFindingId/v1":"46e9178e78063c2e128f5af18a5f812ec807a6b8e06c7b9fb558bbb4eac3efdb"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testReset_clearsPauseOffset: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/Recording/RecordingSessionTests.swift"},"region":{"startLine":72}}}],"partialFingerprints":{"codehealthFindingId/v1":"927a2ccf30f37e7c7c77107db977a61244658f46a6730c8a21f8c34ac2622257"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testVideoURL: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/VideoEditor/VideoEditorWindowInputTests.swift"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"9e8dd0efa302e399a14be9fb5dcd7e46db09a63a7a1242ef9d11dd1b4998772c"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCalculateCropRect_flipsYAndClampsToFrameBounds: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/VideoEditor/VideoEditorZoomAndAutoFocusTests.swift"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"0742f9cc593ae6026d9de535c21c86913ed39483a22c534abf1dadee2bf263df"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCalculateTransform_offsetsFromNormalizedCenter: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/VideoEditor/VideoEditorZoomAndAutoFocusTests.swift"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"eba8aa57c24697c4c078b992c8da555dc282a813bdadc95e9c16969936e5a804"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testAutoFocusCameraState_usesPathCenterAfterTransition: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Features/VideoEditor/VideoEditorZoomAndAutoFocusTests.swift"},"region":{"startLine":175}}}],"partialFingerprints":{"codehealthFindingId/v1":"57e3393aad81addc2645b06fbca2ad0b203fe81ebae2683e9850819b734d4ef3"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testHoverTickCost_livePassthroughPath: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionHoverPerformanceTests.swift"},"region":{"startLine":70}}}],"partialFingerprints":{"codehealthFindingId/v1":"bc313765e6d9a626e4eaf62f3f1cc8ca95d0f7bc9de951d197f57b70265637bc"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testDragTickCost_multiDisplayFanOut: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionHoverPerformanceTests.swift"},"region":{"startLine":95}}}],"partialFingerprints":{"codehealthFindingId/v1":"26621152ae57b15133e39fb0ab25a20b861d9eca46eb9873ff5c1ad7313d7ea8"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testWindowServerOnScreenWindowListQueryCost: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/AreaSelectionHoverPerformanceTests.swift"},"region":{"startLine":121}}}],"partialFingerprints":{"codehealthFindingId/v1":"ac7e037bd36315fbf6696551cb78d75d59de8399a218c776b185a1b7a068b7b6"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStartStop_lifecycleDoesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/MouseClickHighlightServiceTests.swift"},"region":{"startLine":28}}}],"partialFingerprints":{"codehealthFindingId/v1":"bf59f3a44448733d72c6ef694f557402c3f162bffe37b26428991bbcebb16e48"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStart_whenAlreadyRunning_noOp: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/MouseClickHighlightServiceTests.swift"},"region":{"startLine":33}}}],"partialFingerprints":{"codehealthFindingId/v1":"034a57c4fbe6918c86dd21eecf600c8ed15c69a77d2ce44b8a4c2533fca5d83f"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testUpdateRecordingRect_doesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/MouseClickHighlightServiceTests.swift"},"region":{"startLine":40}}}],"partialFingerprints":{"codehealthFindingId/v1":"4258d12b6952d0ac37cb2aa66dab7eca9d6fa3975f0931d955f8e19da600f7a5"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStop_whenNotRunning_noOp: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/MouseClickHighlightServiceTests.swift"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"b526273404f04553de8c0b46f82e2c60a3074221b58c13b09983ec7a127a28aa"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStart_createsTimer: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingMetadataCleanupSchedulerTests.swift"},"region":{"startLine":27}}}],"partialFingerprints":{"codehealthFindingId/v1":"90de1750f79e8b2d4aab30ce3ea3dd0c4022d7cfb6a83730b13d173f31e2c099"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStop_invalidatesTimer: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingMetadataCleanupSchedulerTests.swift"},"region":{"startLine":32}}}],"partialFingerprints":{"codehealthFindingId/v1":"5c067ae6f3abe92596442da966f5b2b848d5ebe3697f60cd2d3c2e0567cddd93"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStartStopLifecycle: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingMetadataCleanupSchedulerTests.swift"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"996e95e9447a8aafc265aa081d7c9ce2a74acf0dd91a156846d980f6940c4a0b"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testNative_returnsOddInputUnchangedAtEveryFPS: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"ff9d02ef0d00c05c671799f862be2296103a634c50836ddab35f3a48f3f63233"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testInsideBox_returnsOddInputUnchanged: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"adb8b64afc186d28d8b8905ca824b540389626b6a1a4715b6c44a9af440d643f"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testAuto_keepsMoreSpaceMacBookProUnchangedAt60FPS: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec622a463b40efb6643a017ce15e8e6ea828524a9c5c8de699ae75a1ed415216"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testAuto_keepsDefault16InchMacBookProUnchangedAt60FPS: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"6276550392c31512aba15352739102319e5c7a285362cd7b797e463959380b18"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testAuto_clamps5120By2880At60FPS: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":39}}}],"partialFingerprints":{"codehealthFindingId/v1":"82baacc0de125dc5edf86b40006db27d8e25a8734b5485af600189713a1cf83c"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testAuto_clampsPortraitByTransposing4KBox: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":43}}}],"partialFingerprints":{"codehealthFindingId/v1":"f1c6144c50a7cf8c59ab8da2138b6f2ac3145b295bb0fc4adb6422ee388880b9"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: test4K_5120By2880At60FPS: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"d41158ed836d106ac7a77af799f501a140eeca60f02f30c8caf9d0ba49292a53"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: test4K_16By10Regression: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":57}}}],"partialFingerprints":{"codehealthFindingId/v1":"249d7887cc10e2338221b177943e71771016392fcc444614abd00884912a0020"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: test4K_MacBookMoreSpace: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"565ed17f444f05fea45b1d82b0f5beb89c6b30159e9b47bf943f3464112b336d"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: test4K_portraitTransposesBox: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":65}}}],"partialFingerprints":{"codehealthFindingId/v1":"5d4aa585d4012d51e3520e37f41b42705ec6b0fd5541b1a4d4df73118d66d5c2"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: test4K_squareInput: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":69}}}],"partialFingerprints":{"codehealthFindingId/v1":"9dcedf2a0336b6bf403f92a6c9b4cafca7bd0596dbe68688863e76c4b4068420"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testDoesNotUpscale: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/RecordingVideoCompatibilityLimiterTests.swift"},"region":{"startLine":78}}}],"partialFingerprints":{"codehealthFindingId/v1":"1c7c2bd0e86ce2d4f4b27a31c8ad2e99e3275c466f0183e7ea6dba0d6bb366cc"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCanToggleAutoScrollOnlyAfterFirstFrameLocks: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/ScrollingCaptureWindowSharingTests.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"158541abb73ff5b4ca37c54d0de9dd3322944b60d167a382f26ee47d62a07b8b"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testTimeout_afterSuccessfulFinish_doesNotResumeAgain: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/SingleFrameStreamCaptureSessionTests.swift"},"region":{"startLine":111}}}],"partialFingerprints":{"codehealthFindingId/v1":"84cf7ed1e747b96f39aa87c4a7509bc057d14df78b4a9bfa10effd643014159b"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testDeleteTempFile_nonexistentFile_doesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Capture/TempCaptureManagerTests.swift"},"region":{"startLine":172}}}],"partialFingerprints":{"codehealthFindingId/v1":"ca7ee6db5a7f20e936bce05ac90a5dfa0e9d7a771b9cbf98ebcdbb5d5c060fec"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCopyFileURLs_emptyArray_noOp: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Clipboard/ClipboardHelperTests.swift"},"region":{"startLine":31}}}],"partialFingerprints":{"codehealthFindingId/v1":"ceccb3b16e0d20b0fb0518108ee3dc64f8e6723fd53fdf847c1f6eda7d96484a"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testCopyImageFromURL_missingFile_logsAndReturns: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Clipboard/ClipboardHelperTests.swift"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"bff3d3d7a3529fb92706457102860030ddef9109d92795319601939806856a14"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testSweep_skipsWhenHistoryDisabled: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/History/CaptureHistoryRetentionServiceTests.swift"},"region":{"startLine":67}}}],"partialFingerprints":{"codehealthFindingId/v1":"c7ac5ae6375eb50b53225750ba817cff7d8cda5ca4527619fbd9fb6242ee0b5d"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testStartStop_lifecycleDoesNotCrash: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/History/CaptureHistoryRetentionServiceTests.swift"},"region":{"startLine":195}}}],"partialFingerprints":{"codehealthFindingId/v1":"f6f22ff63a2f09c9708f8694cf17001ac7700dab67387835fb79259743922b86"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testUnauthorizedMapsToTypedError: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/RemoteOCRServiceTests.swift"},"region":{"startLine":173}}}],"partialFingerprints":{"codehealthFindingId/v1":"56b7028611175527591bf53eabf22701d8403c0fe6246d3b1bfc4fc7d5c3c303"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testHTTPErrorIncludesStatusAndBodySnippet: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/RemoteOCRServiceTests.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"b4c2c87994637b9ef1f0e73077d116f8046abc43e839b0b00d1a958f64187533"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testEmptyContentThrowsInvalidResponse: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/RemoteOCRServiceTests.swift"},"region":{"startLine":242}}}],"partialFingerprints":{"codehealthFindingId/v1":"6b9a5642894d60225eb354d99153e212c4e3569d5d6664714d2b1cdb362a1459"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testMalformedJSONThrowsInvalidResponse: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Media/RemoteOCRServiceTests.swift"},"region":{"startLine":247}}}],"partialFingerprints":{"codehealthFindingId/v1":"5f5f9cf6558774a08bb5b6e4ae11722d3ecdb2b3779d3f131e4e0d33e657d397"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testSessionShortcut_registersOnlyWhileRecordingSessionActive: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutGatingTests.swift"},"region":{"startLine":241}}}],"partialFingerprints":{"codehealthFindingId/v1":"f1f16dce5dd2384af8a55ac9c15244e083cc08b55118977296064e7ed5b35ad8"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testNonSessionShortcut_staysRegisteredRegardlessOfSessionState: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutGatingTests.swift"},"region":{"startLine":273}}}],"partialFingerprints":{"codehealthFindingId/v1":"ad0b8fe6bf68eab0418f9f1137702d28354d7f582e3587f16024897c63f723a6"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testDisabledSessionShortcut_staysUnregisteredWhileSessionActive: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutGatingTests.swift"},"region":{"startLine":298}}}],"partialFingerprints":{"codehealthFindingId/v1":"cc6e40c2d559d15ad9478e004f8d86e6cf3020208f377eb83fc8826eaf2c0117"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testZeroModifierSessionShortcut_staysUnregisteredWhileSessionActive: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutGatingTests.swift"},"region":{"startLine":316}}}],"partialFingerprints":{"codehealthFindingId/v1":"3f7b967398a89fb35693556819a60762260a6e62d8ed8f8089bbac0f7aea48d7"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testClearedSessionShortcut_staysUnregisteredWhileSessionActive: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutGatingTests.swift"},"region":{"startLine":334}}}],"partialFingerprints":{"codehealthFindingId/v1":"94dade65cda777cb8f38efad04da991116f1987c5f7a415b30cbbe45fe5cac4f"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testTogglePenShortcut_releasedWhenRecordingSessionEnds: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutObservationTests.swift"},"region":{"startLine":120}}}],"partialFingerprints":{"codehealthFindingId/v1":"84170cf0dea6aec8bb1dad457bee013a2ac367cc1d7eb0f7ca3e939bdce7993f"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testTogglePenShortcut_staysRegisteredWhilePaused: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutObservationTests.swift"},"region":{"startLine":142}}}],"partialFingerprints":{"codehealthFindingId/v1":"0aedac9897fd48edccdb5ebbebd35b9a41f534311b0e1fc4fbb3e34d7e40daf7"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testPauseResumeShortcut_becomesRegisteredWhenRecordingSessionStarts: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutObservationTests.swift"},"region":{"startLine":163}}}],"partialFingerprints":{"codehealthFindingId/v1":"5b0ac09f3817517d09981bc2ba83a3a9009de252b93181108eb03a6dd3e615d5"}},{"ruleId":"D10","level":"warning","message":{"text":"No assertions: testTogglePenShortcut_releasedWhenPrepareFailsBackToIdle: This method\u0027s 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* \u2014 so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as \u0027no assertion this check knows how to see\u0027, and if that is right, add one."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"SnapzyTests/Services/Shortcuts/RecordingSessionShortcutObservationTests.swift"},"region":{"startLine":194}}}],"partialFingerprints":{"codehealthFindingId/v1":"c747f0c3adc3e044517e4ba446cbb1203892d6ec55da57f9420706ba19ef8b1b"}},{"ruleId":"D13","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"ca1f8b8a74945fb6997d593c942a4279c8a762449afa3e33ed1dde1d056b4c62"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D13","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"2f61a3d648daa91d03b3055615b584aaedd1d309e37852f8ef716726fb827a69"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift: Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in DrawingCanvasNSView.mouseUp at line 1313. 8 of those changes were fix/bug commits, and the other 15 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift"},"region":{"startLine":1313}}}],"partialFingerprints":{"codehealthFindingId/v1":"84551a925613f688ccb89f964d0132c6aa8c0a995349b175167cd2abfb36716b"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Capture/AreaSelectionWindow.swift: Snapzy/Services/Capture/AreaSelectionWindow.swift changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AreaSelectionController.startSelectionSession at line 553. 21 of those changes were fix/bug commits, and the other 24 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Capture/AreaSelectionWindow.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionWindow.swift"},"region":{"startLine":553}}}],"partialFingerprints":{"codehealthFindingId/v1":"4435627d7988f3bf9d26e697ef38eaf92991a83730c2eb6c22dfad9f88d29edc"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Capture/CaptureViewModel.swift: Snapzy/Features/Capture/CaptureViewModel.swift changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ScreenCaptureViewModel.shortcutTriggered at line 349. 8 of those changes were fix/bug commits, and the other 18 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Capture/CaptureViewModel.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Capture/CaptureViewModel.swift"},"region":{"startLine":349}}}],"partialFingerprints":{"codehealthFindingId/v1":"87f0a44a97d3a0414ee35c12af8da4e7af7c1ec5e2ac4a252dddc1a8f54c9308"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/AnnotateState.swift: Snapzy/Features/Annotate/AnnotateState.swift changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in AnnotateState.updateAnnotationProperties at line 3679. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/AnnotateState.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/AnnotateState.swift"},"region":{"startLine":3679}}}],"partialFingerprints":{"codehealthFindingId/v1":"1ac3daa232d8b498f85a8b3c02b0d504af37568e090c0787028812856a62d916"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift: Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in CaptureSettingsView.body at line 117. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCaptureSettingsView.swift"},"region":{"startLine":117}}}],"partialFingerprints":{"codehealthFindingId/v1":"86023f95621c80e7971a7114ce2a35ae8eb8ce53945d1dc78f5aa0596023063a"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift: Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in SnapzyConfigurationDefaultDocument.globalShortcut at line 273. 1 of those changes was a fix/bug commit, and the other 14 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift"},"region":{"startLine":273}}}],"partialFingerprints":{"codehealthFindingId/v1":"47a47707d902ca8ddf548ca321d9569dea641f56ea7e61f9927afb5f0da92b38"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift: Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in InlineAreaAnnotateRootView.body at line 234. 5 of those changes were fix/bug commits, and the other 9 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/InlineAreaAnnotateWindow.swift"},"region":{"startLine":234}}}],"partialFingerprints":{"codehealthFindingId/v1":"7224f9b09f6eefe88fbf2054be6697c38834a1da580f0bad186cd7cbb72bda39"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift: Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in SnapzyConfigurationImporter.collectQuickAccess at line 344. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift"},"region":{"startLine":344}}}],"partialFingerprints":{"codehealthFindingId/v1":"ec05af9a937881d5a162356cf62cdba56db1450c55910edb0fdba6644a8d04fd"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift: Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in AnnotateQuickPropertiesBar.activePropertiesContent at line 178. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":178}}}],"partialFingerprints":{"codehealthFindingId/v1":"9363b2aa5cdaa0f6860f7e410a75bc10abaef546e08d98ee42d6615e1ff1d918"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift: Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ShortcutsSettingsView.handleGlobalShortcutChange at line 1058. 1 of those changes was a fix/bug commit, and the other 9 changed it for other reasons \u2014 this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one \u2014 a file this often edited pays the complexity back every time. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift"},"region":{"startLine":1058}}}],"partialFingerprints":{"codehealthFindingId/v1":"dcbae22a6d58acdf9d1774b8c995f31fed47256894e6eea9e5348e353f364913"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift: Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AnnotateCanvasView.body 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-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateCanvasView.swift"},"region":{"startLine":88}}}],"partialFingerprints":{"codehealthFindingId/v1":"a62c2ac9956eee9288a2e2d5a8fa62912abcf60afac7f6316b2dec2ca6220152"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift: Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in KeyboardShortcutManager.loadShortcuts at line 1201. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Shortcuts/KeyboardShortcutManager.swift"},"region":{"startLine":1201}}}],"partialFingerprints":{"codehealthFindingId/v1":"adf42952df2fec94662e1a29edb72120dc252cc988561ae2a5a3037874e284b6"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift: Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AnnotationRenderer.drawCurrentStroke at line 128. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift"},"region":{"startLine":128}}}],"partialFingerprints":{"codehealthFindingId/v1":"c4313463c0d3fc768d6e127d3357b9c0431c150702c264388dba7df120ba9820"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/App/AppStatusBarController.swift: Snapzy/App/AppStatusBarController.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in AppStatusBarController.makeMenuItem at line 511. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/App/AppStatusBarController.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/AppStatusBarController.swift"},"region":{"startLine":511}}}],"partialFingerprints":{"codehealthFindingId/v1":"1a73b088dd92c15ff661212a72df5a55e3a027adc3548d1008284abcc68d550f"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Capture/ScreenRecordingManager.swift: Snapzy/Services/Capture/ScreenRecordingManager.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ScreenRecordingManager.prepareRecording at line 790. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Capture/ScreenRecordingManager.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScreenRecordingManager.swift"},"region":{"startLine":790}}}],"partialFingerprints":{"codehealthFindingId/v1":"48179e525f577e92f29e3137317ad6fbf68c351cfcbce043bb28684bc68e92d2"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift: Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in QuickAccessCardView.body at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"3d47107e2c0f596e5aaca1e623d9432216315af43b4ed07abe3735b62093cfe5"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Services/AnnotateExporter.swift: Snapzy/Features/Annotate/Services/AnnotateExporter.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in AnnotateExporter.renderFlatFinalImage at line 403. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Services/AnnotateExporter.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateExporter.swift"},"region":{"startLine":403}}}],"partialFingerprints":{"codehealthFindingId/v1":"fa0520dd30a72c09d99dec49cc81744b0961ae48c135b2e95fb37ac7845f6428"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Configuration/SnapzyConfigurationShortcutCodec.swift: Snapzy/Services/Configuration/SnapzyConfigurationShortcutCodec.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in SnapzyConfigurationShortcutCodec.keyCode at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Configuration/SnapzyConfigurationShortcutCodec.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationShortcutCodec.swift"},"region":{"startLine":57}}}],"partialFingerprints":{"codehealthFindingId/v1":"3e108d0409a93b5322b78f5f8fd7331b85da7cbc52e3f01acd7cedc86b8502ad"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/App/SnapzyDeepLinkHandler.swift: Snapzy/App/SnapzyDeepLinkHandler.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in SnapzyDeepLinkHandler.handle at line 19. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/App/SnapzyDeepLinkHandler.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/App/SnapzyDeepLinkHandler.swift"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"97fe5bff03ca6b786bb146e3554e71ce25dd47ba5408c0dac5b6692f588d3113"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift: Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in AnnotationFactory.createAnnotation at line 53. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":53}}}],"partialFingerprints":{"codehealthFindingId/v1":"03721cfa84b9650b966852422ea34ff1d437f017b142aca6409bde7bbcf5fc46"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Capture/AreaSelectionMagnifier.swift: Snapzy/Services/Capture/AreaSelectionMagnifier.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in AreaSelectionMagnifier.update at line 340. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Capture/AreaSelectionMagnifier.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/AreaSelectionMagnifier.swift"},"region":{"startLine":340}}}],"partialFingerprints":{"codehealthFindingId/v1":"361b6f5dabb961bca963e956ce65da037deb04734a0fa313eca267066a84cdbe"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift: Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AnnotateBottomBarView.annotateActionButtons at line 392. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateBottomBarView.swift"},"region":{"startLine":392}}}],"partialFingerprints":{"codehealthFindingId/v1":"d7bfaac9007c1fd7c016dc2d7a3f5a414d1816b68d1e5d60bdcfb7f1043ee5a2"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/VideoEditor/VideoEditorState.swift: Snapzy/Features/VideoEditor/VideoEditorState.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in VideoEditorState.undo at line 1941. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/VideoEditor/VideoEditorState.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/VideoEditorState.swift"},"region":{"startLine":1941}}}],"partialFingerprints":{"codehealthFindingId/v1":"5c67f0b04800e3399d4e4d48b248b3bed216925a7d2d6f1fa6b65019c4269107"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift: Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in VideoEditorExporter.exportWithZooms at line 206. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift"},"region":{"startLine":206}}}],"partialFingerprints":{"codehealthFindingId/v1":"87c71ac2f45b1ee49062e3515e655e20fc3c03ed19b8f8f0b37414e7b6539be7"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift: Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in CloudCredentialFormView.body at line 816. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesCloudSettingsView.swift"},"region":{"startLine":816}}}],"partialFingerprints":{"codehealthFindingId/v1":"00b03b8ff83d4d6a96fed96158bf352fe72c2665091b41818c71a8f4dc864d63"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Capture/WindowSelectionQueryService.swift: Snapzy/Services/Capture/WindowSelectionQueryService.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in WindowSelectionQueryService.prepareSnapshot at line 52. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Capture/WindowSelectionQueryService.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/WindowSelectionQueryService.swift"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"f104e92bbc88a490e9f80d6d0f6cadd467ff5c6f7dc7b4270b8ea38798b97b28"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Features/History/Managers/HistoryFloatingPanel.swift: Snapzy/Features/History/Managers/HistoryFloatingPanel.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in HistoryFloatingPanel.performKeyEquivalent at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Features/History/Managers/HistoryFloatingPanel.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/History/Managers/HistoryFloatingPanel.swift"},"region":{"startLine":61}}}],"partialFingerprints":{"codehealthFindingId/v1":"96d8c2d8f03bf65ced4cd21d63975909b4f1ed6e92cc9724e1c3bd11241e0515"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureFrameSource.swift: Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureFrameSource.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ScrollingCaptureFrameSource.stream at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-30..2026-09-28, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272026-06-30 14:52:40 \u002B00:00\u0027 --until=\u00272026-09-28 14:52:40 \u002B00:00\u0027 --full-history --no-merges -- Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureFrameSource.swift\u0060: 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 \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Capture/ScrollingCapture/ScrollingCaptureFrameSource.swift"},"region":{"startLine":92}}}],"partialFingerprints":{"codehealthFindingId/v1":"abeb43d199055b961cbb07aeaa03ae164a56e69fd17c68ad163af790e07886d7"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no architecture or design documentation: The README for development tools (xcodebuild, build_and_run.sh) describes no architecture or design rationale; only a Prerequisites list and local-debugging steps are present. Add an Architecture section explaining the dual-path Ruru composite model that powers Liquid Glass, so readers can understand why this tooling exists."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"docs/DEVELOPMENT.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"fd3393d995626e4731cb097cc62398e394980f692120c705aa0c2d704dc5f303"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no architecture or design documentation: The recording runtime path is described but no architecture or media-pipeline diagram accompanies it. Add a short architecture sketch (or link to) the ScreenRecordingManager pipeline, showing trigger, pre-record toolbar, and output stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"docs/RECORDING.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"80d67c67961f5019eb13288ddc271bdb64a5318bd590f10978bdf89cc336716c"}},{"ruleId":"D20","level":"note","message":{"text":"No ADRs found: No ADRs found. No recognised ADR directory (\u0060docs/adr/\u0060, \u0060docs/decisions/\u0060, \u0060adr/\u0060, \u0060docs/rfcs/\u0060, an \u0060ADR0001/\u0060 folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (\u0060docs/adr/use-postgres.md\u0060, \u0060docs/adr/2024/0001-x.md\u0060); or a file anywhere whose name is ADR-shaped (\u00600001-use-postgres.md\u0060, \u0060adr-012-caching.md\u0060); or, when neither turned anything up, a document carrying the decision-record signature (an \u0022Architecture Decision Record\u0022 heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these \u2014 unnumbered files outside any recognised directory, without those headings \u2014 is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in \u0060docs/adr/\u0060."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"d2bea044ff79d7d275f5a91a6e2f548586178eaf480274c33960ad020c854631"}},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"613343d1b752f35745826fe8d15b453cf20383607c0f92f58d6658c1e8f77558"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"0e7bbf6d58d90cf992a92b7992dbc53cd3428c139b35e16035ce1a663cc60295"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"bc17439367157c6f6ff8590f4dfe29bc3a0ce4e328d99df310f8a49a2877af10"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"fab6e8a5725d1609542cf6c557c7692d54f6b2566c12193f496c202cfc492385"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"ba5dde7a3b9303f71db94ea8bb328a682ed46d3dc8943054832dfc32abb227fb"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"f619b35a97a85d09df187f02dc6ce3efb80df190039cfaeee8a0a7f68368b683"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"eae8eb4d6947740bcb32111338789297840cccab3fb4c9258f416a23900ea3f9"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"80f90257fdcf745f1d5870758878b164b28cc57b7af528a904ecb0974dbe198a"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"d7ee6f9807022fb027c69e69d296e233516984d6b4eb71e92874d05bdac68f1c"},"taxa":[{"id":"CWE-522","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-829","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"03c86561402b4af713efffb02c7c3b46c14dbe25fd61a84ba97c412185a2983c"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"92c0fafd8aa1d1ada2154348d6b5645882fb89c2746b85d2e3ad5d1bb61cc909"},"taxa":[{"id":"CWE-522","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-829","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"883662942abb017f404d2d9bb2bbc1dd38e4e2cbc23482aef63f7a4d776572a8"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D31","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"a2adad9ed8a261a2179e08742ad6b53d3895e9fd22804658aa61c98337712521"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D31","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"c902806bddf773628e1bacdb66062a692d6a723f6a1bb3af915763b2740c843f"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D31","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"81c4fab746d9506e85fb78a32167c7460bd8a65972bb0819e0c3f001cf4356b5"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D34","level":"note","message":{"text":"Orphaned files with no living knowledge: 1 of 392 analysed file(s) have no living knowledge left \u2014 their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 392 of the 519 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each \u2014 most significant first: Snapzy/Services/Capture/ActiveWindowResolver.swift. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"ce861fd78f6935114d3a342cb90ad25870f984e1042954fcbbe27c0e23be3658"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: SnapzyConfigurationExporter.swift \u2194 SnapzyConfigurationImporter.swift: \u0060Snapzy/Services/Configuration/SnapzyConfigurationExporter.swift\u0060 and \u0060Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift\u0060 change together 100% of the time (13 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are \u006076d09cb5\u0060 feat: Added a maximum recording resolution to improve H.264 browser c\u2026; \u00601862794d\u0060 feat: Add Sound Effects Toggle to Quick Access (#586); \u006068e3d638\u0060 feat: enlarge screenshot magnifier and add pixel grid, crosshair, col\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationExporter.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ca2822bd24406ca4a22e3d700965c9ebf893d6a16b98a926874c1c75b4f13aea"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: ShortcutOverlayModels.swift \u2192 AppStatusBarController.swift, CaptureViewModel.swift, PreferencesShortcutsSettingsView.swift: \u0060Snapzy/Features/Shortcuts/ShortcutOverlayModels.swift\u0060 changes together with 3 other files \u2014 \u0060Snapzy/App/AppStatusBarController.swift\u0060, \u0060Snapzy/Features/Capture/CaptureViewModel.swift\u0060, \u0060Snapzy/Features/Preferences/Components/PreferencesShortcutsSettingsView.swift\u0060 \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Shortcuts/ShortcutOverlayModels.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7f250c8f03f3f4a69e4c1aae1606482fc97462caf9838e18ee2463b269a143b5"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: AnnotateAnnotationFactory.swift \u2194 AnnotateAnnotationRenderer.swift: \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift\u0060 and \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift\u0060 change together 79% of the time (11 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are \u0060938f46b7\u0060 feat: add text snapping for highlighter in annotate editor (#410); \u0060b299badd\u0060 feat: Add double-sided arrow in the mark-up (#368); \u0060ff259de1\u0060 feat: Introduce arrow types and integrate into annotation features (#\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"08ae56bcae0b7f3d936f9485f0f3e20cd0c82e4886b336b1ce3b63c2231c779a"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: SnapzyConfigurationDefaultDocument.swift \u2192 PreferencesKeys.swift, SnapzyConfigurationExporter.swift, SnapzyConfigurationImporter.swift: \u0060Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift\u0060 changes together with 3 other files \u2014 \u0060Snapzy/Features/Preferences/Models/PreferencesKeys.swift\u0060, \u0060Snapzy/Services/Configuration/SnapzyConfigurationExporter.swift\u0060, \u0060Snapzy/Services/Configuration/SnapzyConfigurationImporter.swift\u0060 \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Configuration/SnapzyConfigurationDefaultDocument.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"a190f3255dfbd5a6702dcb7a76481e6d2520337340f4d65b4b261731dc605849"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: AnnotateQuickPropertiesBar.swift \u2192 AnnotateCanvasDrawingView.swift, AnnotateAnnotationFactory.swift, AnnotateAnnotationRenderer.swift: \u0060Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift\u0060 changes together with 3 other files \u2014 \u0060Snapzy/Features/Annotate/Components/AnnotateCanvasDrawingView.swift\u0060, \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationFactory.swift\u0060, \u0060Snapzy/Features/Annotate/Services/AnnotateAnnotationRenderer.swift\u0060 \u2014 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."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Annotate/Components/AnnotateQuickPropertiesBar.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5d4ece2d7f523eec603698cee49ab9c2cf725ccce65b4af205a7613a394431e5"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: VideoEditorZoomPreviewOverlay.swift \u2194 VideoEditorZoomCompositor.swift: \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomPreviewOverlay.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Services/VideoEditorZoomCompositor.swift\u0060 change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 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 \u2014 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 8 shared commits counted here, the most recent 3 are \u0060c4247083\u0060 refactor: Refactor and rename video editor components for clarity; \u0060f71b0b8a\u0060 refactor: Enhance video export settings and aspect ratio handling in \u2026; \u0060db3f9072\u0060 feat: Add zoom transition duration configuration and improve zoom tra\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorZoomPreviewOverlay.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"30dcc32b67c0e841ab6c8049b8983e67e27f86c4270f0acdf4566a7052b5a0fe"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: PreferencesQuickAccessSettingsView.swift \u2194 QuickAccessCardView.swift: \u0060Snapzy/Features/Preferences/Components/PreferencesQuickAccessSettingsView.swift\u0060 and \u0060Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift\u0060 change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 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 \u2014 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 9 shared commits counted here, the most recent 3 are \u00601862794d\u0060 feat: Add Sound Effects Toggle to Quick Access (#586); \u0060a45b2ce4\u0060 feat: Add quick access settings for hiding cards when windows are ope\u2026; \u006072e645b3\u0060 feat: Implement swipe actions for Quick Access cards with customizabl\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Components/PreferencesQuickAccessSettingsView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"dd1ea6fd244113ab36a5d86a0c1634bf1c7bb16f247f2a0c182b8f93d6344d44"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: PreferencesKeys.swift \u2194 L10n.swift: \u0060Snapzy/Features/Preferences/Models/PreferencesKeys.swift\u0060 and \u0060Snapzy/Shared/Localization/L10n.swift\u0060 change together 57% of the time (39 of the 69 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 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 \u2014 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 39 shared commits counted here, the most recent 3 are \u006076d09cb5\u0060 feat: Added a maximum recording resolution to improve H.264 browser c\u2026; \u00601862794d\u0060 feat: Add Sound Effects Toggle to Quick Access (#586); \u006041222250\u0060 feat: Added camera overlay to screen recordings (#560) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Preferences/Models/PreferencesKeys.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5cb9c82ea02f39dc572c6b07180bca9bf88729644e62d2fc361855bbc502917c"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: RecordingCoordinator.swift \u2194 RecordingToolbarView.swift: \u0060Snapzy/Features/Recording/RecordingCoordinator.swift\u0060 and \u0060Snapzy/Features/Recording/RecordingToolbarView.swift\u0060 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 \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are \u006041222250\u0060 feat: Added camera overlay to screen recordings (#560); \u0060d332f1a4\u0060 feat: Implement recording output mode selection (video/GIF) in the to\u2026; \u0060ea606bc6\u0060 feat: Add screenshot capture functionality to recording toolbar \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/Recording/RecordingCoordinator.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"cc6ea469a28ea519be7d99d2d2296cad784791226e554c76c2107bee272b90d1"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: VideoEditorVideoControlsView.swift \u2194 VideoEditorExporter.swift: \u0060Snapzy/Features/VideoEditor/Components/VideoEditorVideoControlsView.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Services/VideoEditorExporter.swift\u0060 change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 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 \u2014 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 \u0060b242b50f\u0060 feat: Add speed segment functionality to Video Editor (#316); \u0060f71b0b8a\u0060 refactor: Enhance video export settings and aspect ratio handling in \u2026; \u0060556bf830\u0060 feat: Implement auto-focus functionality with mouse tracking (#1) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorVideoControlsView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e1b0b8cea1af4fe14af6b66f68d04a18f0973a3eb6b413c9172390d2288ea40c"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: QuickAccessCardView.swift \u2194 QuickAccessPanelController.swift: \u0060Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift\u0060 and \u0060Snapzy/Features/QuickAccess/Managers/QuickAccessPanelController.swift\u0060 change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 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 \u2014 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 \u0060a45b2ce4\u0060 feat: Add quick access settings for hiding cards when windows are ope\u2026; \u00606b037585\u0060 feat: Improve QuickAccess animations and card dismissal logic for smo\u2026 (at that commit the files were still \u0060Snapzy/Features/QuickAccess/QuickAccessCardView.swift\u0060 and \u0060Snapzy/Features/QuickAccess/QuickAccessPanelController.swift\u0060); \u006094eadfa1\u0060 feat: Implement QuickAccess animations, progress indicators, and soun\u2026 (at that commit the files were still \u0060ClaudeShot/Features/QuickAccess/QuickAccessCardView.swift\u0060 and \u0060ClaudeShot/Features/QuickAccess/QuickAccessPanelController.swift\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/QuickAccess/Components/QuickAccessCardView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"3feaeb3f2c405ecd0b03134efe1d6cbb188d2aa261d838301918c2e4d9217116"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: VideoEditorLeftSidebar.swift \u2194 VideoEditorZoomPreviewOverlay.swift: \u0060Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift\u0060 and \u0060Snapzy/Features/VideoEditor/Components/VideoEditorZoomPreviewOverlay.swift\u0060 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 \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u00607de8dc5b\u0060 refactor: Refactor video editor state management and enhance playback\u2026 (at that commit the file was still \u0060Snapzy/Features/VideoEditor/Components/VideoEditorRightSidebar.swift\u0060); \u0060db3f9072\u0060 feat: Add zoom transition duration configuration and improve zoom tra\u2026 (at that commit the file was still \u0060Snapzy/Features/VideoEditor/Components/VideoEditorRightSidebar.swift\u0060); \u0060556bf830\u0060 feat: Implement auto-focus functionality with mouse tracking (#1) (at that commit the file was still \u0060Snapzy/Features/VideoEditor/Components/VideoEditorRightSidebar.swift\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Features/VideoEditor/Components/VideoEditorLeftSidebar.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"86476728a033061a7d5c169e5f32632d6869aef29e7098dc0c85ea999418158d"}},{"ruleId":"D36","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"1b213f6eedd4b140d0bc37bdf1496f72811a643f34064f12518b32e9e83bcfc7"}},{"ruleId":"D36","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"eb00976a698a5d68999b7ee6d27206fd374e916853e7ff1ead5eed42386f043f"}},{"ruleId":"D36","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"90f83b4fa27db32740afe9540c905f3c0499caed87f61049a8a903ecc95b41c3"}},{"ruleId":"D36","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"0752d0df7434000fcabf1048e2de30a7a1a8b982b3db9a19898c4dec199856b4"}},{"ruleId":"D36","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"329f0ef4132322722fbf83ac33f5bb7ad638ed99d037a66c3aa244b1e2ee654e"}},{"ruleId":"D36","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"d657599f6f99da1927d3377533dfc0888b34c4d84aa7d5579841fd72d0e39bce"}},{"ruleId":"DM6","level":"error","message":{"text":"Domain fused to persistence infrastructure: CloudUploadRecord: \u0060CloudUploadRecord\u0060 is a domain concept fused to persistence ON ITS OWN DECLARATION (the GRDB \u0060PersistableRecord\u0060/\u0060FetchableRecord\u0060 conformance), with no separate pure-domain layer \u2014 the domain entity IS the ORM row (active-record). A schema/persistence change ripples straight into the domain type. Keep the ORM/table mapping on a boundary adapter and the domain entity framework-free (or map row\u2194domain through a repository)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/Cloud/CloudUploadRecord.swift"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"4177856aee61cb6798d6b273fe1745525ef4733e318aef3b4ea53451e4a2e78e"}},{"ruleId":"DM6","level":"error","message":{"text":"Domain fused to persistence infrastructure: CaptureHistoryRecord: \u0060CaptureHistoryRecord\u0060 is a domain concept fused to persistence ON ITS OWN DECLARATION (the GRDB \u0060PersistableRecord\u0060/\u0060FetchableRecord\u0060 conformance), with no separate pure-domain layer \u2014 the domain entity IS the ORM row (active-record). A schema/persistence change ripples straight into the domain type. Keep the ORM/table mapping on a boundary adapter and the domain entity framework-free (or map row\u2194domain through a repository)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Services/History/CaptureHistoryRecord.swift"},"region":{"startLine":30}}}],"partialFingerprints":{"codehealthFindingId/v1":"a20c52c52281f42a7adeed55a989150e58cad74b76d7428ee547ee80ffe9d383"}},{"ruleId":"M2","level":"note","message":{"text":"No ADRs: No Architecture Decision Records found \u2014 no conventional ADR directory, no numbered \u0060NNNN-title\u0060 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."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"670b3d6e36a756d63097d0dfbf90afd5fc761308800b9354894a07c3f4e4aa14"}},{"ruleId":"M3","level":"note","message":{"text":"No src/ separation: Production code isn\u0027t grouped under a src/ folder \u2014 it\u0027s spread across several top-level directories, so there\u0027s no one place that says \u0027this is the product\u0027."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fdf7f5b24e313364d10170a5c2542959902fe0d26ed70edef3eaa10ec5bcdb1d"}},{"ruleId":"P3","level":"note","message":{"text":"No SAST: No static application security testing detected. For this repository\u0027s stack, add CodeQL\u0027s Swift pack (Swift/Xcode) (or \u0060semgrep --config=auto\u0060, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 53729 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\u0027s web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen \u2014 if that is your case the row is wrong, and saying so is more useful than adding a second scanner."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6e54424179c892f03ef2fd003130ac4bd43f39bbf3b1ca0a0143e25acb80ec87"}},{"ruleId":"P4","level":"note","message":{"text":"No rollback/health safety: Deployment is orchestrated by compose, but no service declares a \u0060healthcheck:\u0060 and nothing pins a previous image to fall back to \u2014 the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"db6bab8a28a2145f47e5a4e6683cda39d2ba0296c723238e8057da979ae1c706"}},{"ruleId":"P4","level":"note","message":{"text":"No release approval gate: Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY\u0027S PIPELINE FILES. What was read: every file under \u0060.github/workflows/\u0060, \u0060.forgejo/workflows/\u0060, \u0060.gitea/workflows/\u0060, \u0060.azuredevops/\u0060 and \u0060.azure-pipelines/\u0060, plus \u0060.gitlab-ci*\u0060 and \u0060azure-pipelines*\u0060 \u2014 with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab\u0027s \u0060when: manual\u0060, CircleCI\u0027s \u0060type: approval\u0060, an Azure \u0060ManualValidation@\u0060 task or an \u0060approvals:\u0060 block, a Jenkins \u0060input\u0060 step, a \u0060uses:\u0060 step naming an approval action, an \u0060environment:\u0060 paired with \u0060reviewers\u0060 / \u0060required_reviewers\u0060 / \u0060protection\u0060 / \u0060wait-timer\u0060 / \u0060deployment_branch_policy\u0060, a draft-release step, a \u0060workflow_dispatch\u0060 promotion, or a release-event gate. \u2605 What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy \u2014 all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6c11e2dbd483b4b423b95ac61bfcc7af1d55351b28a20d2b1105b31cfe38cc60"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060normalized.contains(\u0022hans\u0022) || normalized.hasPrefix(\u0022zh-cn\u0022) || normalized.hasPrefix(\u0022zh-sg\u0022)\u0060 appears character-identically in 2 files \u2014 Snapzy/Shared/Localization/AppLanguageManager.swift, scripts/swift-tools/ocr/ocr-readme-benchmark.swift. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Localization/AppLanguageManager.swift"},"region":{"startLine":150}}}],"partialFingerprints":{"codehealthFindingId/v1":"5ee9e697f0b91d7e3f312419877d0f72af93fd9c93d3b34be0c5565268a28ff6"}},{"ruleId":"X10","level":"note","message":{"text":"Duplicated predicate: \u0060normalized.contains(\u0022hant\u0022) || normalized.hasPrefix(\u0022zh-tw\u0022) || normalized.hasPrefix(\u0022zh-hk\u0022) || normalized.hasPrefix(\u0022zh-mo\u0022)\u0060 appears character-identically in 2 files \u2014 Snapzy/Shared/Localization/AppLanguageManager.swift, scripts/swift-tools/ocr/ocr-readme-benchmark.swift. It is one line, so the duplication detector\u0027s token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Snapzy/Shared/Localization/AppLanguageManager.swift"},"region":{"startLine":146}}}],"partialFingerprints":{"codehealthFindingId/v1":"685ffe8b765aafb25b75b36b0a75149e01944277fc4fe7de28380eeab2c29a30"}}],"taxonomies":[{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d","organization":"MITRE","informationUri":"https://cwe.mitre.org/","isComprehensive":false,"shortDescription":{"text":"The MITRE Common Weakness Enumeration (CWE)."},"taxa":[{"id":"CWE-1032","guid":"5f21e517-68aa-a650-9a25-5771ef024637","name":"OWASP Top Ten \u2014 Security Misconfiguration category","shortDescription":{"text":"OWASP Top Ten \u2014 Security Misconfiguration category"},"helpUri":"https://cwe.mitre.org/data/definitions/1032.html"},{"id":"CWE-1059","guid":"a2381a08-60f6-9554-a8b8-f3018cfaaca5","name":"Insufficient Technical Documentation","shortDescription":{"text":"Insufficient Technical Documentation"},"helpUri":"https://cwe.mitre.org/data/definitions/1059.html"},{"id":"CWE-1357","guid":"e4d2e772-757e-0a5c-bd7d-77052949d866","name":"Reliance on Insufficiently Trustworthy Component","shortDescription":{"text":"Reliance on Insufficiently Trustworthy Component"},"helpUri":"https://cwe.mitre.org/data/definitions/1357.html"},{"id":"CWE-16","guid":"659db3ea-affc-8453-8add-c1218fbfcb92","name":"Configuration","shortDescription":{"text":"Configuration"},"helpUri":"https://cwe.mitre.org/data/definitions/16.html"},{"id":"CWE-259","guid":"ae9ad959-fbb6-9d5e-892d-3dca66da0b69","name":"Use of Hard-coded Password","shortDescription":{"text":"Use of Hard-coded Password"},"helpUri":"https://cwe.mitre.org/data/definitions/259.html"},{"id":"CWE-353","guid":"09d7e902-d4ee-f05d-ae6c-0a1554d0c18f","name":"CWE-353","shortDescription":{"text":"CWE-353"},"helpUri":"https://cwe.mitre.org/data/definitions/353.html"},{"id":"CWE-494","guid":"b8a65e0d-e459-4a55-a931-fc1136482375","name":"Download of Code Without Integrity Check","shortDescription":{"text":"Download of Code Without Integrity Check"},"helpUri":"https://cwe.mitre.org/data/definitions/494.html"},{"id":"CWE-522","guid":"71fb233e-ce6a-ae57-9419-ef8373540b09","name":"CWE-522","shortDescription":{"text":"CWE-522"},"helpUri":"https://cwe.mitre.org/data/definitions/522.html"},{"id":"CWE-732","guid":"1da27e8f-b330-7650-ab63-bd61953eae5d","name":"Incorrect Permission Assignment for Critical Resource","shortDescription":{"text":"Incorrect Permission Assignment for Critical Resource"},"helpUri":"https://cwe.mitre.org/data/definitions/732.html"},{"id":"CWE-77","guid":"332c8ade-6612-9f56-a06b-d8d90b1a8750","name":"Command Injection","shortDescription":{"text":"Command Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/77.html"},{"id":"CWE-78","guid":"2e31ceaf-c7ae-2e5e-9661-cfb1362789cf","name":"OS Command Injection","shortDescription":{"text":"OS Command Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/78.html"},{"id":"CWE-79","guid":"fd45580b-e8c4-fc5e-8c2f-aa8fab0b4dbf","name":"Cross-site Scripting (XSS)","shortDescription":{"text":"Cross-site Scripting (XSS)"},"helpUri":"https://cwe.mitre.org/data/definitions/79.html"},{"id":"CWE-798","guid":"5e8f057d-fee3-995a-a0cb-9fc5b0d174d1","name":"Use of Hard-coded Credentials","shortDescription":{"text":"Use of Hard-coded Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/798.html"},{"id":"CWE-829","guid":"13c33925-97fb-5a5e-b40c-56d328b8a4d7","name":"CWE-829","shortDescription":{"text":"CWE-829"},"helpUri":"https://cwe.mitre.org/data/definitions/829.html"},{"id":"CWE-89","guid":"6d08fdad-37eb-c150-bbf0-d7d946863407","name":"SQL Injection","shortDescription":{"text":"SQL Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/89.html"},{"id":"CWE-94","guid":"75e7f50c-6c2f-dd52-bf40-bf6c52b861fd","name":"Code Injection","shortDescription":{"text":"Code Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/94.html"}]}],"properties":{"codehealthPublication":{"public":true,"notice":"This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings \u2014 which rule fired, in which file, on which line, and how to fix it \u2014 are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.","securityFindingsRedacted":23,"secretScannerRunsExcluded":0}},"redactionTokens":["A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."]}]}