Document or support fallback when semantic search is unavailable in a repository region

[Anexria]

Summary

entire checkpoint search cannot search a repository whose data is hosted in an unsupported region. Entire CLI 0.9.0 now returns a clear region-availability error, but the documented search workflow does not describe regional availability or a supported local fallback.

Environment

• Entire CLI: 0.9.0
• OS: Windows amd64
• Authentication: active GitHub device-flow login
• Repository: Entire-enabled Git repository with local and remote entire/checkpoints/v1 refs

Reproduction

Run an exact search for a known session that exists in local checkpoint history:

entire checkpoint search "<known-session-id>" --json

Actual result:

search failed: semantic search: semantic search is not yet available in the region(s) hosting this search

The same session is available locally:

entire checkpoint explain --session "<known-session-id>" --search-all --json --limit 1000 --no-pager

This returns multiple checkpoints. The default branch-limited local lookup can return zero for the same older session.

Expected Behavior

One of the following should be supported and documented:

1. Hosted semantic search is available for every region where Entire can host/index repository checkpoint data; or
2. The CLI provides a supported local-history fallback when hosted search is unavailable; or
3. The search documentation clearly lists regional availability and the exact local fallback command.

Machine-readable --json calls should ideally return a structured error that distinguishes regional unavailability from an empty search result.

Additional Context

On Entire CLI 0.8.42, the same exact query returned an empty result set, which could be misinterpreted as absent history. Version 0.9.0 improves the error message, but agents still need a documented way to avoid a false no-history conclusion.

Acceptance Criteria

• Regional search availability is documented or made universal.
• Automation can distinguish regional unavailability from zero matches.
• A supported fallback is documented when hosted search cannot serve the repository.

[atirna]

I can take a focused pass on the CLI contract: classify regional unavailability in --json and document the existing checkpoint explain --search-all path for known sessions. I’d keep automatic fallback out because local history lookup isn’t semantically equivalent to search. Would that scope work?