command-center/agent/managed-skills/omp-bundle-claim-audit/SKILL.md

name, description

name	description
omp-bundle-claim-audit	Verify or discover omp TUI behavior facts from the minified dist/cli.js bundle, with live niri-screenshot matrix confirmation; use when auditing docs claims or answering "how does omp actually do X".

omp bundle claim audit

Ground omp behavior claims in ~/.bun/install/global/node_modules/@oh-my-pi/pi-coding-agent/dist/cli.js (minified single line), not guesswork.

Extraction

• grep -oE too weak for long windows; use python: read whole file, re.search(r'ANCHOR.{0,900}', s) windows around stable anchors.
• Reliable anchors: settings ids (id:"statusLine.contextLine"), renderer ids (id:"path",render\(e\)\{), registry arrays (l9e=\[, Uxe=\{ preset table), descriptions ("Label",description:"([^"]+)").
• Minifier renames symbols per release — anchor on string literals, never on #Xt/zG names.
• Enum values live in a var: find id:"KEY" → values:VAR → re.search(r'VAR=\[[^\]]+\]').
• Some segments are factory-generated (VDt("token_in",...)) — literal id scans miss them; check the catalog array (l9e) and preset tables for referenced ids.
• Beware gallery/preview code faking production behavior (e.g. N4r synthesizes a status bar for the settings gallery) — confirm the window you cite is the production render path.

Live confirmation (only where pixels decide)

1. Edit ~/.omp/agent/config.yml (file-watched, repaints without restart).
2. sleep 2 && niri msg action screenshot-screen --path /tmp/x.png --show-pointer false; sleep 1.5 (flag is --path, NOT -o; the write lands slightly late — sleep before PIL).
3. Crop + 1.3x LANCZOS via PIL, read the crop.

• Multi-window screens make bar crops ambiguous: prefer settling the question in code (the layout gate layout!=="box"&&layout!=="band" style booleans) over pixel forensics; scan rule rows by dominant-color spans only for single-color questions.
• ALWAYS restore config edits afterwards (track exact line anchors; the edit tool demands a matching snapshot header).

Audit output

Correct false claims in-place, keep an "Audit log" section listing each claim → truth with code/live evidence; mirror corrections into omp-docs/log.md.