Repository navigation
Releases
0.9.0
Checked against enola v0.4.35, and read again as someone who has never
heard of enola: a developer landing on the README, one following guide 01
literally on a Python service, and a tech lead deciding whether to adopt
it. What they tripped on is fixed, and every command it changed was run
against v0.4.35.
- The README says what enola is and how to install it before anything
else, and groups the guides into tracks: new to enola, your stack, laws
and CI, agents, deeper, and an optional knowledge-base track. - Three new guides. 00, what enola is: the
pieces, a glossary, who makes what, and enola beside linters and
dependency-rule tools. 19, rolling out:
measured costs (Mastodon and a 20,000-file Rails monolith), one recipe
instead of five, report then enforce, owners, what to commit, turning
it off. 20, reading a verdict: every
section and exit code, partial and declined, the surprises. - Guide 01: install pinned through
pipx, the npmenolawarning, the
MCP server registered withalwaysLoad,doctorbefore a restart, a
first law in YAML that fires on any layout with the output it gives,
and why a first.rblaw in a repository with no Ruby makes the verdict
partial and grades an old breach as new. - Guide 04: modes as a table with the confidence each reports at; fix,
exempt, suppress or leave in the baseline, with the syntax in Ruby and
YAML; a recipes section;checkneeds a pinned baseline. - Guide 05: the action pinned with
version:, Rubydex installed pinned;
the template's variables, requirements, exit codes and comment. - Guide 06: registering the MCP server per agent, what the agent does
differently, v0.4.35's narrower search refusal and folder-of-repositories
install, what to commit (the hooks carry an absolute path) and how to
turn each piece off. templates/enola-check.sh: a regression under enforcement is a verdict
with a comment, not "did not run"; the confidence floor stays at 1.00 so
advisory laws never fail; a shallow clone fails on CI instead of passing
quietly; the comment is edited by its numeric id; without Ruby the
comment is enola's own summary;.enola-versionpins the release.
script/test-check-templatecovers each.- The knowledge-base hooks leave a repository with no decision records
alone (ENOLA_DECISION_DIRS) and are wired from.claude/hooks/, where
enola-guides copywrites them. The five knowledge-base skills call a
wrapper that now ships,templates/kb/kb, tested byscript/test-kb.
examples/knowledge-base's cluster config parses on v0.4.35. - Fixed: the
enola --generate . && enola check .line in guide 02, the
skills and the twenty-six law READMEs fails with no pinned baseline;
constraints initbinds a recipe only when every role has a directory;
a Rubyvia:keyword on a sentence is dropped (writevia :importsin
the law);enola gctrims the local history; the Ember recipe is copied
withenola-guides copy, notgem contents; undefined names (munola,
the brain) are gone;list recipesno longer lists the recipes README. - What v0.4.35 still reads less than the code, each re-checked: an
Expressrouter.post("/")under a mount, an inline Axum.nest, a
bare Cargo version read as pinned, an inline TypeScript handler,
layered'sdepends_onrules on Python, TypeScript, Go and Rust, and a
Rubywhere:value that is not a string. - tabula and taha are marked as a preview: neither is public yet.
script/check-linkschecks#anchorstoo.
0.8.0
One command, enola-guides, in every ecosystem: RubyGems, npm, PyPI,
crates.io, Go and Homebrew, and binaries for Linux, macOS and Windows on
the GitHub release. list, show and copy read one catalogue,
bundle/bundle.json, generated from the tree by script/bundle: 74 items
across guides, examples, laws, skills, hooks, recipes and templates. The
five implementations (Go, Rust, Node, Python, Ruby) are held to the same
22 cases, byte for byte, by script/test-clis, and CI runs them against
each package as installed from the artifact a release would publish, and
installs the Homebrew formula from a local tap. VERSION is the one
version; a tag vX.Y.Z publishes everywhere through trusted publishing
(RELEASING.md). A NOTICE names enola. CONTRIBUTING.md, SECURITY.md,
a code of conduct, issue and pull-request templates and Dependabot for the
actions and the crate; script/test runs every check CI runs that needs
no registry.
0.3.1
The recipes README says where the catalogue ships: built into munola, written by munola init; the upstream channels carry upstream's built-ins only.
0.3.0
The recipe catalogue munola binds: data-ownership, api-boundaries, background-work and the tenant-foreign-key template beside ember-conventions, each law an existing enola form with the number it held at on a real monolith; every file lints clean bound to a Rails tree.
0.2.1
enola v0.4.4 released the constraints program the guides describe; the README says released rather than landing and the start guide names v0.4.4 as the minimum.
0.2.0
What a knowledge base gets: guides 09-12 (a knowledge base with enola, hooks, the skills as they run, the wrapper), four hook templates, five skills (deepdive, ingest check, drift, citation hygiene, zoom out), and a worked example knowledge base.
0.1.2
One law per file: the Rails shop, the cluster laws, the maintenance-task laws and the starter each put every law in a file of its own that declares the parts it speaks about.
Since 0.1.0: eight guides, two worked examples, the laws catalogue (twenty-six declarations, one directory each), four agent skills, the CI check template and its renderer, a cluster configuration, and the recipes. Written against the release of enola that carries the constraints vocabulary (enola-labs/enola#247). On rubygems as enola-guides 0.1.2.