chore: bump @plannotator/core 0.25.11 and @plannotator/ui 0.51.0

[backnotprop]

Version bump for the npm publish. Not published yet: publishing needs the owner's npm credentials. Merging this PR changes no runtime code; it is the version bump, bun.lock, and the HANDOFF entries.

Wanted now by Workspaces for the question fixes #1683, #1699 and #1702.

@plannotator/core 0.25.11 (patch, additive)

• question-block (fix(questions): plain-bullet choices keep their wrapped lines #1699, fix(questions): answers saved under a 0.28.1 label still show their pick #1702): plain-bullet choices keep their wrapped lines; a - **Name:** prose bullet takes Name as its label; labels over 200 chars are cut at the first sentence; Recommended: wraps like a paragraph. New QuestionChoice.aliases? and canonicalQuestionAnswer(question, answer), which maps an answer saved under an older plain-bullet label to the current one. Task-list choices and questionKey are unchanged. Behavior change for hosts that store answers: plain-bullet labels can differ from 0.25.10's, so a host that reads stored answers itself should pass them through canonicalQuestionAnswer (QuestionBlock already does).
• external-annotation (feat(tool): contract v2 with session ids, list and close #1709): ExternalAnnotationEvent gains { type: "session-closed", by: "agent", unsentAnnotations }. A host with an exhaustive never switch over the event type has to add the case.
• html-anchor (fix(export): image headings name the resolved file; diff comments sort after the document #1700): HtmlElementContext.sourceName? (validated); ELEMENT_CONTEXT_SHED_ORDER exported.
• model-catalog (feat(pi): offer Pi's thinking levels in Ask AI #1704): Pi thinking levels (PI_THINKING_LEVELS, piCatalogFromRpc, …) and an off effort label.
• agent-terminal / ai-context (Several files in one annotate review (0.29 PR 4, bundles) #1718): "annotate-bundle" mode; AnnotateContext.bundlePosition?.
• guide-viewer-manifest (Fix gruvbox positive diff colors #1721): pins the new viewer stylesheet viewer.DuqkfIUz.css (gruvbox diff colors). The viewer JS (viewer.BYGvfCcj.js) is unchanged.
• No new subpath exports; package.json exports are unchanged.

@plannotator/ui 0.51.0 (minor; BREAKING for 0.50.0 "Ask this session" consumers)

Pins core 0.25.11 exactly. It imports canonicalQuestionAnswer and PI_THINKING_LEVELS, so it cannot run on an older core.

• Breaking (fix(ai): Ask AI uses only the session when a session bridge is present #1685): "Ask this session" becomes the only Ask AI choice when a bridge is listed. Removed: findUsableSessionBridge, resolveSessionBridgeFallback, the 'fallback' SessionAskAction, SessionAskActions.fallbackLabel, and DocumentAIChatPanel.sessionAskFallbackLabel. Use findSessionBridge instead.
• Questions: pinpoint inside a card targets the prompt, context, or choice that was clicked (fix(ui): pinpoint in a question card targets what was clicked, not the prompt #1683, data-question-part). Card context renders through the document's block renderers (fix(questions): plain-bullet choices keep their wrapped lines #1699, new QuestionContext). Answers saved under an older label still show their pick (fix(questions): answers saved under a 0.28.1 label still show their pick #1702).
• Restore after an edit (fix(annotate): true line labels and Unanchored chips after a restore across an edit #1717): AnnotationRestoreReport.moved? and the new utils/annotationOwnsHighlight predicate.
• Drafts (Annotate drafts follow the file's path (0.29 PR 2) #1710): DraftTransport.save may resolve { staleGeneration }; also adds flushPendingSave().
• Agent close (feat(tool): contract v2 with session ids, list and close #1709): useExternalAnnotations({ onSessionClosed }), plus the new utils/agentClosed.
• HTML pinpoints and Ask AI (fix(annotate): tell the agent which image (or element) a pinpoint points at #1694, fix(export): image headings name the resolved file; diff comments sort after the document #1700): the element-naming quote, CommentAskAIContext.detail / elementIdentityForAskAI, the media file name in export headings, and diff-view comments exported after the document.
• Diagrams (feat(diagrams): Ask AI from a diagram comment #1695): Ask AI from a diagram comment, with optional onAskAI on DiagramViewer, DiagramPopout, MermaidBlock and GraphvizBlock.
• Composer (fix(ui): drop the ⌘↵ hint from the comment popover and the composer's Looks good on HTML #1693, fix(ui): drop the keyboard hint under the decision note composer #1711, feat(ui): bring the one-click thumbs-up back to the HTML pinpoint composer #1712): submit hints removed; onQuickLookGood unchanged (as 0.50.0).
• Ask this session (fix(ask): a prompt typed into an Ask-this-session turn takes it over on every host #1703, feat(ui): first-run announcement for Ask this session and non-blocking reviews #1690): session_taken_over is shown as a note (AIResponse.notice, SessionAskNote); new announcement dialog.
• Exports and linked docs (fix(annotate): folder sessions export each comment once #1696, Several files in one annotate review (0.29 PR 4, bundles) #1718): useLinkedDoc.getFeedbackDocuments(); exportLinkedDocAnnotations(…, heading?) with full-fidelity entries; bundle order for document groups; DocBadges.onBack optional; PlanHeaderMenu bundle ids.
• gruvbox (Fix gruvbox positive diff colors #1721): green added diff lines.
• Agent tool switch and offer (feat(ui): agent tool switch in Settings and a one-time offer on Pi and OpenCode 2 #1725, merged into this branch): Settings takes optional agentToolSetting + onAgentToolChange and renders the General row [data-agent-tool-setting] only when both are passed. New utils/agentToolSetting, hooks/useAgentToolSetting, utils/agentToolAnnouncement and components/AgentToolAnnouncementDialog (the one-time offer on Pi and OpenCode 2; nothing in the library mounts it). parseAgentToolSetting returns undefined unless the server sends agentToolHost and agentToolEnabled, so Workspaces sees no row and no offer. No core change.
• useAIProviderActivation (fix(ai): Ask AI uses only the session when a session bridge is present #1685): optional providers?; an id the server does not list is never activated.
• XMark and useLatchedTrue are documented as unsupported internal exports.

HANDOFF.md now covers every host-facing change since 0.50.0. The new section is "Questions, restore, drafts and the rest (ui 0.51.0, core 0.25.11)". Stale "unreleased" and "next ui release" headings now name 0.50.0 or 0.51.0, and the first "Publishing & versioning" bullet names this pair and its publish order. I checked the changed-file list against the published @plannotator/ui@0.50.0 tarball: every source file that differs maps to a commit in ba7d0159..main. origin/main is merged in (merge commit) so #1725 ships in ui 0.51.0; it touches no core file and leaves the manifest unchanged, so core stays 0.25.11.

guides.show manifest: CHANGED, deploy needed BEFORE publishing core

packages/core/guide-viewer-manifest.ts changed in #1721 (css: viewer.BCFKWQXh.css → viewer.DuqkfIUz.css). guides.show last deployed at v0.28.4 (0f787992), which predates #1721:

• https://guides.show/v1/viewer.DuqkfIUz.css → 404 (not live yet)
• https://guides.show/v1/viewer.BYGvfCcj.js → 200
• https://guides.show/v1/viewer.BCFKWQXh.css → 200 (the old pin)

If core is published first, every host's guide page would load without its stylesheet.

Publish order (owner)

# 1. guides.show: publish the new viewer CSS (add-only), then confirm it is live
gh workflow run guides-show-deploy.yml --ref main
gh run watch "$(gh run list --workflow guides-show-deploy.yml -L 1 --json databaseId -q '.[0].databaseId')"
curl -sI https://guides.show/v1/viewer.DuqkfIUz.css | head -1   # expect 200
curl -sI https://guides.show/v1/viewer.BYGvfCcj.js  | head -1   # expect 200

# 2. after this PR merges, from an up-to-date main
git checkout main && git pull && bun install --frozen-lockfile
bun run --cwd packages/ui smoke:package

# 3. core first, then ui (no --provenance locally)
cd packages/core && npm publish --access public && cd ../..
cd packages/ui && npm publish --access public && cd ../..

To preflight under next first, add --tag next to both npm publish commands, then promote with npm dist-tag add @plannotator/core@0.25.11 latest and npm dist-tag add @plannotator/ui@0.51.0 latest.

Verified locally

• bun run --cwd packages/ui smoke:package passes. It packs ui 0.51.0 and the local core 0.25.11, then installs both with pnpm in an outside consumer, which builds and typechecks. As expected, it notes that core 0.25.11 is not on the registry yet.
• bun run typecheck passes, including packages/ui/tsconfig.strict-consumer.json.
• The UI seam-contract and DOM tests from test.yml pass (1478 tests), and so does the isolated file-browser DOM test.
• bun test packages/ui packages/core passes (after the feat(ui): agent tool switch in Settings and a one-time offer on Pi and OpenCode 2 #1725 merge: 1560 pass, 0 fail), and so do feat(ui): agent tool switch in Settings and a one-time offer on Pi and OpenCode 2 #1725's DOM tests (Settings.agentTool, AgentToolAnnouncementDialog).
• bun install --frozen-lockfile reports a clean lockfile.