What should be committed?

[SimplicityGuy]

I see many files in the graphify-out directory, specifically in cache. What should be checked into the repo? All but cache?

graphify-out
├── cache
│   ├── 00a069217d057e9a0c80132ab64a010460e67ed7d51340aadcf94ea00109d3f8.json
│   ├── ...
│   └── feb056d74325af7bb5946dfcd4cabdabaa21503c69a563319570042ce10dae4c.json
├── cost.json
├── GRAPH_REPORT.md
├── graph.html
├── graph.json
└── manifest.json

[Khanz9664]

I dug through the README and the team workflow section, and it looks like graphify-out/ is meant to be committed — but not wholesale.

From what I can tell:

• The core, shareable artifacts are graph.json, graph.html, and GRAPH_REPORT.md — these are the “map” that other teammates (and assistants) rely on, so committing them makes sense.
• manifest.json is explicitly described as mtime-based and invalid after clone, so it shouldn’t be in the repo.
• cost.json is just local token accounting, so also not useful to share.
• cache/ is more of a tradeoff: it’s deterministic and can speed up incremental runs across the team, but it can also get large quickly. The README hints it’s optional, so I’d lean toward ignoring it unless the team specifically wants shared caching.

So practically, I’d treat it as:

• commit → graph outputs (source-of-truth artifacts)
• ignore → manifest.json, cost.json
• optional → cache/ depending on repo size vs rebuild speed

Might be worth making this a bit more explicit in the README — especially around cache/, since that’s the main ambiguity.