Scheduling
`launchd` install, ensure, reload, and path-aware reinstall flows.
Use upstream for the engine. Use this repo for the control room.
If all you need is one export right now, the upstream project may already be enough. Apple Notes Snapshot earns its keep when you want the workflow to stay observable, schedulable, and easier to recover later.
Decision table
| Question | Choose upstream only | Choose Apple Notes Snapshot |
|---|---|---|
| Do you only need a one-time export? | Yes | No, you want recurring snapshots |
| Do you care about freshness, failure reason, and logs? | Not much | Yes, operational visibility matters |
| Do you want a local control plane around the exporter? | No | Yes, CLI + optional Web console |
| Do you want a reviewable wrapper around path changes and scheduler setup? | Not necessary | Yes |
| Do you want AI-assisted diagnosis around backup health? | No, deterministic status alone is enough | Yes, an operator next-step assistant would help |
| Do you want MCP-aware agents to inspect local backup state? | No, no agent-facing surface is needed | Yes, a read-only MCP contract is useful |
| Do you want a token-gated same-machine browser/API lane? | No, CLI plus logs are enough | Yes, the Local Web API is useful |
What the control room adds
Health surface
`status`, `verify`, `doctor`, log health, and metrics make the workflow inspectable.
Operational safety
Locks, state files, log rotation, vendor provenance, and token-aware local Web actions.
Path-aware wrapper
A calmer local shell around the exporter, so reinstall, path drift, and recovery stay reviewable instead of magical.
Optional second lane after the control room
Once the operator fit is already obvious, the repo also adds three builder-facing surfaces around the same local facts: AI Diagnose for advisory explanation, a token-gated Local Web API for same-machine browser or HTTP workflows, and a read-only-first MCP surface for agent hosts.
Those layers are real, but they are still second-shelf surfaces. Open Proof if you want the trust boundary first, or For Agents if you already know you need the host-facing contract.
What this repo does not try to add
- No cloud sync
- No team collaboration surface
- No two-way Apple Notes editing
- No write-capable MCP surface in v1
- No claim that the upstream engine is replaced or obsolete
What to open next
- Quickstart if you already know the wrapper is the right fit
- Proof if you want the evidence and boundary page before you install anything
- Support routing if your next step is help, Q&A, or a bug report
- Release history if you want the tagged story versus current main
- FAQ if you still need short answers before you clone