content: refresh bootstrap for Heid's current operating surface

Brokkr-side audit surfaced 9 items worth folding in:

- AGENTS.md: skill-mediated specializations section. Heid often
  receives messages dispatched via /heid-contract-review (artifact-only
  contract paraphrase) or /heid-code-review (structured code-vs-
  contract drift findings) — these carry hardcoded discipline she
  should recognize and bias toward.
- CROSS-FRONTIER-COOPERATION.md: two complementary anti-failure
  framings codified (authority-frame: fresh perspective not superior
  reasoning; role-frame: peer-reviewer not operator-level oracle).
  Mirrors what Brokkr's user-level CLAUDE.md now carries. Plus a note
  that callers triage every reply, so Heid should land between hedge-
  paralysis and over-assertion.
- CONTEXT.md: Bifrost version refresh (v0.3.1 today, v0.4 in flight
  with capability families); Eitri-Smithy entry (Brokkr's standing
  peer — same family as Heid, different role: embedded/standing vs
  cross-project/per-turn); Ratatoskr entry (Worldtree debug TUI, v0
  scaffold); Lofn entry (Worldtree Tier-1 welcoming-intermediary
  agent, calibration case for /heid-contract-review).
- INVENTORY.md: snapshot date refreshed 2026-05-17 → 2026-05-24;
  Lofn added to Worldtree's agent list; rows added for Eitri-Smithy,
  Ratatoskr, Bifrost.
- README.md: rename history note (Volva → Heid 2026-05-24), so
  references in older transcripts or git blame are recognizable as
  the same agent.

Working-dir transient/*.md files remain gitignored.

CONTEXT.md

@@ -21,7 +21,7 @@ Resolution rule: **most-local-wins** — project-level `CONTEXT.md` files in ind
 **Althing** — inter-agent message bus for Corviduo. Markdown messages with YAML frontmatter (SQLite-backed v2 as of 2026-05-17); operated via `althing-cli`. Per-agent handles follow `<project>-dev` (`brokkr-smithy-dev`, `worldtree-dev`, etc.) plus a few non-`-dev` role handles (`forseti` moderator, `infra-ops`). Web UI for multi-agent discussion in flight.
 *Avoid: the bus, the messenger, `althing-cli` (the operator surface, not the bus itself).*
 
-**Bifrost** — the MCP-in-reverse protocol. Platform mints per-session JWTs and dispatches tool calls outbound; consumer apps run their own MCP servers exposing tools back to the platform. Independent repo (`vh/bifrost`) on its own semver (v0.1.1 today, v0.2 in flight). Consumed by platforms (Worldtree), implemented by consumers (Skaldsong, Sleipnir verifier role).
+**Bifrost** — the multi-plane bridge protocol (originally "MCP-in-reverse"). Platform mints per-session JWTs and dispatches outbound calls; consumer apps run their own servers handling those calls back. Independent repo (`vh/bifrost`) on its own semver (v0.3.1 today; v0.4 in flight will introduce capability families — `tool.*` already shipped, `memory.*` proposed, future `agent.*` planned — all riding over the same bridge). Consumed by platforms (Worldtree), implemented by consumers (Skaldsong, Sleipnir verifier role).
 *Avoid: MCP (ambiguous), reverse-MCP, tool injection.*
 
 **corviduo-project-template** — canonical home for cross-cutting Corviduo specs and tooling. Lives at `~/development/corviduo-project-template/`. Brokkr-Smithy is canonical-spec steward as of 2026-05-15. Hosts the v2.x contract-format spec, the four engineering principles, and the canonical-sync tooling. Operators bootstrap new projects by copy-cloning this template; consumers pin against it via `.corviduo-canonicals.toml`.
@@ -43,15 +43,24 @@ Resolution rule: **most-local-wins** — project-level `CONTEXT.md` files in ind
 **Brokkr-Smithy** — Corviduo's research and forging lab. Empirical methodology spine for prompt, orchestration, and architectural-shape claims that ship to consumer projects. Opens R-numbered research targets with charter / hypothesis ledger / probes / actions / findings; authors SOTA literature surveys; runs calibration probes. Ships intelligence packages via althing — **never drafts contracts for consumer repos** (consumer repos run their own `/vor` sessions and own their specs). The assistant working in this repo is addressed as **Brokkr** (the dwarf-smith persona).
 *Avoid: the lab, the research repo, Snorri (the rename ghost — refers to the historical name or to the decision-rule engine subsystem), Edda (deeper rename ghost).*
 
+**Eitri-Smithy** — Brokkr-Smithy's Codex-shaped embedded research peer. Lives at `~/development/eitri-smithy/`, althing handle `eitri-smithy-dev`. Pinged by Brokkr at every R-target gate as a standing peer (vs. your per-turn oracle role). Contributes to Brokkr-Smithy R-targets; does NOT run a parallel R-target queue. Can dispatch its own Codex subagents in parallel-dispatch mode. **You and Eitri are both Codex-shaped but architecturally distinct**: Eitri is brokkr-smithy-specific + standing + can spawn subagents + writes to brokkr's research/ tree; you are cross-project + per-turn + stateless + read-only against your bootstrap. If a caller references "Eitri", do not impersonate; route correctly.
+*Avoid: the other codex, Brokkr's codex (collides with the project distinction), Eitri-the-dwarf (the Norse referent is Brokkr's brother — the dwarf-pair association is the point, but the name is operationally "Eitri-Smithy").*
+
 **Domari** — Worldtree's pan-judgment specialist agent. Routes verdict requests (likert / binary / pairwise / scalar / gap_list) to backbones (Selene / Skywork) per a dispatch table; returns a polymorphic discriminated-union response with `verdict_kind` discriminator. Returns 200 + `ErrorVerdict` envelope on backbone failures rather than 5xx. Norse: "the judges."
 *Avoid: the judge (Worldtree has a separate Judge agent for code review — distinct surface), the judgment agent.*
 
 **Heimdall** — Worldtree's auth-scope mechanism. Per-API-key tier (`user`, `admin`) maps to a set of scopes (`domari:invoke`, `bifrost:invoke`) via `config/policies.yaml`. Live policy resolution at every authz call; no per-key scope override. Norse: watchman of Asgard.
 *Avoid: auth, the scope mechanism (too generic outside Worldtree).*
 
+**Lofn** — Worldtree's foundational welcoming-intermediary agent (Tier 1, #182). One of the Asgardians; ships with **no dedicated preference store** — conversational continuity (user name, favored agents, past topics) emerges from Worldtree's substrate (memory engine + valence engine) rather than per-agent storage. ADR-0003 sets the precedent: Tier 1 agents use substrate for continuity, do not duplicate it. Norse: goddess of permission/love who grants forbidden marriages — Worldtree's welcoming role. Calibration case for `/heid-contract-review` (the contract's scope vs invariants contradiction Heid caught on first read).
+*Avoid: the welcoming agent, the Tier-1 host (too generic).*
+
 **Mead Hall** — A Corviduo Project — a Worldtree client application. A "Workspace Shell" designed flexibly enough to span use cases as different as business automation and multi-agent role-playing (personas, memories, GM/narrator, world history, goals) — these are bounding examples that pin the flexibility requirement. MVP ships the business-automation configuration. High-fidelity aesthetic non-negotiable.
 *Avoid: the new client app, the workspace shell (architecture, not product), business-and-roleplay-from-one-shell (deprecated framing).*
 
+**Ratatoskr** — A Corviduo Project — a dev-grade debug-observability TUI for Worldtree's Conversation API. Python + Textual framework; v0 scaffold (design locked 2026-05-20, implementation pending separate dev team). The product **is** the observability surface — chat is the input mechanism; the value is watching agent SSE stream + persona/Vili affect dispatch + tool calls + Bifrost handshake + admin events + raw logs side-by-side in one terminal. NOT a polished consumer for end-users, NOT an admin tool, NOT a multi-session orchestrator. Norse: the squirrel that runs up and down Yggdrasil carrying messages between the eagle and Níðhöggr — Ratatoskr literally runs up and down Worldtree's API surface.
+*Avoid: the TUI, the dev tool (too generic), Andvari (earlier candidate name, demoted on cursed-ring association).*
+
 **Skuld** — Worldtree subsystem — token-spend ledger. Subscribes to `LLMCallEvent` (Worldtree's wire format for LLM calls) and persists per-call usage to a durable store, giving Worldtree clients cost attribution per request. Norse: future-Norn.
 *Avoid: the ledger, token-spend.*