Veomni Fix Docs

Fix VeOmni Documentation

Audit documentation and apply only corrections supported by evidence. This skill is self-contained: it requires no bundled script, extra Python package, GPU, or network connection. Use the repository's available search, build, and validation tools; do not imply that a manual search is an exhaustive parser-based scan.

Scope and baseline

1. Read the request and applicable AGENTS.md. A review-only request calls for findings, not edits. A correction request permits verified documentation fixes, not unrelated code changes or a push.
2. Run git status --short before editing. Preserve unrelated changes. Use requested paths; otherwise inspect tracked Markdown/MDX in README.md, docs/, .agents/, and component documentation. Include relevant new unignored files.
3. Record the repository revision and which files or directories you actually checked. For large scopes, work in batches and report any uninspected area instead of claiming full coverage.

Mechanical checks

Enumerate candidates with git ls-files --cached --others --exclude-standard -- '*.md' '*.mdx'. Do not use rg --files, which skips hidden paths such as .agents/, or plain git ls-files, which omits untracked files. Search for Markdown links/images (including reference definitions), HTML a[href] and img[src], headings, code fences, and repeated words. Search output is a candidate list, not proof that all links were found: multiline Markdown, footnotes, comments, code spans, MyST directives, and HTML can defeat simple patterns. Use an available Markdown parser or renderer when comprehensive coverage matters, without introducing a permanent dependency just for this skill.

For each candidate link or image:

• Resolve a relative path from the containing document, including .., URL decoding, and exact filename case. Do not resolve every link from the repository root. Check whether an absolute-site path is handled by the documentation renderer.
• For a fragment, inspect the target heading or explicit HTML ID and the intended renderer's generated permalink. GitHub and Sphinx/MyST can produce different IDs, especially for Emoji, linked heading text, punctuation, and duplicate headings. Do not remove an icon or change a heading merely to make a guessed fragment match.
• For a source-file link with a line anchor (file.py#L142), open the target line and confirm it is the symbol or statement the link text names. Line anchors drift silently when code above them changes; re-point a stale anchor to the current line rather than dropping it.
• Check reference-style links against their definitions. Exclude literal code and commented examples unless the user asks to review examples.
• Treat malformed URLs, suspicious duplicates, missing spaces after heading markers, and unmatched fences as review candidates. Verify context before editing. Do not guess a replacement URL or destination.
• Check external links only if network access is available and authorized; otherwise mark them unverified. MyST labels/directives, generated targets, MDX/JSX routing, and site-specific URL rules need renderer-specific checks.

If a target is missing or ambiguous, search the repository for its intended replacement. Fix only when the destination is clear; otherwise report the uncertainty with file and line.