munola 0.6.2 → 0.6.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f9aaf4515e419373749156b376859f5385d8770bd6c3f6c4954f483008dd7594
-  data.tar.gz: 86f089c88a6fb0b843e91b10cc1c3e88d897198f8a9f1fa81764a265fce3733e
+  metadata.gz: 9d0769301017f5ed54e67058529b940ded629e3d5d779b13eec3337db05078e6
+  data.tar.gz: 5c5ac5828b84e3fb36128bc0fb93e9aa61c3825ba30af6a1c94ca2b60a373f8f
 SHA512:
-  metadata.gz: 640e95eea31e3cb19b93c1af6bd9351e8411ab7093d42713dba0f920cf4851c74ec144d64a08e01d5aa5b9863940b9a1d888708687dfb2c9cdfc37b20f4c0012
-  data.tar.gz: e09afd9a96fba881ae389297f43447b4a6909f4e297f688a91d78ccb63747457773debdbe477ace4a6beaf5d00622712b361af6ebccfe1a98bde8e8d88797f5a
+  metadata.gz: b4a4634b0cdd1eda32d0d40c68e577b6c287bc95f4a5bf21fd89a5d952b71731580bd935102dbd5a9ec9a2e1c084d7da16dee0e21d639944a0cdd3157a9813d0
+  data.tar.gz: 95479941d69ca41b0447240bd9a4024a140ee106f7f3d5078bb2b964e59e339c13da07428c0a5a2355da40f0aac7f08f1d1d82c6adcf79f03409c1f78e71ba20

data/CHANGELOG.md

@@ -1,3 +1,75 @@
+## munola 0.6.4 (2026-10-20)
+
+munola drives channel release `0.4.32.1`, cut from the promoted current at
+upstream enola 0.4.32 and published on misabegovic/enola as
+`munola-v0.4.32.1` (five platforms with checksums and a `version.json`). Its
+notes name 32 differences from upstream 0.4.32, among them the recipe
+catalogue at enola-guides v0.3.1 and the init role binding, the member check,
+the providers mode, the built-in prism provider and the larger MCP surface.
+
+The Rubydex version the config writes moves from 0.4.0 to 0.4.1, the library
+the 0.4.32.1 channel fetches. A config naming 0.4.0 would have the binary skip
+the provider for a version mismatch, silently.
+
+## 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

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/munola/providers_config.rb

@@ -9,7 +9,7 @@ module Munola
   # written once, never rewritten; the Rubydex library is fetched after the
   # binary, and a fetch that fails is a named skip, never a silent absence.
   module ProvidersConfig
-    RUBYDEX_VERSION = "0.4.0"
+    RUBYDEX_VERSION = "0.4.1"
 
     def self.write(root, ruby: RbConfig.ruby)
       path = File.join(root, "mcp-arch.yaml")
@@ -23,7 +23,7 @@ module Munola
       lines = ["repo: .", "repos:", "  - .", "providers:"]
       script = prism_script
       if script
-        lines += ["  - name: prism", "    command: [#{ruby.inspect}, #{script.inspect}]", "    expected_version: \"0.1.0\""]
+        lines += ["  - name: prism", "    command: [#{ruby.inspect}, #{script.inspect}]", "    expected_version: #{prism_version.inspect}"]
       else
         lines << "  # prism: the enola gem on this machine carries no provider script; add one here to run it"
       end
@@ -31,6 +31,11 @@ module Munola
       "#{lines.join("\n")}\n"
     end
 
+    def self.prism_version
+      version = Enola::Providers.prism_version if Enola::Providers.respond_to?(:prism_version)
+      version || "0.2.0"
+    end
+
     def self.prism_script
       return nil unless defined?(Enola::Providers) && Enola::Providers.respond_to?(:prism_script)
 

data/lib/munola/version.rb

@@ -3,7 +3,7 @@
 module Munola
   # UPSTREAM_VERSION names the enola release this channel is built on,
   # CHANNEL_VERSION the fork release the gem fetches.
-  UPSTREAM_VERSION = "0.4.10"
-  CHANNEL_VERSION = "0.4.10.1"
-  VERSION = "0.6.2"
+  UPSTREAM_VERSION = "0.4.32"
+  CHANNEL_VERSION = "0.4.32.1"
+  VERSION = "0.6.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: munola
 version: !ruby/object:Gem::Version
-  version: 0.6.2
+  version: 0.6.4
 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: enola
@@ -56,8 +56,8 @@ description: |
   The binary this gem fetches is not an enola-labs release. It is a build
   cut from https://github.com/misabegovic/enola, a fork of enola, whose
   release notes name what differs from upstream release by release; this
-  gem drives channel release 0.4.10.1, built on enola
-  0.4.10. Everything else is the enola gem's wrapper,
+  gem drives channel release 0.4.32.1, built on enola
+  0.4.32. Everything else is the enola gem's wrapper,
   unchanged: fetched on first use, verified against the checksums the
   release publishes, cached per user, every command and exit code
   forwarded. Use the enola gem to run stock upstream instead.