oma-docs

# Documentation Maintenance ## Scheduling ### Goal Keep documentation aligned with repository behavior and report verification limits. ### Intent signature Check references, update docs for a code diff, identify translation drift, or lint localized prose. ### When to use Repository documentation verification, diff-based synchronization, and translation maintenance. ### When NOT to use - General source research -> oma-search. - Application implementation -> the owning specialist. - Translating known text -> oma-translation. ### Expected inputs Mode (`verify`, `sync`, `i18n`, or `lint`), target paths or diff range, and authorized edit scope. Use `verify` when no mode is specified. ### Expected outputs Findings with paths and evidence, authorized patches when requested, and unresolved checks. CLI reports remain distinct from host-authored interpretation. ### Dependencies The `oma docs` CLI, Git for diff-based work, and repository docs. `lychee` is optional for URL verification. Read `resources/commands.md` for flags and output files of the selected mode. ## Structural Flow ### Transitions - `verify`: extract and resolve references, then summarize the report. - `sync`: obtain candidates, read relevant docs and diffs, and apply only authorized corrections. - `i18n` / `lint`: report drift or style issues; use oma-translation for authorized corrections. - Review-only requests produce proposals. Existing scoped edit requests authorize applying those corrections without anot...