[Feature]: Add project-level questions and coordination chat

[roomote-community]

Problem

Questions and steering currently live inside individual task threads, making project-wide decisions and control difficult to discover and answer once.

Proposed behavior

Promote relevant task questions into durable project questions with item/milestone/project blocking scope, evidence, options, recommendations, assignment, and answer audit. Link one durable Roomote coordination task/thread to Project Chat and route explicit project, milestone, item, or task targets.

Reuse request_user_input, existing web question cards, communication-surface question transports, task follow-up/resume, actor handoff safety, and task transcripts.

Acceptance criteria

• Item questions block only affected work; project questions pause the project.
• Equivalent questions are deduplicated.
• One answer from web or linked chat resolves the originating request once.
• Direct task steering remains actor-safe.
• Ambiguous project messages are never broadcast to every task.

Dependencies

• [Feature]: Link project plan items to existing Roomote task execution and controls #1041
• [Feature]: Add the project event timeline and audited control commands #1043

[roomote-community]

I've analyzed this issue and here's my proposed implementation plan:

1. After [Feature]: Link project plan items to existing Roomote task execution and controls #1041 and [Feature]: Add the project event timeline and audited control commands #1043 establish project execution and events, extend packages/db/src/schema.ts and the project service layer from [Feature]: Add the project planning domain model and authorization foundation #1037 with durable project questions, linked origin requests, and answers. Store scope (item, milestone, or project), target, evidence, options, recommendation, assignee, originating task/run/request IDs, resolution actor/time/source, and a normalized fingerprint with an active-question uniqueness constraint for deduplication.
2. Promote eligible request_user_input events through apps/worker/src/callbacks/communication.ts and a typed packages/sdk procedure. Keep ACP question/answer shapes from packages/types/src/acp.ts, but make the database record authoritative rather than the current Redis-only pending state in packages/communication/src/request-user-input.ts.
3. Add one transactional answer command shared by the project web UI and communication handlers. It should conditionally claim an unanswered question, append the audited project event from [Feature]: Add the project event timeline and audited control commands #1043, and deliver the answer once to every linked originating request using the existing sandbox/communication answer paths. Concurrent or repeated answers should return the stored result without re-enqueueing.
4. Apply blocking through the project readiness/control services: item questions block only their item and dependants that cannot proceed, milestone questions block that milestone's remaining work, and project questions set the durable project pause state from [Feature]: Add the project event timeline and audited control commands #1043. Resolution should recompute readiness without marking work accepted.
5. Implement the Questions and Chat surfaces in the project workspace introduced by [Feature]: Add the Projects dashboard and manual project setup #1038, reusing PendingUserInputRequestCard.tsx patterns for options and custom answers. Show scope, evidence, recommendation, assignment, answer audit, and links to originating task transcripts. Link Project Chat to one normal coordination task created through the [Feature]: Link project plan items to existing Roomote task execution and controls #1041 launch path so its transcript, follow-ups, wake/resume, and cancellation remain standard Roomote behavior.
6. Route Project Chat messages through a project command service: explicit project or milestone targets go to the coordination task, while explicit item or task targets resolve to exactly one linked task and use the actor-safe delivery behavior in apps/api/src/handlers/tasks/sendMessageToTask.ts and apps/web/src/trpc/commands/sandbox-session/index.ts. Ambiguous messages stay in the coordination task for clarification and are never broadcast.
7. Add database/service tests for scope blocking, normalized deduplication, authorization, answer races, event auditing, and exactly-once origin delivery; worker/API tests for web-versus-chat answer races and actor handoff; and responsive web tests for project Questions/Chat rendering and routing. Update apps/docs/ with question scopes, coordination-chat targeting, and non-broadcast behavior.

This approach keeps project coordination durable and auditable while reusing Roomote's existing task runtime, transcripts, structured-question UI, communication transports, and actor-safety rules rather than introducing a second execution system.

Please tag @roomote if you'd like me to implement this, or reply with feedback on the plan.