Persist plugin thread status and repair Darwin plugin builds

[brsbl]

Summary

• add an experimental content-script API for persistent, plugin-owned thread-row status across navigation
• render running plugin statuses with the same host icon treatment and shimmer used by composer status
• package and validate both Darwin architecture variants of esbuild, Tailwind Oxide, and Lightning CSS so the packaged CLI can build plugins under either Node architecture

Verification

• affected Turbo typechecks passed for @bb/app, @bb/desktop, @bb/plugin-sdk, and @bb/templates
• affected suites passed: app 2,191 tests; desktop 190; plugin SDK 77; templates 14
• affected Turbo builds passed for app, desktop, plugin SDK, and transitive packaged runtime targets under Node 22.23.1
• packaged arm64 app and x64-Node plugin-build smoke passed during implementation
• isolated BB UI verification passed, and the final active installation passed manual testing

Dependency

Merge this host capability before brsbl/bb-plugins#12. The Prompt Improver plugin feature-detects the API, so this order is backward-safe and avoids shipping the plugin with its persistent indicator dormant.

[SawyerHood]

🚨 SLOP COP 🚨 · review

I am SlopCop. I started the review under the supplied security, code quality, performance, and end-to-end test rules.

[SawyerHood]

🚨 SLOP COP 🚨 · review

Security review complete. I found no actionable security issue. The new setter accepts any thread ID, but content scripts already run as trusted same-origin code.

[SawyerHood]

🚨 SLOP COP 🚨 · review

Code quality review complete. I found no actionable correctness or contract issue. The lifecycle, status ownership, UI priority, SDK declarations, and Darwin package checks are consistent.

[SawyerHood]

🚨 SLOP COP 🚨 · review

Performance review complete. I posted two findings: a workspace-wide dual-CPU install cost and three full package-tree scans during packaging.

[SawyerHood]

🚨 SLOP COP 🚨 · review

Test phase complete. Turbo type checks passed for @bb/app, @bb/plugin-sdk, and @bb/desktop. Turbo tests passed with 297 app files and 2,191 app tests, plus the plugin SDK and desktop suites. I started the exact PR head and opened it with a browser. The app shell loaded without page or console errors. The isolated test data had no installed status plugin, so the automated lifecycle and route-status tests provide the status-specific coverage.

[SawyerHood]

🚨 SLOP COP 🚨 · review

Review complete. I found no security or correctness issue. I found two non-blocking performance issues: normal installs now fetch both CPU variants, and desktop packaging scans the full output tree three times.

Validation passed: all affected type checks, all affected package tests, and a browser smoke test at the exact head SHA.

[SawyerHood]

Please delete the old plugin api that you added previously (the one to set a thread status via useComposer)

[brsbl]

Addressed the requested API deletion in 658d131: removed PluginComposerApi.setThreadRowStatus from public types, generated declarations, docs, tests, and host routing; retained only an unadvertised runtime no-op so prebuilt SDK 0.4.1 bundles do not throw during rollout. Prompt Improver now uses the persistent content-script API exclusively in brsbl/bb-plugins#12. Added replacement malformed-status coverage and updated the audit entry. Fresh scoped review is clean; affected tests, typecheck, and production build pass. Please re-review this exact head.