@@ -4,6 +4,7 @@ Full release notes with details on each version: [GitHub Releases](https://githu
 
 ## 0.9.63 (2026-09-16)
 
+- Fix: the `/graphify` skill's `--no-cluster` and `--force` flags are now actually implemented instead of being referenced but never wired through. Step 2 suggested `--no-cluster` for a flat corpus and the shrink-guard error message suggested `--force`, but Step 4 called `cluster()` unconditionally and `to_json()` never received `force=`, so neither flag could do anything. Step 4 now builds a single "Full Corpus" community instead of clustering when `--no-cluster` is given, both `to_json()` calls honor `force=`, and Step 5's labeling is skipped when there is nothing to label (#1619, thanks @edtrackai).
 - Feature: Elixir `alias`/`import`/`require`/`use` targets now resolve onto the module's `defmodule` node across files, so the internal module dependency graph is no longer dropped as dangling. Only top-level modules are indexed (a nested `defmodule`, labeled with its bare inner name, cannot capture an unrelated `use <Name>` from another file), and a same-file reference is left unresolved so it cannot clobber the structural `contains` edge (#3603, thanks @ayushcodes10).
 - Feature: a Rust `self.method()` call now resolves to a method defined on the same type in another file (the common split-`impl`-block layout), pooling methods across every `impl` of one type and refusing to link when two unrelated types share a bare name (#3602, thanks @ayushcodes10).
 - Feature: a Ruby member call `obj.foo` on a known-type receiver now resolves to a method `foo` inherited from a superclass, including across files, using the same conservative promotion as the implicit-self resolver — a single owning class, matching method kind, and one unambiguous ancestry chain, or it stays dangling (#3585, thanks @oleksii-tumanov).