Your files, and what to commit

Everything the tool keeps about your project lives in ONE folder inside your app’s repo: just-ai-i18n-docgen/, beside your package.json. Every path resolves against config.json in that folder — run the CLI from anywhere.

Commit these (they are your project’s record)

• config.json — the project: source (the one path fact — its folder is your locale dir, its basename your source language), targets, context, glossary, placeholder/plural settings (inferred when absent), and the docs prefixes.
• <lang>.accepted.json — the human review record: who accepted what, hashed over (key, flag, source, target) so edits re-open findings. Committed so CI’s check sees the same acceptances you do.
• <lang>.notes.json — your notes to the translator, per key.

Gitignore these (machine state — the Setup page prints the block to paste)

• <lang>.probe.json — the probe’s second-pass sample.
• .just-ai-i18n-docgen-cache.json — the English each translation was made from (how a changed English string is found). Deleting it costs nothing but that: the current translations are taken as up to date. (.just-ai-i18n-docgen-probe-cache.json is no longer written; an old one can go.)
• .just-ai-i18n-docgen-state.json — your review cursor, the undo log, staged proposals, the back-translation cache, run history. Deleting it costs your place and your undo history — never your work: applied translations are in your locale files, acceptances and notes in their committed files.

One folder, both doors

The app and the CLI read and write the same files. Writes are atomic but not locked — if a CLI run and an open Review page race, last write wins; finish one before driving the other.