[brsbl]

Human comments

What was wrong

Automation runs were stored and displayed as user messages. The compact row from #4763 still exposed the prompt and coupled automation presentation to core.

What changed

• Automations render their own named timeline markers with time, status, View prompt, and Retry after failure.
• Generic experimental SDK APIs attach markers to hidden turns and let the owning plugin read or update them.
• Markers follow their exact turn through queuing, cold starts, completion, failure, and cancellation.
• Existing Show automation prompts as compact timeline rows #4763 chips retain their rendering. Additive database fields preserve existing records; daemon protocols are unchanged.
• SDK 0.6.17, Plugin Guide, automation CLI retry, and discoverable automation guidance document the new behavior.

How you verified

• Remote CI passed on bab5dc5db6: 26 jobs succeeded, including Linux/Windows tests, type checks, and package smoke checks.
• Chrome for Testing 151.0.7922.71: success, prompt disclosure, failed turn, Retry, reload, and desktop/mobile layouts passed at 2×.
• Retry created a distinct hidden turn in the same thread; the timeline contained zero user-message rows.
• One architectural/implementation review identified five P1 issues; targeted fixes and regression checks resolved them.

The checkout lacks scripts/bb-dev-app; evidence uses its exact app/server/daemon development services with isolated data and browser profile.

Before: c201f6490a · After: bab5dc5db6 · 2× pixel density.

State	Viewport	Before	After
Success	1440×900
View prompt	1440×900
Failure with Retry	1440×900
Success and failure	390×844
View prompt	390×844

Review follow-ups

Deferred P2 findings: thread forks do not yet copy plugin markers; a successful run can inherit an inaccurate error string from the legacy settlement fallback. These remain follow-up work under the review scope policy.

User QA is pending. This PR does not migrate Action Cards or Digests.

BB-Thread-ID: thr_h9xm8rfpbh

AGENT GENERATED

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.