v0.43.0.0

Your agent now has five memory verbs it can actually reach. Cathedral 1 freezes
a stable, versioned memory protocol — recall, remember, entity, synthesize,
forget — over the brain's operation catalog, the way Postgres speaks one wire
protocol to every client. Point any MCP harness at it (claude mcp add gbrain -- gbrain serve --surface verbs, or the Codex/OpenClaw equivalents) and the agent sees
exactly five self-describing tools instead of a wall of internal ops. Every response
carries what it is, why it matched, where it came from, and what it spent (the token
budget on recall, latency on entity, the full cost block on synthesize) — and the
contract never breaks: v1 field names and meanings are frozen, changes are
additive-forever.

What you can do now that you couldn't before:

• Remember a fact once, recall it in a fresh session — in any harness. remember
  takes mandatory provenance (where the fact came from) and an optional expiry, dedupes
  against what's already known, and supersedes the old fact when it changes
  ("X joined acme-example" → "X left acme-example" — the outdated fact expires, the
  history stays). recall retrieves saved facts and,
  with a query, budget-packed page snippets — the server enforces the token budget and
  tells you what it dropped instead of trusting the client to trim.
• Look up one person/company/project as a compact card in well under 100ms, zero LLM
  calls. entity resolves a name to a privacy-safe card (who/what, aliases,
  last-touched, open threads, top typed edges) — or, on a miss, near-miss suggestions
  instead of a dead end.
• Reason across pages when you actually need it. synthesize is the explicitly
  expensive verb (it says so in its own description), with a best-effort cost block so
  agents choose it deliberately. No API key configured? It says unavailable with a
  fix, never a fake answer.
• Certify any memory server against the contract. gbrain protocol --json publishes
  the machine-readable spec; gbrain protocol conformance [--target <endpoint>] runs the
  frozen-contract test suite against gbrain's own server or any MCP endpoint — and
  provably fails servers that don't comply. gbrain protocol stats shows per-verb
  adoption and your real time-to-first-use, all from a local file that never leaves
  your machine.

gbrain serve keeps every operation by default (--surface full) — existing installs
are unchanged. The new --surface verbs is the quickstart surface for agents. No schema
migration; the verbs ride the existing facts, pages, and typed-graph tables. The full
contract, per-harness install blocks, and the additive-forever versioning policy live in
docs/protocol/MEMORY_VERBS_v1.md.

This release also fixes which search verb your agent reaches for (#2416). The
search and query tool descriptions, the mandatory lookup chain, and the search
guides had drifted from reality: they described search as keyword-only (it has been
cheap hybrid — vector + keyword, no LLM expansion — for many releases) and told agents
to try search first for everything, falling back to query only when results looked
"thin". For concept questions ("all the X that do Y", "the ecosystem around Z") that
fallback never fired, and synonym-phrased matches dropped silently.

• Concept questions now route to query by default. The tool descriptions and the
  lookup-chain convention are intent-driven: exact known tokens → search (cheaper, no
  expansion call); concept / synonym / exhaustive-set questions → query first. Verified
  with a live LLM routing eval: all concept phrasings route to query, and personal
  questions still route to the salience ops.
• "Got results" is no longer treated as "got everything." The descriptions, docs, and
  conventions now say it plainly: a populated search result set is not proof of
  coverage, and query is still top-K — literal exhaustive enumeration belongs to
  list_pages pagination.
• The CLI nudges you when it can help. A concept-shaped gbrain search "..." prints a
  one-line hint on stderr suggesting the equivalent gbrain query call (results stay
  clean on stdout; --quiet silences it; never auto-reroutes).
• think cost accounting reads consistently. When no LLM call ran (stubbed or no
  API key), usage is now uniformly null in --json output rather than sometimes
  missing.

To take advantage of v0.43.0.0: re-run gbrain serve with --surface verbs to give
your coding agent the five-verb memory protocol (or keep --surface full for the
complete operation catalog — both speak the verbs). Run gbrain protocol conformance
to self-certify, and gbrain protocol stats to watch adoption. Memories your agent
saves are readable by every agent connected to the brain by default; pass
visibility: "private" for local-only facts. If your agent instructions or skill
files copy the old "search first, query if thin" rule, refresh them from
skills/conventions/brain-first.md — the shipped skillpack carries the corrected
routing.