docs: v0.31.5 release notes

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

Author: ualtinok

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

@@ -0,0 +1,11 @@
+# v0.31.5
+
+Patch release: two user-reported fixes.
+
+## Fixed
+
+### Pi historian failing on every run with some extension setups (#222, #221)
+Hidden Pi subagent children (historian, dreamer, recomp) load your Pi extensions so extension-provided models keep working. In Pi's print mode, extensions load before the child's prompt is read — an extension that starts an agent turn during startup made the child fail with `Agent is already processing` on every model in the chain, wedging the historian entirely. The runner now detects this exact collision and retries the run once with user extensions disabled (Magic Context's own tooling stays loaded). Well-behaved extension setups are unaffected and keep extension-provided models; colliding setups get a working historian using built-in or provider-configured models, with a clear log line distinguishing extension interference from model failures.
+
+### Doctor warned about a removed setting (#220)
+The doctor's user-memories check read the v1 `dreamer.user_memories.enabled` key, which the v2 config migration removes — so the warning fired on every run when `dreamer.disable=true` and pointed at a setting that no longer exists. The check now reads the v2 task schedule (`dreamer.tasks["review-user-memories"].schedule`), matching the runtime gate. Thanks @tobwen for the diagnosis and the fix (#219).