[Improve] Make guided agent interactions reliable

[roomote-roomote]

​Created by Roomote. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Add optional setup discovery for supported document, monitoring, and project-tracking integrations, with curated matching, secure configuration dialogs, skip/reorder support, and automatic continuation when nothing matches.
• Make guided input durable and replay-safe: persist stable option IDs with label compatibility, record the responding human, keep responses in transcript chronology, suppress duplicate successful tool rows, and preserve failed rows.
• Reconcile setup state and canonical receipts idempotently across live execution and queue recovery so saved answers, starter choices, and completed setup cards continue reliably without duplicate turns.
• Share effective integration status and cache invalidation across setup and Settings so connection/configuration changes refresh availability and Fast tool discovery.
• Harden Discord guided-input callbacks with stronger request tokens, active reply-target checks, and safe rebinding across snapshot resumes; document the optional integration flow.
• Replay the exact 21-commit guided-interaction patch series directly onto current develop, preserving all eight Bruno-authored commits and removing unrelated release/hotfix ancestry.
• Correct two stale DB test fixtures exposed by the exact-head CI run: invalid declarative YAML now omits the required name, and concurrent provider probes receive independent mocked responses.

Why this change was made

Guided setup could lose or misattribute answers, duplicate transcript activity, strand saved responses before continuation, and show stale integration availability. The branch also carried unrelated release and hotfix ancestry that obscured the actual review scope, while uncached DB execution exposed test fixtures that no longer matched current behavior or concurrency.

Impact

Guided interactions remain coherent across reloads, retries, concurrent submissions, recovery, and supported chat surfaces, while optional integration discovery stays non-blocking. The PR now contains 23 commits and 88 changed files relative to develop: 21 patch-equivalent guided-interaction commits plus two one-line DB test corrections.

The complete DB suite passes on a newly created test database (779/779). The previously failing StepAuthEnvVars.client.test.tsx test passes locally (18/18), the full web client suite passes (2,534/2,534), and lint, fast type checks, Knip, formatting, and pre-push gates pass. All substantive exact-head GitHub checks pass, including Test and Roomote code review, with every review thread resolved on 5340f39c8525665fc4ae2cd4b947fba1e97eecd8.

Authenticated browser behavior and external OAuth completion were not revalidated during this history and test-isolation cleanup; no browser or OAuth proof is claimed.

[roomote-community]

No new code issues found. See task

• packages/sdk/src/server/lib/fast-agent-parent-event.ts:2530 Durable setup-turn recovery schedules continuation after zero-match discovery.
• apps/web/src/trpc/commands/fast-sessions/index.ts:977 Structured responses persist the submitting user's identity.
• apps/worker/src/mcp/roomote-mcp-server/user-personalization.ts:18 Opt-out or rejected learning attempts are recorded as successful personalization updates. — dismissed: no longer changed by this PR.
• packages/cloud-agents/src/server/user-personalization.ts:85 Runtime instructions apply private preferences to code and deliverables despite the documented conversation-only scope. — dismissed: no longer changed by this PR.

_{Reviewed 5340f39}

[roomote-roomote]

Resolved the requested findings through 006ca45: zero-match discovery schedules the next setup turn in live and durable-recovery paths, and canonical responses persist the actual submitting user. The specifically linked failed check belongs to duplicate PR #2475; its additional run-scoped cleanup and setup-collaboration findings are also fixed, all related threads are resolved, and its checklist reflects the final state. #2473’s current Roomote review passed with no code issues. Focused web and SDK suites plus repository pre-push gates passed; browser/OAuth proof remains unavailable.

[roomote-roomote]

Cleaned the existing PR branch through 5340f39c: all 21 guided-interaction patches and eight Bruno-authored commits are preserved on current develop, unrelated release/hotfix ancestry is gone, and the two DB test fixtures exposed by uncached CI execution are corrected. The PR now has 23 commits and 88 changed files; Test, Roomote code review, and every other substantive exact-head check pass, and all review threads are resolved.