docs: v0.27.1 release notes

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

Author: ualtinok

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

@@ -0,0 +1,9 @@
+# v0.27.1
+
+Patch release: fixes a first-run setup crash introduced in v0.27.0, and stops the diagnostic log from masking token counts.
+
+## Fixes
+
+- **Setup no longer crashes on a fresh machine.** v0.27.0 moved configuration to the shared CortexKit location (`~/.config/cortexkit/magic-context.jsonc`), but on a brand-new install that directory does not exist yet, and the setup wizard tried to write the config without creating it first, so the run ended in `ENOENT: ... magic-context.jsonc.tmp`. The atomic-write helper now creates the parent directory before writing, so the very first `setup` completes cleanly. If you hit this on v0.27.0, update and re-run `npx @cortexkit/magic-context@latest setup`.
+
+- **Token counts stay readable in the log.** Diagnostic log lines like `tokens.input=45000` and `hasUsageTokens=true` were being rewritten to `<REDACTED>` because the secret redactor matched on the word "token" in the key name. A real key, token, or password is always a high-entropy string, never a bare number or boolean, so numeric and boolean values are now left as-is. Actual secrets (bearer tokens, JWTs, API keys) are still redacted by their value shape regardless of the key name, so nothing sensitive leaks. This also applies to the log tail in `doctor --issue` reports.