Dev

.gitignore

@@ -3,6 +3,12 @@
 /build
 node_modules
 coverage
+*.tsbuildinfo
+graphify-out
+.claude
+
+# benchmark raw results (regenerate with `npm run bench`)
+/benchmark/results
 
 # environment variables
 .env

CHANGELOG.md

@@ -1,6 +1,21 @@
 ## Changelog
 
-### [v4.13.0](https://github.com/panates/lightning-pool/compare/v4.12.0...v4.13.0) - 
+### [v4.14.0](https://github.com/panates/lightning-pool/compare/v4.13.0...v4.14.0) - 
+
+#### 🚀 New Features
+
+- feat: Replace benchmark-tests with a proper benchmark suite @Eray Hanoğlu 
+
+#### 🪲 Fixes
+
+- fix: Correct release/close/ensureMin bugs and cut hot-path allocations in Pool @Eray Hanoğlu 
+
+#### 📖 Documentation Changes
+
+- docs: Split API reference into doc/API.md, add generated doc/BENCHMARKS.md @Eray Hanoğlu 
+- docs: Add CLAUDE.md with graphify usage guidelines @Eray Hanoğlu 
+
+### [v4.13.0](https://github.com/panates/lightning-pool/compare/v4.12.0...v4.13.0) -  27 August 2026 
 
 ### [v4.12.0](https://github.com/panates/lightning-pool/compare/v4.11.1...v4.12.0) -  4 December 2025 
 

CLAUDE.md

@@ -0,0 +1,9 @@
+## graphify
+
+This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
+
+Rules:
+- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
+- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
+- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
+- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).