Expandable Merge Gate Details

Each gate in the merge card (Approvals, Checks, Findings, and Up to date too, for consistency) now has a chevron and opens to show the details behind it. Tests pass (68/68). I checked the look in headless Edge using the trail fixtures plus a made-up failing case; I haven't tried it in Orca yet. Nothing is committed.

What each gate shows when opened

• Approvals: every reviewer with their initial, their state (Approved, Changes requested, Commented…), an "Outdated" tag if they reviewed an earlier commit, and their comment. It also says how many approvals are needed, whether self-approval counts, and whether pushing dismisses approvals. A warning appears if someone requested changes.
• Checks: each check run with a status dot, its app, how long it took and a result pill. It also says which checks are required, or whether every check must pass.
• Findings: each reviewer (agent or runner) and what they found, with how many findings are blocking. It shows the severity that blocks merging (for example "Blocks on high findings"), the high/medium/low counts, and a warning while a review is still running.
• Up to date: "3 commits behind main" or "Ahead of main, nothing missing".
• Every gate: Entire's rationale, plus a line saying whether it blocks merging, when it was checked, and the commit it was checked at. It also flags a gate that was checked on an earlier commit.

Changes

• src/worker/trail.mjs: each gate now carries a detail object, with Entire's text cut to a maximum length and lists capped at 30 items. Check runs come from the change's own list, which includes the app and timing. I removed the old merge.checks field because the panel never used it.
• panel/template.html: the gate rows are now expandable, and the panel remembers which ones are open. It rebuilds itself every minute, which would otherwise close them. The finding cards had that same problem, so they now stay open too.
• test/trail.test.mjs: three new tests cover the gate details, gates that haven't been evaluated yet, and a reviewer who appears twice or reviewed an older commit.

To see it in Orca, turn the plugin off and on so a new worker writes the details. Until then the panel still shows data from the old worker, and opening a gate shows only the rationale and the blocks-merging line.

The preview build script and screenshots are in C:\Users\pcruc\AppData\Local\Temp\entire-gates-preview\, outside the repo.

I made the branch, committed the change and opened the PR: https://github.com/petercr/orca-entire-extension/pull/3

• Branch: gate-details
• Commit: 1c99270 "Let each merge gate open to show what decided it", with the three changed files (src/worker/trail.mjs, panel/template.html, test/trail.test.mjs)
• PR description: summarizes the change and has a test plan. The one item still unchecked is trying it in Orca itself: turn the plugin off and on, then open each gate on a real trail.

My first commit attempt failed, so the branch was briefly pushed pointing at main's commit. The real commit went up right after; nothing else changed.