Let’s keep the Codex session JSONL there too, why the hell not. And the debug build logs, since they’re easily greppable text useful for diagnosing recurring problems. And logs/reports from every test run - a ton of useful info there, lets you track regressions over time; would be a shame to throw it away. We could also store screenshots of every app run to have a LLM-compatible historical record of how each component changed visually. And the token provider billing documents, since we’re gonna have a lot of those once we’ll start maintaining all that.
The author is really just advocating for design docs, which do make sense in a repo. LLMs are excellent at creating .md docs tracking design decisions, code architecture, trade-offs, etc. And these actually can be of great use to future contributors.
