Dev

.github/workflows/test.yml

@@ -41,6 +41,8 @@ jobs:
       fail-fast: false
       matrix:
         node: [ '22', '23', '24' ]
+    env:
+      TZ: Europe/Istanbul  # Set timezone for entire job
 
     steps:
       - name: Setup Environment

.gitignore

@@ -1,5 +1,8 @@
 node_modules
 /build
+*.tsbuildinfo
+graphify-out
+.claude
 
 # environment variables
 .env

CHANGELOG.md

@@ -1,7 +1,8 @@
 ## Changelog
 
-### [v0.1.2](https://github.com/panates/flexy-buffer/compare/v0.1.1...v0.1.2) - 
+### [v1.0.0](https://github.com/panates/flexy-buffer/compare/v0.1.2...v1.0.0) - 
 
-#### 🪲 Fixes
+#### 💬 General Changes
 
-- fix: Fixed return values @Eray Hanoğlu 
+- Add start()/flush(), byte-exact maxLength, fix writeString bug @Eray Hanoğlu 
+- Move to a single ESM-only build @Eray Hanoğlu 

CLAUDE.md

@@ -0,0 +1,25 @@
+## 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).
+
+## API docs baseline (docs/api.md, docs/api/*.md)
+
+`docs/api.md` starts with an HTML comment block (`docs-baseline`) recording the git commit,
+package version, and date the API docs were last verified against source - see that block for
+the exact format and the `git diff <commit>..HEAD -- src/` command it documents.
+
+Rules:
+- Whenever you write or update these API docs, record (or update) that baseline block with the
+  commit you verified against - so a later session can diff from a known point instead of
+  re-reading everything from scratch.
+- Before trusting/updating the docs, diff `src/` (and `test/**/*.spec.ts` for examples) between
+  the recorded commit and `HEAD` to see what actually changed, then update only the affected
+  doc section(s) - don't regenerate everything unless the diff is broad enough to warrant it.
+- After updating, bump `git-commit`/`package-version`/`date` in the baseline block to the new
+  `HEAD` (only once the docs are verified accurate as of that commit).