pi-readseek 0.10.7 → 0.11.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-readseek",
-  "version": "0.10.7",
+  "version": "0.11.1",
   "description": "Pi extension for LINE:HASH-anchored file operations and structural code navigation",
   "type": "module",
   "exports": {
@@ -39,8 +39,8 @@
     "node": ">=20.0.0"
   },
   "dependencies": {
-    "@jarkkojs/readseek": "^0.10.7",
-    "@jarkkojs/readseek-api": "^0.10.7",
+    "@jarkkojs/readseek": "^0.11.1",
+    "@jarkkojs/readseek-api": "^0.11.1",
     "diff": "^9.0.0",
     "xxhash-wasm": "^1.1.0"
   },

package/prompts/{edit.md → edit_text.md}

@@ -1,7 +1,7 @@
 Edit existing text files with fresh `LINE:HASH` anchors. Read or search the file first when no fresh anchors are available. Each `edits[]` item must use exactly one nested object: `{"set_line":{"anchor":"LINE:HASH","new_text":"..."}}`, `{"replace_lines":{"start_anchor":"LINE:HASH","end_anchor":"LINE:HASH","new_text":"..."}}`, `{"insert_after":{"anchor":"LINE:HASH","new_text":"..."}}`, `{"replace_symbol":{"symbol":"name","new_body":"..."}}`, or `{"replace":{"old_text":"...","new_text":"..."}}`.
 
-Anchors come from `readSeek_inspect`, `readSeek_grep`, `readSeek_search`,
-`readSeek_refs`, `readSeek_def`, or `readSeek_write`.
+Anchors come from `readSeek_show_content`, `readSeek_find_text`, `readSeek_find_nodes`,
+`readSeek_find_references`, `readSeek_find_definitions`, or `readSeek_write_file`.
 
 ## Variants
 

package/prompts/{def.md → find_definitions.md}

@@ -8,7 +8,7 @@ Go to a symbol definition or declaration by name. Accepts qualified or unqualifi
 - `gitScope` — in a Git repository, which files to search: `tracked`, `untracked`,
   `ignored` (untracked plus ignored), or `all`. Defaults to tracked plus untracked.
 
-After `readSeek_inspect` with `select: "identity"`, use
+After `readSeek_show_content` with `select: "identity"`, use
 `identity.identifier.text` for the token under the cursor. Use
 `identity.symbol.qualified_name` only when intentionally navigating to the
 enclosing declaration.

package/prompts/{search.md → find_nodes.md}

@@ -1,8 +1,10 @@
-Search code by AST structure using ast-grep-style patterns. Results include line hashes usable as `LINE:HASH` anchors. Use `readSeek_grep` for identifiers, strings, comments, configuration, documentation, or other plain text and regex.
+Search code by AST structure using ast-grep-style patterns. Results include line hashes usable as `LINE:HASH` anchors. Use `readSeek_find_text` for identifiers, strings, comments, configuration, documentation, or other plain text and regex.
 
 ## Parameters
 
 - `pattern` — AST pattern to match.
+- `context` — surrounding code context for sub-statement patterns (used with `selector`).
+- `selector` — target AST node kind to extract from pattern context.
 - `path` — file or directory; defaults to the current directory.
 - `language` — language override for ambiguous, extensionless, generated, or
   JSX-like source.
@@ -28,3 +30,12 @@ $OBJ.$METHOD($$$ARGS)
 <$TAG $$$ATTRS>$$$CHILDREN</$TAG>
 if ($COND) { $$$BODY }
 ```
+
+## Sub-statement patterns
+
+When searching syntax fragments that cannot parse as standalone statements (such as struct fields, function parameters, or class members), provide the surrounding syntax in `context` and specify the target node kind in `selector`:
+
+```text
+context: "struct S { int $NAME; };", selector: "field_declaration"
+context: "fn foo($NAME: i32) {}", selector: "parameter"
+```

package/prompts/{extract.md → show_assets.md}

@@ -1,6 +1,6 @@
 Extract one document asset selected by a stable `asset:ID` into a destination file.
 
-Call `readSeek_inspect` on the document first to discover asset IDs. This tool writes binary data directly to disk and never returns those bytes through tool output.
+Call `readSeek_show_content` on the document first to discover asset IDs. This tool writes binary data directly to disk and never returns those bytes through tool output.
 
 ## Parameters
 

package/prompts/{inspect.md → show_content.md}

@@ -27,7 +27,7 @@ Use this for anchored source content, diagnostics, cursor identity, shallow stru
 
 ## PDF workflow
 
-Inspect a PDF without a selector first. The result contains stable page, node, and asset IDs. Narrow with `page:N`, `node:ID`, or a KDL `query`. Use `readSeek_extract` only when the binary bytes of an `asset:ID` must be saved.
+Inspect a PDF without a selector first. The result contains stable page, node, and asset IDs. Narrow with `page:N`, `node:ID`, or a KDL `query`. Use `readSeek_show_assets` only when the binary bytes of an `asset:ID` must be saved.
 
 ## Output