oma-docs

1# Documentation Maintenance
2 
3## Scheduling
4 
5### Goal
6Keep documentation aligned with repository behavior and report verification limits.
7 
8### Intent signature
9Check references, update docs for a code diff, identify translation drift, or lint localized prose.
10 
11### When to use
12Repository documentation verification, diff-based synchronization, and translation maintenance.
13 
14### When NOT to use
15- General source research -> oma-search.
16- Application implementation -> the owning specialist.
17- Translating known text -> oma-translation.
18 
19### Expected inputs
20Mode (`verify`, `sync`, `i18n`, or `lint`), target paths or diff range, and authorized edit scope. Use `verify` when no mode is specified.
21 
22### Expected outputs
23Findings with paths and evidence, authorized patches when requested, and unresolved checks. CLI reports remain distinct from host-authored interpretation.
24 
25### Dependencies
26The `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.
27 
28## Structural Flow
29 
30### Transitions
31- `verify`: extract and resolve references, then summarize the report.
32- `sync`: obtain candidates, read relevant docs and diffs, and apply only authorized corrections.
33- `i18n` / `lint`: report drift or style issues; use oma-translation for authorized corrections.
34…