docs: add native-Windows + AMD Strix Halo deployment field notes

[midtskog]

What & why

Net-new documentation: field notes for running Hermes Agent natively on Windows (gateway as an always-on LocalSystem service) and on an AMD Strix Halo unified-memory iGPU — two deployment paths the current docs don't cover. Aligns with contribution priorities #2 (cross-platform compatibility) and #7 (documentation).

The content is hard-won operational knowledge gathered running Hermes in this configuration day-to-day:

• LocalSystem gateway gotchas — system-site vs --user dependency visibility (python -s -m pip), HERMES_HOME resolution under the systemprofile, session-0 limits for interactive OAuth/GUI + a scheduled-task proxy pattern, S4U-not-SYSTEM for credential-reading tasks, PowerShell 5.1 (ISOWeek) traps, ffmpeg on the service PATH.
• Windows-specific Hermes traps — cron --script extension dispatch, no env-var expansion in the agent's file tools, CRLF for agent-written .bat, and the MEDIA: unquoted-Windows-path delivery behavior.
• Strix Halo tuning — MoE ≫ dense on a bandwidth-bound iGPU, Q4_K vs BF16, MTP crashes, the "system RAM is the scarce pool, not VRAM" insight + --no-mmap + system-managed pagefile, depth-bound throughput, aux-model constraints, and the NPU reality (Whisper-only, experimental).

Placement

docs/deployment/windows-strix-halo.md (new — docs/ currently has no deployment/hardware home).

Testing / platforms

Every item was observed in practice on Windows 11 + Ryzen AI MAX+ 395 (Strix Halo, 128 GB unified memory) running Hermes v0.15.1, Ollama, and a llama.cpp server. Measurements are framed as one-setup/directional rather than guarantees, and Hermes-behavior claims are marked v0.15.1-specific. The MEDIA: section cites the existing open Windows-path PRs (#34021, #32735, #26368, #26098; cf. issue #6249).

Notes

These are field notes, not normative docs — happy to relocate (e.g. split deployment vs hardware), trim, or reframe to match the docs structure you prefer.

[tonydwb]

Code Review Summary

Verdict: Approved ✅

Review Findings

This PR adds comprehensive field notes for running Hermes Agent natively on Windows (as a LocalSystem service) and on AMD Strix Halo unified-memory hardware.

✅ Looks Good

• Practical value: Covers hard-won operational knowledge — session-0 isolation, HERMES_HOME resolution, system vs user site-packages, S4U logon pattern, ffmpeg PATH, PowerShell 5.1 traps, MoE vs dense on iGPU.
• Honest framing: Properly scoped as "field notes, not official docs" with version-specific claims marked.
• Well organized: Two clear parts (Windows service issues, Strix Halo tuning) with numbered subsections.
• Citations: Inline references to relevant PRs and issues where applicable.
• Clean diff: 205 new lines, 0 deletions.

No Issues Found

---

Reviewed by Hermes Agent

[tonydwb]

Code Review Summary

Verdict: Approved ✅

Review

Excellent field notes for native-Windows + AMD Strix Halo deployment. Hard-won operational knowledge from day-to-day experience.

✅ Looks Good

• Practical value: Covers real gotchas (LocalSystem gateway, session-0 limits, MoE vs dense on iGPU, --no-mmap requirement) that users would only discover through painful trial and error.
• Well-structured: Organized by domain (Windows setup, Strix Halo tuning, NPU reality) with clear version markers.
• Honest about limitations: Measurements framed as directional, Hermes-behavior claims marked v0.15.1-specific.
• Appropriately placed: New docs/deployment/ — fits the existing docs structure.

---

Reviewed by Hermes Agent (cron job)

[teknium1]

Thanks for preserving operational Windows and Strix Halo experience.

Problems

• docs/deployment/windows-strix-halo.md:1 is outside the published Docusaurus source. The site is configured from website/ (website/docusaurus.config.ts:92-100), published pages live in website/docs/, and navigation is in website/sidebars.ts:3-29; this new file would not reach the docs site.
• docs/deployment/windows-strix-halo.md:103 says the file tools do not expand ~, but current resolution explicitly calls _expand_tilde() (tools/file_tools.py:34-48, 451-464). Please mark this as a verified historical v0.15.1 limitation or update it for current behavior.

Suggested changes

• Move/split the material into website/docs/: the supported Windows gateway path is already documented at website/docs/user-guide/windows-native.md:167-199; place the Strix-specific material in an appropriately frontmatter-equipped guide and add it to website/sidebars.ts.
• Recheck version-sensitive Hermes claims before publishing. Current MEDIA: extraction supports unquoted Windows drive-letter paths (gateway/platforms/base.py:1489-1511; commit 51d165a8e).

Automated hermes-sweeper review.

[teknium1]

This path is not part of the published Docusaurus source: site content lives under website/docs/ and navigation is website/sidebars.ts. Please move/split this into website/docs/ with frontmatter and add the relevant sidebar entry; otherwise the field notes are not published.

[teknium1]

Current main expands ~ in file-tool paths via _expand_tilde() (tools/file_tools.py:34-48,451-464). Please label this as a v0.15.1-only observation with a current-status note, or revise it so readers do not treat it as current behavior.