Tool/function-call edit mode

.gitignore

@@ -1,2 +1,3 @@
 /target
 /tmp
+/.cargo-home

AGENTS.md

@@ -0,0 +1,33 @@
+# refac — contributor notes
+
+## Comments are code
+
+A comment must **provably earn its place**: it survives only if it carries a
+**WHY**, a **gotcha**, or a **constraint** a future reader would otherwise trip
+over. Never restate what the code, a signature, or a type already says; never
+narrate WHAT the next lines do; never leave development-history trivia ("changed
+from…", "the API doesn't infer this"). **When in doubt, delete.** Comment density
+is itself a cost — a wall of even-true remarks buries the few that matter and
+makes the code harder to read.
+
+Doc comments on crate-internal items get the same bar: keep one only for a
+non-obvious WHY or when a macro consumes it (e.g. a `schemars` field doc that
+becomes a model-facing schema description).
+
+## Types
+
+Prefer real types over `serde_json::Value` or stringly-typed data for anything
+refac constructs or controls. The one sanctioned `Value` is a payload echoed back
+to a provider verbatim for byte-fidelity (re-serializing would reorder fields) —
+and that exception carries a WHY comment.
+
+## Build & test
+
+The toolchain is pinned via nix, not rustup. From a clone:
+
+```bash
+cargo test
+cargo clippy --all-targets -- -D warnings   # must stay clean
+```
+
+Both must pass before requesting review.

Cargo.toml

@@ -15,17 +15,16 @@ repository = "https://github.com/bddap/refac"
 [dependencies]
 anyhow = "1.0.69"
 clap = { version = "4.1.8", features = ["derive"] }
-itertools = "0.10.5"
 reqwest = { version = "0.13", default-features = false, features = [
   "rustls",
   "blocking",
   "json",
 ] }
 rpassword = "7.5.0"
 dialoguer = "0.11"
+schemars = "1.0"
 serde = { version = "1.0.154", features = ["derive"] }
 serde_json = "1.0.94"
-similar = "2.2.1"
 toml = "0.7.3"
 tracing = "0.1.37"
 tracing-subscriber = "0.3.20"