Fix analyze process stopping after segmentation on first run

[Copilot]

Analysis chain stops after segmentation on first run due to stale React state closure in handleRetryAnalysis. The function captures capture at invocation time, then checks capture.analysis?.segmentation after async handlers complete—but state updates haven't propagated to the closed-over variable.

Changes

• Return updated capture from handlers: handleSegmentation, handlePithDetection, handleRingDetection now return CaptureWithAnalysis | null
• Pass capture through chain: Added optional captureOverride parameter to pith/ring handlers
• Use return values instead of stale state:

// Before: checks stale closure
await handleSegmentation();
if (capture.analysis?.segmentation) {  // ❌ still old value
  await handlePithDetection();
}

// After: chains via return values
const segmentedCapture = await handleSegmentation();
if (segmentedCapture?.analysis?.segmentation) {  // ✅ fresh value
  const pithCapture = await handlePithDetection(segmentedCapture);
  if (pithCapture?.analysis?.pith) {
    await handleRingDetection(pithCapture);
  }
}

• Fix button handlers: Wrapped onPress in arrow functions to avoid TypeScript type mismatch with optional parameter

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.expo.dev
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/tree-disk-analyzer/tree-disk-analyzer/tree-disk-capture/node_modules/.bin/expo lint (dns block)
• reactnative.directory
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/tree-disk-analyzer/tree-disk-analyzer/tree-disk-capture/node_modules/.bin/expo lint (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>analyze process is stopping after segmentation on first run</issue_title>
<issue_description>must be something with the react state and database handling. when i load the capture again, the complete analyze step is working. but on the first analyzing process, it stops after the segmentation and i have to manually retry the pith and ring detection, even though the segmentation was successful.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes analyze process is stopping after segmentation on first run #40

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.