docs: v0.27.2 release notes

Co-authored-by: Alfonso [Magic Context] <288211368+alfonso-magic-context@users.noreply.github.com>

Author: ualtinok

.alfonso/release-notes/v0.27.2.md

@@ -0,0 +1,15 @@
+# v0.27.2
+
+Patch release: fixes a TUI sidebar that fails to load on OpenCode 1.17.10, a config-migration edge case that could leave you running on defaults, and a context-limit misreport on OpenAI OAuth models. Also includes the two fixes already queued from v0.27.1's window (#176, #177).
+
+## Fixes
+
+- **TUI sidebar loads again on OpenCode 1.17.10.** OpenCode 1.17.10 bumped its TUI runtime (OpenTUI) to 0.4.2. The Magic Context sidebar ships as raw TSX that compiles against OpenTUI's JSX runtime, but the plugin didn't declare `@opentui/solid` / `solid-js` as dependencies, so on 1.17.10 the sidebar failed to load with `Cannot find module '@opentui/solid/jsx-dev-runtime'`. Those runtime dependencies are now declared (pinned to the versions the host ships), and a CI smoke test imports the TUI entry the way OpenCode loads it so this can't silently regress again.
+
+- **Config migration no longer moves your user config when you open OpenCode inside the config directory.** The v0.27.0 config-location migration moves a legacy config into the shared CortexKit location. If you happened to open OpenCode with its working directory set to the config home itself (`~/.config/cortexkit`), the project-scope migration treated your user config as a project config, moved it into a `.cortexkit/` subfolder, and renamed the original aside, leaving Magic Context running on default settings until you noticed. The migration now never treats a user-scope config as a project source. No data was lost by the original behavior (the file's contents were preserved), but the active config path could go empty.
+
+- **Context limit no longer misreported for OpenAI OAuth models (e.g. gpt-5.5).** Magic Context reads each model's prompt limit from OpenCode's resolved provider config. That limit is auth-dependent: on OpenAI OAuth, gpt-5.5's input cap is 272k, not the catalog's 922k. If the limit cache warmed up before your provider auth finished loading, it could cache and persist the raw 922k, and because the existing recovery only corrects a limit that's too *low*, a too-*high* value never self-corrected, so the sidebar showed plenty of headroom while the backend rejected the request. The limit cache now re-warms once, after a successful response proves auth is live, replacing any stale pre-auth value with the real one.
+
+- **Pi spawns correctly on Windows (#177).** Pi subagents now spawn through the running Node executable instead of a bare `pi` command, which failed on Windows. The spawn path is also shell-free, so prompt text is never passed through `cmd.exe`.
+
+- **Fresh installs default to `.jsonc` config (#176).** New installs now write `magic-context.jsonc` instead of `tui.json`.