[aicayzer]

Summary

Adds a recommended practice to Sync a folder: for reference records kept beside code, use a folder inside the repository that git ignores, named marfa/, and says why. It also syncs the contract from withmarfa/marfa, which adds the git warning of marfa folders add. This pull request waits on withmarfa/marfa#2417, which adds the warning and its contract statements.

Changes

• content/docs/run/sync-a-folder.mdx: after the storage warning sentence, a paragraph that recommends marfa/ (not .marfa, which every folder already holds for its store and folder.yaml), says any directory works elsewhere, and explains that git and Marfa would both change the same files, so folders add warns and goes on.
• scripts/sync-from-marfa.sh output, run against the branch of feat(cli): warn when git tracks the directory of a folder being added marfa#2417: the contract index gains folders/git-tracked-warns, folders/git-tracked-continues and folders/git-untracked-silent. The same run also carried the file-text search statements, the v0.0.39 release and its download and image lines that were already on marfa's main.
• folder-safeguards, keep-folders-running, folder-files and the glossary do not mention storage warnings or git, so none contradicts the new paragraph.

Testing

• pnpm test: 39 files, 709 tests passed (content lint and the command check included).
• Not run: pnpm build and pnpm types:check (CI runs them).
• Before this leaves draft, re-run scripts/sync-from-marfa.sh against marfa main once feat(cli): warn when git tracks the directory of a folder being added marfa#2417 has merged, so the generated files match main and not the branch.

Notes for reviewers

• Draft until feat(cli): warn when git tracks the directory of a folder being added marfa#2417 merges. The CLI reference is generated from marfa's COMMANDS.md, whose folders add help text changes there.
• The first draft of a sync from a branch is expected to differ from one from main only by the commit hashes of the contract index entries it carries.

Checklist

• The title is a scoped Conventional Commit.
• New behavior has a test that was seen failing first, or no test was needed and the reason is above.
• Docs, comments and the contract still say what is true after this change.