v0.10.1

New & Noteworthy

• Context comes back ranked. build_context no longer truncates the neighbourhood at the oldest rows: related engrams are ranked by how strongly they connect to the anchor, spreading activation through the relation and link graph the way recall follows associations, and max_related keeps the most relevant. Salient engrams rank higher on the way; seeds always come back complete.
• The learning loop closes at session end. The Stop hook's capture nudge now also asks the agent to raise the salience of a recalled engram that proved to be the key to the task, so knowledge that keeps paying off surfaces first in future sessions. Same once-per-session contract, about 120 tokens.
• Retired knowledge fades, it never disappears. An engram whose status is deprecated, superseded, archived or legacy now ranks below equally relevant current knowledge in every scored search mode and in context ranking - softly faded by the new search.retired_weight setting (0.0 to 1.0, default 0.6, 1.0 disables), also settable as CRYSTALLINE_SEARCH_RETIRED_WEIGHT. Nothing is ever filtered out by it: a superseded engram still answers "how did we do this before". The write surfaces teach the recognized retirement vocabulary, so agents pick a status the fade understands.

Fixes

• The Streamable HTTP transport no longer prepends an SSE priming event (retry: 3000) to POST responses. Strict intermediary parsers such as AWS Bedrock AgentCore Gateway rejected that optional field and failed every tool call; responses now open directly with the JSON-RPC message, the same minimal shape the Python MCP SDK emits. The deprecated 2024-11-05 HTTP+SSE transport was never served and now says so in the deployment docs; legacy clients get an immediate 400 naming the missing session

Breaking changes

• Default ranking changes for knowledge bases that hold retired engrams: they now rank below current ones instead of tying. Restore the old behavior with crystalline config set search.retired_weight 1.0
• build_context returns related engrams in relevance order instead of the previous undocumented storage order; integrations that relied on that order should rely on the ranking instead