[ymichael]

Human comments

What was wrong

The thread Info tab was a hard-coded list of core rows and sections in ThreadMetadataContent, so plugins had no way to add to it. Automations that target a thread (#5554) could only be seen in the global Automations view. An earlier attempt (local commit 11ec452c81) gave plugins a data hook that only core rendered from, and core did not use it itself.

What changed

Two slots, used by core and plugins alike

• app.slots.experimental_threadInfoRow adds a row to the details block, and app.slots.experimental_threadInfoSection adds a section below it.
• A registration is { id, group, order?, component }. The component receives { threadId, projectId } and mounts once per visible thread.
• ThreadMetadataContent now renders only through ThreadInfoRows / ThreadInfoSections (apps/app/src/components/secondary-panel/info/ThreadInfoSlots.tsx). These merge CORE_THREAD_INFO_ROWS and CORE_THREAD_INFO_SECTIONS with plugin registrations.
• Placement works like thread actions: sort by group, then order within it (unset last), then registration order, with core first on a tie. The comparator thread actions used moved to apps/app/src/lib/grouped-placement.ts, and both use it.
• bb's groups are exported as experimental_THREAD_INFO_ROW_GROUPS (thread, environment, git, pullRequest, lifecycle) and experimental_THREAD_INFO_SECTION_GROUPS (related, changes, storage). Core uses orders 10, 20, 30 within each group and keeps today's order.
• Plugin entries mount in a per-thread crash boundary. A crash removes only that row or section.

Shared building blocks

• experimental_InfoSection (heading, count pill, collapse), experimental_DetailRow, experimental_InfoList (the "N more" list) and experimental_InfoListRow are the components core draws with.
• DetailRow ({ label, icon?, align?, children }) is now bb's only label/value row: every core Info row and the commit dialog draw with it, and it is experimental_DetailRow. The old variant with class overrides is deleted. Branch and Archived truncate through an inner span, and the commit dialog's vertical changed-files row draws its own markup.
• Section collapse now comes from the slot. Core ids are unchanged (commits, forks, …), so saved collapse state carries over. Plugin sections are stored as <pluginId>/<id> in infoPanel.collapsedSections.
• Section separators moved from divide-y on direct children to each [data-info-section], so plugin wrappers do not break them.

Automations (first plugin caller, #5554)

• A section in the related group, ahead of Child threads, lists automations whose execution.targetThreadId is the open thread. It shows 3 rows with "N more", status labels from the overview, and refreshes on any automations realtime signal. Selecting a row opens the automation.
• automations_list and bb automation list --target-thread <id> take the target-thread filter. This is the server, CLI and test part of 11ec452c81. The skill documents it.

Docs and API process

• docs/api_to_audit.md entry with core callers and audit items.
• New Plugin Guide card "Thread Info rows and sections", with an Info tab fixture in the side panel wireframe.
• Authoring references and API indexes updated.
• Plugin SDK 0.6.69 → 0.6.70.

Not moved through the slots

• The empty/loading decision (hasAnyThreadMetadata plus the forks query in ThreadDetailSecondaryContent) still decides from core state whether the tab shows details, a skeleton, or "No thread details available." Plugin entries do not count toward it. This is audit item 3.

No server/daemon wire changes.

How you verified

Tests

• ThreadInfoSlots.test.tsx covers:
  • plugin rows and sections placed among core's by order, with unordered ones last;
  • a crashing plugin row or section dropped while core stays;
  • per-registration collapse, where a plugin section that reuses a core id does not collapse the core section.
• thread-info-section.test.tsx (automations) covers the target-thread RPC, realtime refresh from another project, status labels, and navigation.
• Server harness test for automations_list and the CLI --target-thread filter.
• Guide fixture, order, and mobile tests.
• turbo run test typecheck lint for @get-bb/plugin-sdk, @bb/app, bb-plugin-plugin-api-docs, bb-plugin-automations and @bb/domain: 20/20 tasks.
• turbo run typecheck lint --filter='...[origin/main]': 142/142 tasks.
• @bb/server test/services/plugins: 551 tests passed.
• check-plugin-sdk-version.mjs passes.

DetailRow consolidation: Info panels at 589 and 339 px wide (long branch names truncating, an archived thread, a PR) and the commit dialog were pixel-compared against main. The dialog and five of eight panels are identical; the rest differ only by an animated glyph, a ticking relative time, and one anti-aliased pixel.

Parity with main in the real app

• Built apps/app at main (cc292b9) and at this branch, and served each through a proxy in front of the live bb, so both builds showed the same real threads.
• Captured the Info panel at 1500×2200 for five threads covering parent/child, PR, commits, uncommitted files, a detached checkout and thread storage, then pixel-diffed the panels.
  • Two threads are identical, and so is a third once its slow workspace status (87 ahead / 198 behind) had loaded.
  • The other two differ only in the animated status glyphs of running child threads.
• Collapsing "Child threads" on the branch build showed it collapsed on the main build, so the preference key is unchanged. It was restored afterwards.

Automations in a dev instance (pnpm start:worktree)

• Created five automations that target a thread. The Info tab showed "Automations 5" below the details with three rows and "2 more", in the same style as core sections.
• Expand, collapse and re-expand work.
• Pausing and deleting from the CLI updated the section without a reload.
• Selecting a row opened /plugins/automations/automations/<project>/<id>.
• The Guide card renders with badge 13 over the Info tab.

Fixes #5554

AGENT GENERATED

🤖 Generated with Claude Code