Runtime Debug Protocol

Use this when static audits pass but a selected, hovered, focused, or active runtime state still fails.

Required Steps

Reproduce the issue in Obsidian with the exact runtime state active.
If the CDP endpoint is closed while Obsidian is already running, close the existing Obsidian processes and reopen Obsidian with --remote-debugging-port=9222 before capturing evidence.
Run runtime-debug-snippets/table-cell-dump.js when the issue is table/cell geometry.
Run runtime-debug-snippets/matched-rules-dump.js to capture theme/core matched rules.
Inspect inline style first. Inline geometry means the issue may not be solvable by ordinary owner CSS.
If a theme rule is responsible, map the bundle line through effective-source-map.json and edit the source owner.
If an Obsidian core rule is responsible, do not override it unless an owner contract explicitly permits it.
Re-run the same runtime state after editing; static audits alone are insufficient.

DOM chain: tag, class, inline style, text preview.
Rect chain: x/y/width/height for the target and parents.
Computed geometry: display, position, width, height, min/max height, padding, line-height, vertical-align, overflow, transform.
Matched rules: selector and CSS text for geometry-affecting declarations.