enola 0.5.3 → 0.5.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7587a8fade69cbde43c50ccf899b2085830d99e05e83feb03c1d31293e0eaedc
-  data.tar.gz: 9d1bc99945a58b925dfeca0a70335907e53f4a47154d26fb5091250bdd353ab1
+  metadata.gz: b51cf9aa67dfbedac9d50b3b497dc1aa4a8cf503a64fbb8005ee229f33e2622d
+  data.tar.gz: 4472e4831653a8b39856ff614c29e453ddbd4a516f81de25ca7b5a6141979d60
 SHA512:
-  metadata.gz: e6baed0ecc468220f0d80d37b40352e4b97889ae17e5049b7b167142d3f1ddd60c2bcd35f77ffe84dcb04493cd00bc7ae3954a879421a3abfb6f88303fab538b
-  data.tar.gz: b39f2adc88525ed513773913d48b07071fd9e4bcf4a2a2fbaf7a1070e6e68a6d88e28271cae2b2ee7266b8f8f62f5ae7c13d8507661af852a3c0759c711624ce
+  metadata.gz: 441a27c23a38787138349ad7a8962d7c1acdc0f0138b6d208e241a22bce2cb4fdda14801ad8a11cf9de5f5d40d3f4f7cf39f037776692694259cb5808327094d
+  data.tar.gz: 3a92d8fcaaba9073b9bb606b45f64d1fe272a37e6550e9d295fc37d464db63e75c205727a473407f65e7e3a4e792623a316afaac7fdb0afa3f56a1add5660cb4

data/CHANGELOG.md

@@ -1,3 +1,76 @@
+## 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
+exclusion filter (#255, in 0.4.7), rescored the layers explainer per language
+cohort (0.4.7), began reading package manifests as dependency facts with a
+declared-purpose diff (0.4.8), gave the dashboard its own command (0.4.9), and
+documented the snapshot artifacts as a versioned contract with fact identity
+(0.4.10). The vendored Prism provider script and the Rubydex engine pin are
+byte-identical across the span, so nothing re-vendors; the wrappers move by
+the release they name.
+
+## munola 0.6.1 (2026-08-24)
+
+munola drives channel release `0.4.6.1`, cut from the promoted current at
+upstream enola 0.4.6. The prefix walk fix is in the binary this gem fetches,
+so the expiry the 0.6.0 note named is met and Rubydex is on by default again.
+The channel still carries the exclusion filter, which upstream merged an hour
+after 0.4.6 was published, so an excluded document is skipped before its
+definitions are read: 440 seconds to 193 on a Rails monolith, facts identical.
+
+The 0.6.0 note said munola waits on Prism alone. On the Rails install path it
+did not. `munola init` reuses enola-rb's installer, which writes
+`mcp-arch.yaml` first, and munola's own writer yields to a file that already
+exists, so the config every Rails project got was the enola gem's, with both
+providers on, against a channel binary built before the fix. Two things follow.
+The config and the binary now agree, which is what closes it. And munola's
+writer has a test that reads munola's writer, rather than one that reads the
+file enola-rb wrote and reports on munola.
+
 ## enola 0.5.3, enola-rb 0.5.3 and munola 0.6.0 (2026-08-24)
 
 Both providers are on again. enola-labs shipped the prefix walk fix in 0.4.6,

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.19 as of `enola 0.5.5`, 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.19/` (`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.19 (f34e1998d5c41eeeb14e95f6c3584b8fee0746c6), 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.6"
-  VERSION = "0.5.3"
+  UPSTREAM_VERSION = "0.4.19"
+  VERSION = "0.5.5"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: enola
 version: !ruby/object:Gem::Version
-  version: 0.5.3
+  version: 0.5.5
 platform: ruby
 authors:
 - Muhamed Isabegovic
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-24 00:00:00.000000000 Z
+date: 2026-09-14 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.6 here. The binary is not in the
+  UPSTREAM_VERSION, 0.4.19 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.6.'
+  This release drives enola 0.4.19.'
 test_files: []