Repository navigation
Release 0.4.0 — layered control plane (overlays, strict load, lazy federation) + CI - #2
Merged
Merged
Conversation
Reconstructed from git history between v0.2.0 (6f22d83) and the v0.3.0 version bump (4f32c24) plus the release_notes.md narrative: rune command schema export, intent-based procedural discovery, JSON-RPC MCP server, federation adapters, OWASP metadata/auditing, and the wairu runtime adapter. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Pytest matrix on Python 3.11/3.12 using the [test] extra, plus a ruff lint job scoped to src/ (tests/ carry pre-existing lint findings that are out of scope here). Pattern follows semantiscan's workflow without the postgres service. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CI installs only `.[test]`, which does not (and should not) pull in llmcore, but tests/unit/test_federation.py imported grimoire.federation at module level, which imports llmcore.observability.federation. That made pytest collection fail with ModuleNotFoundError in every CI matrix entry. Guard the module with pytest.importorskip, matching the existing semantiscan smoke-test pattern, so the suite skips these tests in environments without the optional llmcore ecosystem dependency. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…y federation (0.4.0) Phase 0 of the Darwin/control-plane overhaul (grimoire is becoming THE prompt/tool/skill control plane for llmcore + wairu): - Grimoire.layered(roots): facade over ordered (name, path, writable) layers; every API resolves through the composed view - CompositeRepoView: read-only merged GrimoireRepo over layers for ALL artifact types; duck-type compatible incl. in-memory runtime rune registration (drops on reload by design) - LayeredGrimoire: typed accessors for all artifact types, per-key default_vars merge, resolve_layer(id, kind) - Strict + deterministic loading: sorted discovery (stable duplicate winner); strict=True raises RepoError on parse failure/duplicate id, from_roots names the failing layer; validate(layer=...) for per-layer startup checks - federation.py imports llmcore lazily (PEP 562) + declared grimoire[federation] extra — kills the one import-cycle hazard before llmcore hard-depends on grimoire - Perf: static host/git conjure builtins cached per engine (was 2 git subprocesses per conjure); catalog()/tool_schemas() memoized with invalidate_caches() wired into reload + runtime rune registration - 25 new tests (tests/unit/test_layered_all_types.py); suite green; ruff clean; version 0.4.0 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot stopped reviewing on behalf of
araray due to an error
September 19, 2026 03:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Lands
av/26-july_improvements(4 commits): grimoire 0.4.0 — Layered Control Plane, the release that lets grimoire serve as THE single prompt/tool/skill control plane for llmcore and wairu. Fast-forwards ontomain(no conflicts).Highlights
Grimoire.layered(roots)over ordered(name, path, writable)layers;CompositeRepoViewmerges ALL artifact types (spells, runes, promptlets, rituals, bundles, skilldocs, default vars) and stays duck-type compatible with every consumer (runtime rune registration included).LayeredGrimoiretypedget_*/list_*for every artifact type, per-keydefault_varsmerge,resolve_layer(artifact_id, kind).GrimoireRepo.load(..., strict=True)/LayeredGrimoire.from_roots(..., strict=True)raiseRepoErrornaming the failing layer;Grimoire.validate(layer=...)for startup validation of user overlays.catalog()/tool_schemas()memoized withinvalidate_caches().grimoire.federationimports llmcore lazily (PEP 562) and llmcore lives in thefederationextra, so llmcore can hard-depend on grimoire without an import cycle; federation tests are guarded when llmcore is absent.Version / compatibility
0.3.0 → 0.4.0. Consumers: llmcore 0.52.0 hard-depends ongrimoire>=0.4.0; wairu 0.3.0 pinsgrimoire>=0.4.0,<0.5.Verification
git merge-tree main HEAD→ clean.Notes
🤖 Generated with Claude Code