Create and manage Taskboard issues from BB threads

[MateoCerquetella]

Summary

• Add a Taskboard ticket action beside BB composer controls in New thread and existing threads.
• Turn rough prompt text into an editable, repository-aware issue title and Markdown description through a hidden read-only helper.
• Create the reviewed issue in the BB project configured GitHub, Linear, or Jira tracker, then attach it to the composer as a live Taskboard mention.
• Add a compact Taskboard right panel that can remain pinned while switching between chats.
• Allow status changes from the status dot on a List row and the status pill inside task details.
• Keep explicit Taskboard project selections stable and resolve pinned-panel projects from their owning threads.
• Add provider scope checks, Jira project-key inference, cancellation and fallback behavior, tests, documentation, and an interactive demo.

Why

Creating and managing tracker work from BB previously required leaving the conversation or reopening Taskboard after every chat switch. Project navigation could also reapply the source chat project after the user selected another project, leaving the board on an empty project even though the selected project had cached tickets.

This keeps issue creation, issue context, common status updates, and project navigation beside the active thread while preserving a review step before any external issue is created.

Root cause

Taskboard applied the source chat context after its asynchronous project list loaded, even when the URL already represented an explicit project choice. The pinned thread panel also read global route context instead of resolving the project that owns its thread. Those two context paths could point ticket queries at the wrong project.

Explicit project and item routes now win over source context. Context is used only when entering an unscoped Taskboard root or Manage route, and existing-thread panels resolve their project through the thread ID before loading tickets.

User impact

• The ticket icon sits between Improve Prompt and voice controls.
• It is grey and disabled when the prompt is empty, then becomes active without a persistent background once text is present.
• The creation modal follows the selected project Taskboard provider and remains fully editable.
• The thread-header Taskboard button opens the board in BB right panel and pins it across chat switches.
• The right panel follows the project for each thread and can be unpinned from its own header.
• Switching Taskboard projects no longer jumps back to the source chat project or shows that project empty state.
• List rows expose a compact status-dot menu, and task details expose the same provider workflow through the labeled status pill.
• Status updates are optimistic and roll back when a provider rejects the transition.

Safety and correctness

• The drafting helper is hidden, read-only, and cannot create external issues.
• Issue creation is bound to the provider reviewed in the modal to prevent configuration races.
• GitHub repositories, Linear teams, and Jira project keys remain constrained to the configured project scope.
• No real external issue was created and no real ticket status was changed during validation.

Validation

• npm run check
• 37 tests passed across the workspace
• SDK pin checks, TypeScript checks, both plugin builds, and Taskboard build metadata verification passed
• Taskboard was rebuilt and reloaded from the local checkout
• Live BB verification confirmed the right panel persists and resolves the owning project when switching chats
• Live project-switch verification confirmed Bandely displays 4 tickets and freebee displays 248 instead of the source chat empty state
• Live Linear verification confirmed row and detail status menus load the provider workflow without selecting a transition