Recommended loop
hyperlocalise run --dry-run- inspect task list and counts
hyperlocalise run- review failures and rerun if needed
Lock-file behavior
.hyperlocalise.lock.json tracks completed tasks to avoid repeated work.
When you change source content or config mappings, re-run and verify whether new tasks are planned.
Use Lockfile contract for schema details and reset guidance.
Good practice
- keep dry-run in CI for visibility
- use deterministic file mappings
- avoid manual edits to lock state
Markdown in local workflows
If your bucket mappings point to.md or .mdx files, hyperlocalise run --dry-run still plans tasks from Markdown sources.
When you run without --dry-run, output keeps Markdown and MDX layout stable while translating extracted prose nodes.