Add provenance-preserving federated search

[jmcte]

Summary

• add bounded federated search over opted-in local provider archives
• preserve provider-native ids and return timestamp, sensitivity, redaction, schema, fingerprint, and archive provenance for every hit
• support provider/time filters, deterministic ranking, bounded pagination, current archive retention, migration, and tombstones
• keep high-sensitivity providers and body indexing behind explicit opt-ins

Governing Issue

Closes #96

Validation

• Relevant local checks passed

• Required PR checks are expected to satisfy CI Gate

• Skipped checks are explained below

• swift test --disable-sandbox — 137 tests passed

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

• synthetic tests cover cross-provider ranking, pagination, provider filters, redaction, body gating, and evidence provenance

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. This PR is stacked through #108 and remains draft until its foundations merge.

Flow Contract

• Owner lane: Hermes local search
• Repair owner: jmcte
• Autonomy class: review-gated implementation
• Risk class: high; cross-provider discovery and sensitive metadata

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 actor: foundation reviewers, then independent product and architecture review.

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 deferred only while the PR is stacked on archive and Messages foundations.

Notes

• No global people, place, trip, or account identity is created.
• Search reads current archive documents directly, so retention, migration, and tombstones apply without a second derived index.

[Hermes-omt]

Review deferred pending branch refresh. The PR head 1ddae63 is based on 2b0bcc6, while current main is d7f88dc; GitHub reports mergeable_state=dirty. A local merge-tree confirms conflicts in README.md, CommandLine.swift, CommandRunner.swift, ProviderManifest.swift, ProviderManifestTests.swift, and docs/provider-manifest.md. Repair handoff: rebase or merge d7f88dc into the PR branch, resolve these conflicts, push the new head, and wait for fresh CI before re-requesting substantive review. Exact-head source inspection and targeted federated-search tests passed locally.

[Hermes-omt]

Reviewed current head f4fec63 on Hermes. Inspected the full change set, command routing, archive/privacy gates, crawl behavior, SQLite snapshot handling, and adjacent tests. swift test and swift build -c release passed. Live PR state is mergeable/clean with auto-merge enabled; CI Gate and PR Checks are successful.