Problem
The Team setup section advises teams to commit graphify-out/ and gitignore only two entries:
graphify-out/cost.json
# graphify-out/cache/
Several other local-only artifacts generated by graphify are missing from this list. Teams following the current guidance will inadvertently commit:
graphify-out/memory/ — personal Q&A annotations written by graphify save-result (per-developer, not meant to be shared)
graphify-out/reflections/ — derived from memory/ (LESSONS.md + .graphify_learning.json), local only
graphify-out/.graphify_* — hidden metadata files including .graphify_root (contains an absolute local path), .graphify_semantic_marker, .graphify_cached.json, .graphify_uncached.txt, .graphify_analysis.json
graphify-out/????-??-??/ — dated backup snapshot directories created automatically when semantic artifacts are protected
Fix
PR #1866 expands the recommended .gitignore block to cover all of the above, and adds a commented hint for teams that want to optionally share .graphify_labels.json.
Problem
The Team setup section advises teams to commit
graphify-out/and gitignore only two entries:Several other local-only artifacts generated by graphify are missing from this list. Teams following the current guidance will inadvertently commit:
graphify-out/memory/— personal Q&A annotations written bygraphify save-result(per-developer, not meant to be shared)graphify-out/reflections/— derived frommemory/(LESSONS.md+.graphify_learning.json), local onlygraphify-out/.graphify_*— hidden metadata files including.graphify_root(contains an absolute local path),.graphify_semantic_marker,.graphify_cached.json,.graphify_uncached.txt,.graphify_analysis.jsongraphify-out/????-??-??/— dated backup snapshot directories created automatically when semantic artifacts are protectedFix
PR #1866 expands the recommended
.gitignoreblock to cover all of the above, and adds a commented hint for teams that want to optionally share.graphify_labels.json.