docs: update local model and platform all guidance

[ftchvs]

Summary

• Document platform: "all" as a broad cross-platform preflight mode without implying platform parity.
• Update README/API/local-model guidance for the PR fix: stabilize local model review flow #16 local model UX/runtime behavior: dropdown model discovery, embedding-model filtering, timeout recovery, bounded Ollama generation, think: false, and fenced JSON parsing.
• Replace stale local model recommendation language with current runtime-compatibility caveats and keep deterministic rules as the trusted baseline.

Validation

• make test → 196 passed
• make eval → 58 examples, 1.000 decision accuracy, no decision/policy/category FP/FN notes
• make benchmark → 213 examples, 1.000 decision accuracy, no decision/policy/category FP/FN notes
• make pr-preflight → OK

Notes

• Docs-only follow-up to PR fix: stabilize local model review flow #16.
• Keeps model status: ok framed as runtime compatibility, not proof of policy judgment.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1b7aa8e0e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove incorrect timeout fallback claim

The new README text says browser timeouts still return rule-based findings with model.status = unavailable, but the /ui flow aborts the request client-side on timeout (fetchWithTimeout) and then renders an error state without any analysis payload. In the timeout scenario, users do not receive rule findings, so this guidance is misleading for anyone relying on timeout recovery behavior in the web UI.

Useful? React with 👍 / 👎.