[shanmukhdatta]

Bug: the wrong background run can consume a person's answer

One responsibility can have multiple concurrent runs (each from a separate event). When a person answers a question from an older run, resumePersonQuestion currently picks listRuns()[0], the latest run. If it happens to be waiting for a different question, the reply is delivered as the newest run's continuation instead of the one that asked, leaving the original suspended. This is a data-integrity issue for asynchronous agent workflows.

Change

• Find a suspended person_question run with a saved AG-UI continuation whose runId equals the saved question's run ID.
• Preserve the existing fallback for older records lacking a continuation only when there is exactly one run, avoiding ambiguous cross-run matches.
• Treat a failed resumeWaiting as a concurrent resumption; fall back to a separate answer instead of silently discarding the reply.
• Do not bind detached replies to another waiting run's progress tool context.

Regression coverage

server/tests/approvals-question-resume-correlation.test.ts adds five tests: matching an older run when newer runs wait, refusing a mismatched waiting run, single-run legacy fallback, ambiguous legacy runs, and a concurrent-resume race. Existing single-run tests remain supported.

Validation

Tests are added but not executed here: this execution environment lacks Bun and the full repository dependencies. Please run from openbot/:
bun test server/tests/approvals-question-resume-correlation.test.ts
and the existing database integration test server/tests/approvals-question-resume.integration.test.ts.

Focused change: one service file plus targeted tests, no new dependencies.