Daniele
7e3fa3caad
Against a self-hosted Honcho 3.0.11 every read path came back empty while the server was healthy and full of derived facts: the plugin parsed a `conclusions`/`summary` shape the API no longer emits. - honcho-client: typed models for the real schema — `PeerContext` (`representation` markdown + `peer_card`), `SessionContext` (`summary` as an object, `peer_representation`), wrapped `PeerCard` (a bare array on PUT is a 422, which also broke `honcho_profile` writes). - plugin: the turn-time injection and `honcho_context` read the representation; `honcho_search` and the page's /search now use `conclusions/query` (observer/observed scoping inside `filters`) — a real ranked semantic search with fact ids, which `peer_context?search_query` never provided; /overview returns card + representation + conclusions. - compose: pin the Honcho image by digest (3.0.11) — ghcr publishes no v3 semver tags, and an untracked `:latest` pull is what drifted the schema. - tests: fixture tests from payloads captured on the live server, plus an env-gated live smoke test (HONCHO_E2E_URL/_WS/_PEER, `cargo test -p honcho-client -- --ignored`) — run it before any future Honcho bump.
Skald dev-docs — architectural reference for coding agents. Entry point: ../CLAUDE.md
dev-docs — index
These files hold the design rationale of one subsystem each. They are not loaded into an agent's context automatically: ../CLAUDE.md is, and it names the file to open before touching a given area.
The split criterion is not importance. Everything here is load-bearing — most paragraphs exist to record a trap somebody already fell into ("the obvious alternative is X, and it is wrong because Y"). The criterion is blast radius: a rule a change anywhere can violate stays in CLAUDE.md; the mechanism of one subsystem lives here and is read on entry to that subsystem.
When you change one of these areas, update its file in the same change — same standing rule as docs/ and CHANGELOG.md. A doc written later is written from the diff, which is the version nobody can use.
| File | Read it before touching |
|---|---|
| users-auth-and-boot.md | login, sessions, UserManager, UserContext, per-user DB encryption, what boot unlocks and spawns |
| database.md | any table or accessor under db/, the registry/owner bucket split, memory notes, reports, prompt substitutions |
| filesystem-and-containers.md | container/, the fs-tools, mounts, path routing, skills, the memory signposts, built-in tools |
| projects-and-files.md | projects, shared folders, <file-explorer>, the #files page |
| agent-loop.md | crates/agent-loop/, loop_adapters/, session/handler/, sub-agents, cancellation, restart recovery, the approval gate |
| context-and-compaction.md | compaction, the history window, the cached system-prompt prefix |
| llm-stack.md | LLM clients, providers.yaml, retriability, request logging, token streaming, multimodal attachments |
| mcp-connectors.md | MCP runtimes, connectors, marketplace installs, OAuth, device/QR login |
| plugins.md | plugin visibility, per-user config, HTTP routers, plugin-contributed web pages |
| default-access.md | anything grantable (plugin, connector) and who receives it by default |
| system-agents.md | event triage, the memory lints, the conversation review, their scheduler and settings |
| frontend.md | anything under web/ — components, chat tabs, routing, i18n, theme, the security-group picker |
Two sources of truth sit outside this directory and outrank it:
blueprint/project-family.md— the design document, gitignored and not under version control. Referenced by section number (§0.1, §5.1, §6, §7, §9, §11, §12, §14, §15, §16, §17, §19). Never assume a section says what you remember; open it.../CLAUDE.md— the always-loaded rules: the commit rule, the production/schema constraint, domain neutrality, the event-bus rule, the crate boundaries.