refactor(cli): reuse config overlay reader after updates

[marius-kilocode]

What Problem This Solves

Config overlay updates repeat the same auth, account, config, and source reads used by the existing overlay reader.

Why This Change Was Made

Call the existing overlay Effect after a successful update instead of maintaining a second resolution block. Keep write locking, conflicts, invalidation, events, and disposal ordering unchanged. The request InstanceRef remains the same; project disposal is registered for pre-response and global disposal still follows resolution.

User Impact

No intended HTTP or config behavior change. Scope, fallback behavior, read concurrency, and response construction stay the same. Diagnostic tracing gains a nested ConfigConsoleHttpApi.overlay span under overlayUpdate.

Evidence

• Two files: 1 added line, 42 removed, net 41 fewer lines (29 production plus 12 allowlist). No new helpers, public exports, dependencies, or tests.
• All 47 existing config-overlay, httpapi-instance-context, and httpapi-error-middleware tests pass. These exercise real HTTP reads and writes, response freshness, conflicts, and disposal behavior with temporary fixtures.
• CLI typecheck, focused lint (zero warnings/errors), annotations, and git diff check pass.
• Fresh report: 27 to 26 duplicate pairs, 521 to 502 duplicated lines, 3646 to 3513 duplicated tokens. Only fingerprint ec31254ab83e4a2a removed; duplication ratchet passes.
• No manual UI launch was needed for this internal reuse; the existing HTTP regression tests cover the affected paths.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• packages/opencode/src/kilocode/server/httpapi/handlers/config-console.ts
• script/kilocode-duplication-allowlist.json

---

_{Reviewed by grok-4.6 · Input: 132.8K · Output: 6K · Cached: 172.7K}

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