v0.5.3

🎉 Yggdrasil is now listed on glama.ai!
The MCP server is indexed, builds and passes introspection, and scores tier A on
Glama's Tool Definition Quality Score. Most of this release is the work that got us there.

Changed

• MCP tool definitions tuned to the TDQS rubric (Glama's Tool Definition Quality
  Score) — every tool now has: a tight, front-loaded description that states purpose +
  scope and names its sibling tools for disambiguation (recall = all projects,
  bootstrap = load one project, search = query one project); explicit when/when-not
  guidance; MCP annotations (readOnlyHint/destructiveHint/idempotentHint/
  openWorldHint) carrying the behavioral profile; a meaningful title; 100%
  per-parameter description coverage; and an enum on type (the canonical memory
  categories — also curbs type drift). Estimated per-tool TDQS ~4.3–4.5 (tier A),
  up from C.

Fixed

• MCP serverInfo reported a stale dev identity (yggdrasil-mvp / hardcoded
  0.1.0) to every host — now reports yggdrasil and the real installed version
  (read from package metadata). Surfaced by Glama showing the server as 0.1.0.

Added

• Dockerfile — lets Glama and any container host build, start and introspect the
  MCP server (the stdio facade answers initialize/tools/list cold, no engine
  needed), so directory listings that gate on a Glama check pass.
• glama.json + full canonical Elastic-2.0 LICENSE text (was a one-line
  pointer GitHub read as NOASSERTION) so the license is detected and the server
  is installable from directory listings.
• Per-prompt auto-recall hook (UserPromptSubmit) — the fix for "the agent
  forgets to use the memory". On every request it runs a cross-project recall and
  injects the top genuinely-relevant matches (raw-cosine gate, so off-topic
  prompts inject nothing), and asks the agent to cite what it reused inline as
  🌳 recalled: … — the visible breadcrumb that makes the tool's work trustworthy.
  ygg hooks now installs both retrieval hooks (SessionStart bootstrap + this).