Wire workspace dock chat to project context, views, and workspace actions #258

@kinqsradio, please wire the workspace chat dock into the application's view and workspace interaction contracts.

The frontend branch adds a persistent bottom dock, a project picker, saved project chat entry points, and retained drafts. The user requested that its implementation remain frontend only. This issue tracks the remaining context and action integration.

Requested behavior

• Carry the explicitly selected project through queued turns, resume, and saved history. “This project” should resolve to that project with fresh, permission-checked task and page context.
• Supply the active workspace pane, view, filters, and selected resource when relevant. Keep an established conversation's project scope explicit when navigation or the picker changes.
• Let chat inspect permitted project tasks and page contents, with authoritative source tracking and access revalidation.
• Route chat navigation through the workspace controller so it can open the relevant task, page, project, or view in the intended pane.
• Route proposed changes through existing approval and permission contracts, then refresh affected visible views after confirmed writes.
• Preserve drafts, cancellation, active runs, and session ownership across navigation, project changes, and account changes.

Acceptance

From the Projects list or another workspace view, select a project in the dock and ask which project is selected, what tasks need attention, and what a project page says. Answers should identify the selected project and use its permitted sources. Approved interactions should update or open the correct workspace view. Verify split panes, stale results after project/account changes, kept-out projects, reconnect, and saved-chat reopening.

Frontend foundation is in PR #259, targeting feat/web-rebuild.

This follow-up is separate from merging the frontend UI.