https://techrawcull.netlify.app/tags/issues/Recent content in Issues on RawCullHugoenFri, 04 Sep 2026 20:55:01 +0200https://techrawcull.netlify.app/docs/copilot/issues/Fri, 04 Sep 2026 00:00:00 +0000https://techrawcull.netlify.app/docs/copilot/issues/<h1 id="known-issues-and-findings">Known Issues and Findings<a class="td-heading-self-link" href="#known-issues-and-findings" aria-label="Heading self-link"></a></h1> <p>This is a code-review pass over the main <code>RawCull</code> app target (excluding <code>RawCullTests</code> and the external SPM packages). Overall the codebase is unusually clean for its size: <strong>no force-unwraps (<code>!</code>), no <code>try!</code>, no force-casts (<code>as!</code>), no unguarded array <code>[0]</code> accesses, no <code>DispatchSemaphore</code> or <code>Timer</code>/<code>NotificationCenter</code> leaks</strong>, and every <code>startAccessingSecurityScopedResource()</code> call has a matching <code>stopAccessingSecurityScopedResource()</code> on all paths, including cancellation and <code>deinit</code>. The findings below are the exceptions to that otherwise solid baseline. Severities: <strong>High</strong> (real user-facing breakage or data-loss risk), <strong>Medium</strong> (real bug/gap, narrow trigger conditions or degraded UX), <strong>Low</strong> (code-quality / robustness / maintainability).</p>