docs: clarify shared snapshot guard scope

[marius-kilocode]

The Snapshot slow-repository prompt is easy to reason about as worktree-local, which obscures why Agent Manager can ask for confirmation repeatedly across concurrent worktrees. Within one VS Code extension host, sidebar chat, Kilo tabs, and Agent Manager local worktree sessions route through one lazily started backend service, while only directory-keyed instance state is isolated.

This documents that ownership model and aligns the Snapshot guard commentary with its actual service-scoped lifetime. The guidance now makes clear that the slow-track guard spans shared worktree requests and re-arms only when a continued snapshot successfully produces a hash, so later slow requests may prompt again.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (5 files)

• AGENTS.md
• packages/kilo-vscode/AGENTS.md
• packages/opencode/AGENTS.md
• packages/opencode/src/kilocode/snapshot/track.ts
• packages/opencode/src/snapshot/index.ts

---

_{Reviewed by claude-4.6-sonnet-20260217 · 316,238 tokens}

_{Review guidance: REVIEW.md from base branch main}