@ruso-0/nreki 8.6.2 → 9.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ruso-0/nreki",
3
- "version": "8.6.2",
3
+ "version": "9.0.0",
4
4
  "description": "MCP plugin that validates AI agent edits in RAM before they touch disk. Spectral clustering, architecture diffs, bridge detection, dead code oracle, and cross-file semantic checks for TypeScript, Go (gopls), and Python (pyright). Zero cloud dependencies.",
5
5
  "main": "dist/index.js",
6
6
  "type": "module",
@@ -25,6 +25,13 @@ If the `nreki_*` tools fail to load, timeout, or return connection errors:
25
25
  * **NEVER use Native `Write` or `Replace` to modify existing files.** It bypasses the RAM safety shield.
26
26
  * **SINGLE EDITS:** ALWAYS use `nreki_code action:"edit" symbol:"<Name>"`.
27
27
  * **MULTI-FILE EDITS:** ALWAYS use `nreki_code action:"batch_edit"`. It is a strict ACID transaction.
28
+ * **PATCH MODE (Minimum Output Tokens):** For ANY edit that changes less than 30% of a symbol's body,
29
+ you **MUST** use `mode:"patch"` with `search_text` and `replace_text`.
30
+ **NEVER** rewrite an entire function to change a single line. Output tokens are 5x more expensive than input.
31
+ * **CRITICAL FOR PATCH:** Your `search_text` must be an EXACT substring of the existing AST node,
32
+ including exact whitespace and indentation. If patch fails, NREKI returns a preview of the actual AST content.
33
+ * **SCAFFOLDING EXCEPTION:** When creating BRAND NEW files from scratch, use Native `Write`.
34
+ New files have nothing pre-existing to break. NREKI `edit`/`batch_edit` is for modifying existing code only.
28
35
  * **NEW FILES:** Use Native `Write` ONLY for creating brand-new files.
29
36
  * **RENAMING:** Run `nreki_navigate action:"prepare_refactor"` before renaming.
30
37