docs(changelog): Chrome Extension 0.8.0 (resubmit + configurable row hiding)

[samgutentag]

The changelog half of the Chrome Extension 0.8.0 work (TRUNK-18467). One entry covering both shipped features.

⚠️ Merge after #208 (the docs PR). This entry deep-links to two sections that #208 adds to merge-queue/chrome-extension.mdx (#resubmit-after-failure-or-cancellation and #configuring-row-hiding), so those anchors only resolve once #208 lands.

What's here

• New entry changelog/2026-06-04-merge-queue-chrome-extension-0-8-0.mdx covering:
  • Resubmit after failure/cancellation (with the Failed/Cancelled/Waiting-to-Batch states)
  • Configurable row hiding (the three Hide rows toggles)
• Nav wired by scripts/sync-changelog.py, not hand-edited: docs.json, changelog/index.mdx, merge-queue/changelog.mdx. --check is clean.

Replaces

The duplicate draft changelog entries in #204 (2026-06-03-...) and #180 (2026-06-02-...), which created two posts for the same release. Both should be closed once this and #208 land.

Source: trunk2 #4042 (resubmit/terminal states), #4075 (row hiding). Extension published as 0.8.0 on 2026-06-04.

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
trunk	🟢 Ready	View Preview	Jun 5, 2026, 4:54 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[samgutentag]

Verification status (2026-06-04): live

Verified: customers can use this. Ready to publish.

• Flag state: none. Same 0.8.0 extension work as docs(merge-queue): document Chrome Extension 0.8.0 (terminal states + row hiding) #208; ships in the published Chrome Web Store build, not behind a LaunchDarkly flag.
• Eng PR: trunk-io/trunk2#4042 (terminal states, merged 2026-06-02), trunk-io/trunk2#4075 (row hiding, merged 2026-06-03). Both on main, shipped in deploy v195.
• Flag: none (ungated)
• Signals: extension published as 0.8.0 on 2026-06-04 (announced in #team-merge-queue); no LD flag in either eng diff.

Ready to publish. Merge #208 first (this changelog entry deep-links sections that #208 adds to chrome-extension.mdx).

[samgutentag]

Code verification (2026-06-04): 8 confirmed / 0 contradicted / 0 ambiguous / 0 unverifiable

The changelog entry describes the same extension work as #208. Verified its claims against trunk-io/trunk2 (ts/apps/browser-extension). Same verdicts; the exact toggle-label fix lives in the docs PR #208.

Claim	Verdict	Source
Failed/Cancelled show a Resubmit button	confirmed	prPageMqNotInQueueView.ts:133
Cancelled shows who cancelled ("Cancelled by alice")	confirmed	mergeItemTerminalDetail.vitest.ts:76
"Waiting to Batch" state exists	confirmed	mergeItemPendingDetail.vitest.ts:35
Failed lists failed checks with run-log links	confirmed	mergeItemFailedCheck.vitest.ts:87
Hide rows toggle labels (incl. "Trunk (bot) GitHub Comments")	confirmed	popupHideableRows.vitest.ts:47
Actionable conflict rows ("must be resolved" / Resolve conflicts) stay visible	confirmed	prMergeRowHeuristics.ts:280
Toggles default on, persist in chrome.storage.local	confirmed	constants.ts:18
Settings cards: Hide rows / Verbose logging (byte size) / Keyboard shortcuts	confirmed	popupSettingsSections.vitest.ts:16

---

Toggle label correction (confirmed after fix)

File: popupHideableRows.vitest.ts#L47-L51

expect(mergingBlocked?.name).toBe("Merging is blocked");
expect(branchOutOfDate?.name).toBe("Branch out of date");
expect(botComments?.name).toBe("Trunk (bot) GitHub Comments");

Reasoning: The first draft labeled the third toggle "Trunk bot comments". The on-screen label is "Trunk (bot) GitHub Comments". Corrected in the docs PR so the bold label matches the UI exactly, per the nav/UI standard. The other two toggle labels already matched source.

"Cancelled by <actor>" format (confirmed)

File: mergeItemTerminalDetail.vitest.ts#L76-L123

).toBe("Cancelled by eli");
// ...
it("falls back to cancelled by user when no actor is available", () => {
).toBe("Cancelled by user");

Reasoning: The panel renders "Cancelled by <actor>" using the cancelling user when available, falling back to "Cancelled by user". The docs example "Cancelled by alice" matches the format.

Conflict-row exception (confirmed)

File: prMergeRowHeuristics.ts#L280-L281

"this branch has conflicts that must be resolved";
const RESOLVE_CONFLICTS_CONTROL_SNIPPET = "resolve conflicts";

Reasoning: The "Branch out of date" toggle hides only the informational conflicts row. Rows with "must be resolved" copy or a "Resolve conflicts" control are kept visible, exactly as the docs state.

[samgutentag]

Added a second commit (4412801) unrelated to the 0.8.0 entry: removed trunk-staging-io from the May 19 changelog entry. It's an internal-only bot account customers never see, so it doesn't belong in a customer-facing changelog. Frontmatter is unchanged, so no nav re-sync was needed.