Crash (EXC_BAD_ACCESS) in SwiftUI HostingScrollView / AttributeGraph on macOS 11.7.11 (Big Sur) – AlDente 1.37.3

**MacBook (please complete the following information):**

- **MacBook Model**: MacBookPro11,1 (MacBook Pro 13-inch, Late 2013 / Mid 2014)
- **macOS Version**: macOS 11.7.11 (20G1443)
- **Charger Model**: Apple 60W MagSafe 2
- **Charging Cable**: MagSafe 2 (Apple original)
- **AlDente Pro or AlDente Free**: AlDente Free
- **AlDente Version**: 1.37.3 (94)
- **List or add screenshots of all enabled/disabled settings in AlDente**: Default settings
- **External Monitor connected?**: No
- **MacBook used in Clamshell Mode (with the lid closed)?**: No

### Describe the bug

AlDente crashes with `EXC_BAD_ACCESS (SIGSEGV)` on the main thread.

The crash happens inside SwiftUI’s AttributeGraph / HostingScrollView during layout and scroll updates:

- `AGGraphGetValue`
- `DynamicLayoutScrollable.childGeometries`
- `HostingScrollView.updateContent` / `scrollViewDidScroll` / `offset(for:)`
- Followed by AppKit layout (`NSClipView`, `NSScrollView`, `NSHostingView.layout`)

**Exception details:**
- Exception Type: `EXC_BAD_ACCESS (SIGSEGV)`
- Exception Codes: `KERN_INVALID_ADDRESS at 0x000000000000005f`
- Crashed Thread: 0 (Dispatch queue: com.apple.main-thread)

This is the last version that officially supports macOS 11 Big Sur.

### To Reproduce

Steps to reproduce the behavior:
1. Launch AlDente 1.37.3 on macOS 11.7.11
2. Sеtings
3. App crashes

### Expected behavior

The app should not crash.

### Additional context

Full crash report is attached / pasted below.

Hardware is quite old (2013/2014 MacBook Pro, 8 GB RAM, Intel Iris).
System Integrity Protection is enabled.

---

Crash Report (click to expand)

[pasted-text.txt](https://github.com/user-attachments/files/30684579/pasted-text.txt)

Start by reviewing the attached crash report and reproducing the crash on macOS 11.7.11 with AlDente 1.37.3, following the listed Settings step. Trace any app-owned frames around the SwiftUI AttributeGraph and HostingScrollView calls; done means the reported Settings launch path no longer crashes.

由索引模型根据 Issue 内容生成。