enola 0.5.4 → 0.5.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8765810bf2e4d590bbbba5be8636b967a32850c114c77062f122f352178f2efd
-  data.tar.gz: 3e5b6fcc384b5a4744be1f691fb219968f407b303e2b3220b2333e0c1e59840f
+  metadata.gz: c9465910b66ac8c461af7a7169f074d55b8c64c7c228dfe4acb81bdf70980731
+  data.tar.gz: f5fcd1f86a3cde157a0dc4ae901b56577f08cb1f8735aa065110bec03ad2254e
 SHA512:
-  metadata.gz: 59ee62e4dce004b6828775875e6c68ed8821744ff47e69181a2d0dbdc0040d3ef46f0466b12b9bbd67fbffe7dc851de9bb3fae388f3a33c9680a51d1be630193
-  data.tar.gz: 327a5ccd99c2842900aaedf773e2d550a756447ffd8990dc883b46c6687922cdb02d45cbf709614d80658a6b957ad75f31dc41924684e75a6851f6a3a696994f
+  metadata.gz: bf9acda456730768553a8489cde1f527989f0d8e35e425fbb74ff20eb265796a8c6d995ad5062dfcb92017017082610b950cc12b5f0d4d7ed919d8dc1f2aa629
+  data.tar.gz: 814dd495e17e04801536643b736143644adac776454e27a076256ae07daccdb1f45cd38b88fe7a10ae784f739ecfb1bcc465cd7a30e05d68c022b2a9455d3dcb

data/CHANGELOG.md

@@ -1,3 +1,72 @@
+## enola 0.5.6 and enola-rb 0.5.6 (2026-10-20)
+
+The enola and enola-rb gems drive upstream enola 0.4.32. Between 0.4.19 and
+here upstream indexed a folder of repositories as a cluster (0.4.20), took dead
+code, performance and package metrics into enola itself (0.4.21), installed as
+a Claude Code plugin (0.4.22), stopped counting loops that cannot grow (0.4.23),
+read FastAPI routes in every registration form (0.4.24), parsed Scala 3
+capture-checked code (0.4.25), linked a cross-repo call to the function making
+it and the one serving it (0.4.26), answered `enola impact` from the command
+line (0.4.27), rested performance findings on facts about the callee (0.4.28),
+walked a Laravel endpoint from its URL to its tables (0.4.29), added `enola
+flows` and a `doc` prop on symbols (0.4.30), bound more routes to their
+handlers and extracted TypeScript about twice as fast (0.4.31), and read docs
+from comments in ten languages, module docs from package comments among them,
+with a `docs.jsonl` renderer on by default (0.4.32). `cacheVersion` moved from v265 to v390, so caches rebuild
+once and a pinned baseline can show a one-time change.
+
+The vendored Prism provider script is re-vendored from v0.4.32. Its body is
+unchanged since v0.4.19 and it still answers provider version 0.2.0; only the
+line naming where it was vendored from moves. The Rubydex engine pin is
+unchanged at 0.4.0, which is what 0.4.32 fetches.
+
+munola is unchanged and still drives channel release `0.4.19.1`, until the
+channel is cut on 0.4.32.
+
+## enola 0.5.5, enola-rb 0.5.5 and munola 0.6.3 (2026-09-14)
+
+The enola and enola-rb gems drive upstream enola 0.4.19. Between 0.4.10 and
+here upstream read GraphQL server schemas so client operations have something
+to match (0.4.12), bound Python imports to the module they name and added the
+import-closure explainer (0.4.13), resolved C++ calls when the short name is
+unique (0.4.13), published pip wheels and lowered the glibc floor to 2.17
+(0.4.14, 0.4.15), stopped constraint checks skipping struct owners and
+knowledge-page components (0.4.16), made the dashboard reload its snapshot on
+refresh and bound Python calls to symbols a package defines in its own
+`__init__.py` (0.4.17), made install.sh POSIX and gave upgrades their own
+checksum (0.4.18), and made the Stop hook report once per session (0.4.19).
+`cacheVersion` moved from v257 to v265, so caches rebuild once and a pinned
+baseline can show a one-time change.
+
+The vendored Prism provider script is re-vendored from v0.4.19. It had stayed
+at provider version 0.1.0, the v0.4.4 script, while upstream moved it to 0.2.0
+in 0.4.5: the seam hands the script a `--files` listing of the paths it holds
+no cache entry for, and the 0.1.0 script parsed the whole tree regardless. The
+Rubydex engine pin is unchanged at 0.4.0, which is what 0.4.19 fetches.
+
+munola 0.6.3 drives channel release `0.4.19.1`, cut from the promoted current
+at upstream enola 0.4.19. Three changes promoted into the channel after
+0.4.10.1 ship for the first time: `enola check -member` grades one repository
+of a multi-repository config against the union pin by replaying it, a
+constraints sentence written in snake_case reaches a recipe published in
+kebab-case, and the module-edges binder keys symbol placement by repository
+and drops its own prior derivations before deriving. Still carried: the
+recipe catalogue at enola-guides v0.3.1, the init role binding, the
+cache-version double history at cacheVersion v265, and the blame.go
+spelling. The config munola writes also stops naming the Prism provider's
+version as a fixed `0.1.0`; it asks the script, as the enola gem's config
+already did.
+
+## munola 0.6.2 (2026-08-30)
+
+munola drives channel release `0.4.10.1`, cut from the promoted current at
+upstream enola 0.4.10. The difference list shrank again by contribution: the
+exclusion filter went upstream in 0.4.7, and the constraints reference this
+channel once carried inside INTENT.md shipped upstream as CONSTRAINTS.md and
+PROVIDERS.md over 0.4.5. What the channel still adds is the recipe catalogue
+at enola-guides v0.3.1, the init role binding, the cache-version double
+history and a readability spelling in blame.go.
+
 ## enola 0.5.4 and enola-rb 0.5.4 (2026-08-30)
 
 The gems drive upstream enola 0.4.10. Between 0.4.6 and here upstream took the

data/README.md

@@ -13,7 +13,7 @@ because nobody installs it to avoid Rails. The Rails code is written once, in
 ## `enola`
 
 The wrapper of the released enola. The gem versions itself; the release it
-drives is `Enola::UPSTREAM_VERSION`, v0.4.4 as of `enola 0.5.0`, and every
+drives is `Enola::UPSTREAM_VERSION`, v0.4.32 as of `enola 0.5.6`, and every
 gemspec summary names it.
 
 ```ruby
@@ -29,7 +29,7 @@ bundle exec enola check .
 The first command that needs the binary downloads the release for your
 platform (linux, darwin, windows; amd64, arm64), verifies it against the
 sha256 file the same release publishes, and keeps it under
-`~/.cache/enola/upstream/0.4.4/` (`ENOLA_CACHE_DIR` moves the root). An
+`~/.cache/enola/upstream/0.4.32/` (`ENOLA_CACHE_DIR` moves the root). An
 `enola` already on your PATH is used only when it answers the pinned version;
 offline with an empty cache is a refusal that names the cache and the release
 rather than a fallback to whatever is installed. Nothing downloads at

data/lib/enola/providers/prism/enola_prism_provider.rb

@@ -1,6 +1,6 @@
 #!/usr/bin/env ruby
 # frozen_string_literal: true
-# Vendored from enola-labs/enola examples/providers/ruby/prism/enola_prism_provider.rb at v0.4.4 (1e35dfd88e7b293bb2bffec6949989bd6105b796), Apache-2.0.
+# Vendored from enola-labs/enola examples/providers/ruby/prism/enola_prism_provider.rb at v0.4.32 (37d74c08a48dfa6092ae5e37cc15edb390f66ec7), Apache-2.0.
 
 # enola Prism reference provider.
 #
@@ -34,7 +34,7 @@
 require "json"
 require "prism"
 
-PROVIDER_VERSION = "0.1.0"
+PROVIDER_VERSION = "0.2.0"
 
 if ARGV.include?("--version")
   puts PROVIDER_VERSION
@@ -42,7 +42,13 @@ if ARGV.include?("--version")
 end
 
 root = ARGV[0]
-abort "usage: enola_prism_provider.rb <repo-path>" unless root && File.directory?(root)
+abort "usage: enola_prism_provider.rb <repo-path> [--files LISTING]" unless root && File.directory?(root)
+
+# With --files the seam hands over the repo-relative paths whose facts it has no
+# cache entry for, one per line; only those are parsed, and every fact still
+# names its file, so the seam can store each file's facts under its own key.
+listing = ARGV.index("--files") && ARGV[ARGV.index("--files") + 1]
+abort "usage: enola_prism_provider.rb <repo-path> [--files LISTING]" if ARGV.include?("--files") && !listing
 
 SKIP_SEGMENTS = %w[vendor node_modules tmp].freeze
 
@@ -167,9 +173,13 @@ class CallCollector < Prism::Visitor
 end
 
 lines = []
-files = Dir.glob(File.join("**", "*.rb"), base: root).reject do |rel|
-  rel.split("/").any? { |segment| SKIP_SEGMENTS.include?(segment) }
-end.sort
+files = if listing
+  File.readlines(listing, chomp: true).reject(&:empty?).select { |rel| rel.end_with?(".rb") }.sort
+else
+  Dir.glob(File.join("**", "*.rb"), base: root).reject do |rel|
+    rel.split("/").any? { |segment| SKIP_SEGMENTS.include?(segment) }
+  end.sort
+end
 
 files.each do |rel|
   source = begin

data/lib/enola/version.rb

@@ -3,6 +3,6 @@
 module Enola
   # The gem versions itself. UPSTREAM_VERSION names the enola release it
   # fetches and drives.
-  UPSTREAM_VERSION = "0.4.10"
-  VERSION = "0.5.4"
+  UPSTREAM_VERSION = "0.4.32"
+  VERSION = "0.5.6"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: enola
 version: !ruby/object:Gem::Version
-  version: 0.5.4
+  version: 0.5.6
 platform: ruby
 authors:
 - Muhamed Isabegovic
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-30 00:00:00.000000000 Z
+date: 2026-10-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: prism
@@ -27,7 +27,7 @@ dependencies:
 description: |
   A pure-Ruby wrapper around enola, the architecture-graph tool by enola-labs.
   The gem versions itself; the enola release it drives is named in its
-  UPSTREAM_VERSION, 0.4.10 here. The binary is not in the
+  UPSTREAM_VERSION, 0.4.32 here. The binary is not in the
   gem: the first command that needs it downloads the release for your
   platform, verifies it against the checksum the release publishes, and keeps
   it in a per-user cache. Every command and exit code is forwarded unchanged.
@@ -81,5 +81,5 @@ rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
 summary: 'Runs the released enola from Ruby: fetched on first use, verified, cached.
-  This release drives enola 0.4.10.'
+  This release drives enola 0.4.32.'
 test_files: []