astria 1.0.6: documents you can actually search
1.0.6 makes document and transcript corpora fully searchable for the first time, and brings three more MCP surfaces to the CLI. Install or upgrade with npm install -g @nodesify/astria.
Chunked document retrieval
Markdown, plain-text, and RST bodies used to enter the graph as headings only — the prose in between was discarded, so long documents and conversation transcripts were effectively unsearchable. 1.0.6 chunks document bodies into ~1,200-character nodes (overlapping ~180 characters across boundaries so evidence is never split), each carrying its full text, its covered line range (span: L14-L18), and a real embedding input. ASTRIA_CHUNK_CHARS tunes the size.
On the LoCoMo long-conversation benchmark (1,977 evidence-backed questions, structural — no LLM, no embeddings), evidence-file recall@10 went from 0.2% to 84.5% and MRR to 0.717. The conversational-memory weakness reported in 1.0.5 is the change this release is about.
Ranking
Chunked prose now ranks on multi-term coverage instead of first-line luck: the transcript turn that actually answers the question outranks a speaker line that merely contains one question word. Chunks are their own node type and rank under code and documents on code-majority repositories, so the self-corpus golden set holds at 78.6% recall@5 / 82.9% hit@5 (MRR 0.618) against Graphify v0.9.69's 65.7%. ASTRIA_EMBED=off (or astria query --no-embed) opts out of query-time embedding seeds.
Agent surfaces
astria god-nodes,astria communities,astria neighbors <node>bring the MCP introspection tools to the CLI.--jsonon the query family (query,map,explain,path,affected,stats,status) for scripts.astria statusreports graph build provenance — which CLI built it, under which extraction rules, and whether it is stale.
What enrichment does and does not buy
A paired experiment on the Click corpus, one shared OpenRouter model, ran astria's --deep against Graphify's extract --mode deep. The deep passes cost $0.12 and changed retrieval scores not at all for either tool — code questions are answered by exact symbols, not semantic associations. Details and the reproducibility path are in the retrieval validation; structural stays the default, and enrichment is best viewed as a document-heavy-corpus feature.
See the changelog for the full list. After upgrading, run astria update . once — extraction rules bumped to v10, so documents re-extract with the new chunking.