refactor(cli): scope project ID cache lifecycle

[marius-kilocode]

Project ID resolution used InstanceState.make inside a Kilo service layer, which left lifecycle ownership tied to the ambient instance-state singleton. This prevented the service from owning its cache explicitly and left the architecture ratchet exception in place.

The service now owns an Effect cache keyed by project directory, invalidates only the disposed directory through the existing instance disposal lifecycle, and unregisters the disposal hook when the service scope closes. Resolution priority and public callers remain unchanged. Focused coverage protects concurrent project isolation and cache refresh after disposal.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• packages/opencode/src/kilocode/project-id.ts
• packages/opencode/test/kilocode/project-id.test.ts
• script/architecture-allowlist.json

---

_{Reviewed by grok-4.6 · Input: 155.1K · Output: 41.3K · Cached: 843.1K}

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