feat(ollama): add Linux and Windows local model support

[alexandervazquez98]

Pre-flight Checks

• I have searched existing open issues and this is not a duplicate
• I understand implementation PRs should be approved/sliced before review if the diff grows

Problem Description

Raven already documents Ollama as a local model/runtime option and has a Unix-oriented scripts/raven-ollama wrapper, but first-class Ollama support is not yet complete across both Linux and Windows.

Operators should be able to use Raven incident guidance with local Ollama models without manually translating shell scripts, Modelfiles, environment handling, or setup steps between platforms.

Proposed Solution

Add first-class Ollama setup/support for both Linux and Windows.

Expected scope:

• Provide project-local Ollama artifacts, e.g. ollama/Modelfile.raven, that inject Raven rules safely via SYSTEM prompt or equivalent setup.
• Keep Linux support via a POSIX shell wrapper, validating scripts/raven-ollama or replacing it with a maintained setup flow.
• Add Windows support via PowerShell and/or .cmd wrapper, e.g. scripts/raven-ollama.ps1, with equivalent behavior to the Linux wrapper.
• Document platform-specific usage:
  • Linux/macOS shell invocation.
  • Windows PowerShell invocation.
  • Required environment variables such as RAVEN_OLLAMA_MODEL.
  • How to build/update the local Ollama model with Raven instructions.
• Ensure the wrapper preserves Raven safety rules:
  • CI ID remains mandatory.
  • Do not invent CI IDs.
  • Preserve --source ollama guidance for captured events.
  • Do not embed secrets or edit global Ollama/server configuration silently.
• Consider whether raven setup ollama should generate or validate these files once setup automation exists.

Affected Area

Agent setup / local model integration / scripts / documentation

Acceptance Criteria

• Linux shell wrapper works with ollama run and Raven prompt injection.
• Windows wrapper works from PowerShell or Command Prompt with equivalent behavior.
• Documentation explains Linux and Windows usage clearly.
• Modelfile or setup artifact is project-local and does not require silent global profile edits.
• CI ID validation is consistent across platforms.
• Scripts pass basic syntax validation where practical (bash -n, PowerShell parser/check, etc.).
• No secrets or local operator-specific paths are committed.

References

• docs/agent-setup.md
• docs/ai-usage.md
• scripts/raven-ollama
• Future raven setup ollama flow from the setup automation roadmap