com.limen.mat-serve launchd crash-loop (engine/serve.py missing) drives _health-private ARCA re-seal churn

[4444J99]

Finding

~/Library/LaunchAgents/com.limen.mat-serve.plist (RunAtLoad + KeepAlive) runs
/opt/homebrew/bin/python3 <...>/_health-private/daily-mat-strength-brainstorms/engine/serve.py --launchd
on port 8818. engine/serve.py does not exist, so launchd crash-loops and appends a Python
"No such file" error line to engine/state/serve.log on every restart. That log is now ~24.6MB.

Why it matters to ARCA (POTESTAS 0.3, #2089)

serve.log lives inside _health-private, so its content hash flips on every append. Verified
2026-08-09: scripts/arca.sh status reports _health-private — CHANGED within ~60s of a fresh
seal; each backup beat re-seals and pushes ~24MB to organvm/arca-g2. This inflates generation
history and can trip size-based generation rotation prematurely (ARCA_MAX_MB=512).

Reproduction

bash -c 'test -f ~/Workspace/_health-private/daily-mat-strength-brainstorms/engine/serve.py && echo present || echo missing'
→ missing. tail ~/Workspace/_health-private/daily-mat-strength-brainstorms/engine/state/serve.log
shows repeated can't open file '.../engine/serve.py': [Errno 2].

Fix options (human-gated)

1. Restore/create engine/serve.py (engine file lost or not yet written), or
2. Re-point the plist ProgramArguments at the real script, or
3. launchctl unload/remove the agent until the engine exists.

Plist writes are hook-banned for agents; choosing how the mat engine should serve is a product
decision → human gate. Disposition should be recorded in
institutio/governance/parameters.yaml (mat-serve note).