Repository navigation
v0.10.0
MOOSEDev v0.10.0
v0.10.0 introduces Story mode, trusted CodeEntity source views, and LLM narration safeguards.
Highlights
Story mode
The workbench can now turn an entity or topic's connected project knowledge into a cohesive, evidence-backed Story. Stories include deterministic chronology, lifecycle-aware evidence, code anchors, explicit knowledge gaps, and symbolic comprehension checks.
Story works without an LLM. A configured OpenAI-compatible model can polish the narration, while the graph-selected evidence, chronology, gaps, and checks remain under symbolic control. Generated Stories can be saved as draft or published recipes; recipes contain presentation metadata and references, not authoritative project claims.
Trusted CodeEntity context
CodeEntity record pages now show indexed signatures, locations, and bounded source previews, with links from knowledge-bearing editor hovers into the exact entity's Story.
Source text is served only when the current index can prove its file and definition location. Stale, changed, out-of-repository, or otherwise unverifiable source is withheld with a reindex explanation rather than approximated.
Code-knowledge hygiene
Batch minting and comprehension-debt coverage now exclude public struct fields, whose rationale normally belongs to their containing type. moosedev mint also reports live but out-of-scope CodeEntities explicitly.
A conservative offline pruning example is included for removing only out-of-scope entities that are both unannotated and unreferenced.
Ontology-vector storage now matches the current MOOSE layout. Derived vector caches carry an explicit schema stamp and rebuild automatically when stale, unstamped, incompatible, or based on different ontology/model inputs.
Compatibility
No MCP tools or existing HTTP routes were removed. Story and trusted-source HTTP routes are additive, and existing record and debt responses gained additive fields.
Rust code embedding the moosedev crate should note:
LlmConfig::from_env()now returnsanyhow::Result<LlmConfig>.LlmConfiggainedcontext_window_tokensandstructured_output.MintPlangainedout_of_scope.- Invalid
MOOSEDEV_LLM_CONTEXT_WINDOW_TOKENSorMOOSEDEV_LLM_STRUCTURED_OUTPUTvalues now fail startup. - Parsers that consume the human-readable mint summary must tolerate its appended
out-of-scope=field.
Upgrading
Re-run the code index to enable trusted source previews and current Story line anchors:
moosedev indexOntology-vector caches require no manual migration; MOOSEDev rebuilds incompatible caches automatically.
Story recipe schemas v1 and v2 remain readable without modifying their files. The next successful save migrates a recipe to schema v3.
Source maintainers with the private MOOSE sibling checkout can optionally clean up CodeEntities left by an older mint scope. Stop the daemon and review the supplied dry run before applying any deletion:
cargo run --release --locked --example prune_out_of_scope_code_entities
cargo run --release --locked --example prune_out_of_scope_code_entities -- --applyThe prune retains every referenced or annotated entity.
What's Changed
- New approve-spec skill and such. by @rhinoman in #20
- NeSy 2026 paper benchmark support by @rhinoman in #21
- Updates to work with MOOSE 0.8.0 changes by @rhinoman in #22
- Story mode by @rhinoman in #26
Full Changelog: v0.9.0...v0.10.0