@suss/adapter-ruby 0.10.0 → 0.12.0

package/README.md

@@ -6,7 +6,7 @@ Ruby language adapter for suss. It parses source with tree-sitter (WASM), resolv
 
 `@suss/adapter-ruby` is the Ruby language adapter, per [`docs/internal/facts-and-rules.md`](../../../docs/internal/facts-and-rules.md)'s Layer 1 contract: discover units, emit summaries in the shared IR, emit facts. It parses a file with `web-tree-sitter` and a vendored Ruby grammar (`grammar/tree-sitter-ruby.wasm`, no native build step), tracks class/module nesting to qualify a constant the way Ruby itself would resolve it lexically, and discovers graphql-ruby's class-based `field` DSL on a class extending a pack-configured base class. A `field :x, mutation: Mutations::Y` or `field :x, resolver: Queries::Z` reference is followed one hop: the referenced class's own file is located by Rails' constant-to-path convention and read for its declared return type. Discovered units become `RawCodeStructure` objects handed to `@suss/extractor`'s `assembleSummary`, the same assembly code the other adapters use.
 
-v0 (this slice) reads graphql-ruby only: `routes.rb` is a separate, much larger macro-expansion problem, which the [language-adapters proposal](../../../docs/internal/proposals/language-adapters.md) costs out and leaves for later. `require` is not resolved; class and module nesting is. A resolver's transitions are always empty (`branches: []`), since v0 does no path-engine work, and confidence is pinned low.
+v0 (this slice) reads graphql-ruby only: `routes.rb` is a separate, much larger macro-expansion problem, which the [language-adapters proposal](../../../design/proposals/language-adapters.md) costs out and leaves for later. `require` is not resolved; class and module nesting is. A resolver's transitions are always empty (`branches: []`), since v0 does no path-engine work, and confidence is pinned low.
 
 ## The method behind a field
 
@@ -26,7 +26,7 @@ What the summary then says:
 - When the walk reads a field's whole ancestry and finds no such method, `bodyContent` stays `"absent"` and the summary keeps its no-body sentence. That is right for such a field, because the library gets its value by reading the attribute off the object the field was resolved against.
 - When the walk stops early, `bodyContent` stays unset and the summary gets one sentence saying what stopped it: an ancestor whose file the convention cannot locate, a `define_method` call that defines methods a reader of `def` nodes cannot see, or a wiring value that is not a constant path. `bodyContent` stays unset because the extractor writes its own sentence from that field, and any value would be a claim this reader cannot make. The walk does not read `method_missing` either.
 
-An ancestor the reader could not open stops the search, rather than the search carrying on to a method further along. Ruby would have called whatever that ancestor defines, so a method found past it is not the one that runs, and reporting it would be a confident wrong claim instead of an abstention.
+An ancestor the reader could not open stops the search, rather than the search continuing to a method further along. Ruby would have called whatever that ancestor defines, so a method found past it is not the one that runs, and reporting it would be a confident wrong claim instead of an abstention.
 
 What a body does still goes unread. Reading it needs the path engine: statements to walk, a return value to turn into a shape, and calls to resolve against something that knows what they return. `RawCodeStructure.dependencyCalls` is no shortcut around that, because nothing in the summary assembly reads it. A field's location also stays where the field is declared rather than moving to a resolver method in another file, so the path and line numbers on a summary keep pointing at the same place.
 

package/dist/index.cjs

@@ -15296,7 +15296,7 @@ function date4(params) {
 // ../../../node_modules/zod/v4/classic/external.js
 config(en_default());
 
-// ../../ir-core/dist/chunk-HBAMPBAO.js
+// ../../ir-core/dist/chunk-AQYS5AC6.js
 function gqlIdentityKey(typeName, fieldName) {
   return `gql:${typeName}.${fieldName}`;
 }
@@ -15598,6 +15598,9 @@ function normalizePath(path4) {
   );
   return normalized;
 }
+function pathShape(path4) {
+  return normalizePath(path4).replace(/\{[^}]*\}/g, "{}");
+}
 function methodsAgree(a, b) {
   if (a === null || b === null) {
     return false;
@@ -15649,12 +15652,17 @@ var restSemantics = defineBoundarySemantics({
      * settles it inside the bucket. The identity key stays what a reader
      * sees and a suppression targets ("GET /users", "* /users"), and
      * this key groups what a reader still tells apart.
+     *
+     * A parameter's name goes too. A spec written by hand says
+     * `{userId}` where the Express route that serves it says `:id`, and
+     * both match the same requests, so pairing on the name gave two
+     * boundaries that never met and a run with nothing to report.
      */
     pairingKey(semantics) {
       if (semantics.method === null || semantics.path === null) {
         return null;
       }
-      return `rest ${normalizePath(semantics.path)}`;
+      return `rest ${pathShape(semantics.path)}`;
     },
     sidesAgree(a, b) {
       return methodsAgree(a.method, b.method);

package/dist/index.js

@@ -15245,7 +15245,7 @@ function date4(params) {
 // ../../../node_modules/zod/v4/classic/external.js
 config(en_default());
 
-// ../../ir-core/dist/chunk-HBAMPBAO.js
+// ../../ir-core/dist/chunk-AQYS5AC6.js
 function gqlIdentityKey(typeName, fieldName) {
   return `gql:${typeName}.${fieldName}`;
 }
@@ -15547,6 +15547,9 @@ function normalizePath(path4) {
   );
   return normalized;
 }
+function pathShape(path4) {
+  return normalizePath(path4).replace(/\{[^}]*\}/g, "{}");
+}
 function methodsAgree(a, b) {
   if (a === null || b === null) {
     return false;
@@ -15598,12 +15601,17 @@ var restSemantics = defineBoundarySemantics({
      * settles it inside the bucket. The identity key stays what a reader
      * sees and a suppression targets ("GET /users", "* /users"), and
      * this key groups what a reader still tells apart.
+     *
+     * A parameter's name goes too. A spec written by hand says
+     * `{userId}` where the Express route that serves it says `:id`, and
+     * both match the same requests, so pairing on the name gave two
+     * boundaries that never met and a run with nothing to report.
      */
     pairingKey(semantics) {
       if (semantics.method === null || semantics.path === null) {
         return null;
       }
-      return `rest ${normalizePath(semantics.path)}`;
+      return `rest ${pathShape(semantics.path)}`;
     },
     sidesAgree(a, b) {
       return methodsAgree(a.method, b.method);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@suss/adapter-ruby",
-  "version": "0.10.0",
+  "version": "0.12.0",
   "type": "module",
   "description": "Ruby language adapter for suss, parsing source with tree-sitter (WASM), resolving constant nesting with a lexical binder, and emitting raw extractions for the suss pipeline.",
   "keywords": [
@@ -47,9 +47,9 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@suss/behavioral-ir": "0.10.0",
-    "@suss/datalog": "0.10.0",
-    "@suss/extractor": "0.10.0",
+    "@suss/behavioral-ir": "0.12.0",
+    "@suss/datalog": "0.12.0",
+    "@suss/extractor": "0.12.0",
     "web-tree-sitter": "^0.26.11"
   },
   "devDependencies": {