#22091: docs(readme): add Windows-native dev gateway command

## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [x] Bug fix - [ ] Feature - [ ] Refactor - [x] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [ ] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds Windows-native support for `pnpm gateway:watch` and extracts gateway startup configuration into a separate module. Changes include: - Created `scripts/gateway-watch.mjs` to handle platform-specific watch behavior (stops daemon on Windows before starting watch mode to avoid port conflicts) - Refactored startup config logic from `server.impl.ts` into new `startup-config.ts` module - Added test for gateway method catalog consistency - Updated README with mermaid architecture diagram and Windows-specific notes - Renamed `BASE_METHODS` to `CORE_GATEWAY_METHODS` for clarity The Windows watch flow differs from Unix: it runs `gateway run --bind loopback --port 18789 --allow-unconfigured` instead of `gateway --force`, providing more explicit configuration. <h3>Confidence Score: 5/5</h3> - Safe to merge - clean refactoring with platform compatibility improvements - Clean code extraction, no logic changes in refactoring, adds helpful test coverage, and improves Windows developer experience without affecting existing Unix/Linux/macOS behavior - No files require special attention _{Last reviewed commit: 6859bff} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->