Decide provider and daemon execution model

[jmcte]

Summary

• propose the signed on-demand CLI as the required execution model and archive owner
• compare on-demand CLI, launchd daemon, signed per-domain helpers, and external delegation across every requested operational and security dimension
• classify every current provider by framework, filesystem/plist, private fallback, delegation, or unsupported state
• keep daemon mode, helpers, external substitution, and all mutations behind separate provider-specific decisions

Governing Issue

Refs #83

This issue is explicitly human-required. The PR proposes a decision but does not mark the ADR accepted or close the issue before non-author product, architecture, and security approval.

Validation

• Relevant local checks passed

• Required PR checks are expected to satisfy CI Gate

• Skipped checks are explained below

• git diff --check — passed

• bash scripts/ci/run-fast-checks.sh — passed; 110 tests, 88.58% source coverage, mutation checks, debug and release builds

No checks skipped.

Bootstrap Governance

• Changes are scoped to the linked issue
• Contributor or PR guidance changes are reflected in CONTRIBUTING.md, .github/PULL_REQUEST_TEMPLATE.md, and docs/bootstrap/onboarding.md when applicable
• PR author enabled auto-merge where GitHub allows it, or GitHub plan-limit evidence/unavailable reason is recorded and the fallback merge-readiness policy applies
• No real secrets, runtime auth, or machine-local env files are committed

No contributor guidance changed.

Flow Contract

• Owner lane: Pheidon architecture governance
• Repair owner: jmcte
• Autonomy class: human-required decision
• Risk class: medium architecture and permission boundary

Flow Merge Readiness

• Every blocker has a next actor and next action
• No active blocking requested changes remain
• Non-author approval is present when required
• PR author enabled auto-merge where GitHub allows it, or recorded why it is unavailable/unsafe

Next actors: product, architecture, and security reviewers must accept or amend the proposed decision.

Merge Automation

• PR author enabled auto-merge with gh pr merge --auto --squash, or the reason it is unavailable/unsafe is noted below

Auto-merge is intentionally disabled for the human-required architecture decision.

Notes

• No daemon, helper, IPC listener, or external dependency is implemented.
• Existing local-only and read-only defaults remain authoritative while the ADR is proposed.

[Hermes-omt]

Blocked pending branch refresh: head 0fca069 is behind current main d7f88dc and GitHub reports mergeable=false, mergeable_state=dirty. Please rebase/update the PR branch, resolve conflicts, and wait for fresh CI before re-review. Exact-head local inspection and swift test passed (110 tests); public reviews and inline review comments are empty.

[Hermes-omt]

Exact-head macOS review completed for 8dc58ce7e7cef18a39f626009102c5f1f13ec44a. The branch is current with main, mergeable/clean, auto-merge is enabled (squash), and no unresolved review comments were found. I inspected the full diff, execution-model call paths, release scripts, and adjacent parser tests; git diff --check and local fast checks passed (110 tests). GitHub Actions is successful, but the claude and cloudflare-workers-and-pages check suites remain queued after a bounded wait. Please let those checks settle, then rerun exact-head review before approval or merge.