(CODUX-215) Cover direct worker-inbox Drive runs

[numnx]

🧩 Task: Cover direct worker-inbox Drive runs

Automated task PR opened by Code UX for T05.

📋 Summary

Sprint: Sprint 215 · Google Drive project mount integration · Task: T05

Add an opt-in, project-scoped Google Drive sync-directory mount for Docker Project Manager and worker containers, with an idempotent prompt notice, safe read-only defaults, configurable read/write access, and documented settings behavior.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-11 22:06:00 UTC
Finished	2026-07-11 22:12:19 UTC
Duration	6m 19s

📊 Token Usage

Metric	Value
Input tokens	89,605
Cached input tokens	1,922,560
Output tokens	12,781
Total tokens	2,024,946
Invocations	1
Tool calls	27
Active time	5m 38s

Included usage estimate (subscription/local login): $1.79

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Update direct `WorkerInboxReplyService` provider invocations so dashboard replies, thread compaction, and clarification replies receive the same Google Drive context as shared Project Manager and worker runs.

## Scope
- `src/services/worker-inbox-reply-service.ts`
- `tests/backend/services/worker-inbox-reply-service.test.ts`
- Consume the settings contract from T01, runtime resolver/prompt helpers from T02, and provider input field from T03.

## Implementation Requirements
1. Resolve the effective project/sprint Google Drive settings alongside the existing dashboard settings in `generateReply` and `generateClarificationReply`.
2. Compose the idempotent Drive notice before provider prompt construction and pass the validated runtime mount to `runProvider` for dashboard replies, compact-thread runs, and clarification replies.
3. Keep invocation prompt records aligned with the prompt actually sent, preserve persistent-skill and MCP context, and ensure direct calls use the same fixed container target and access mode as the shared execution path.
4. Add regressions for valid read-only/read-write mounts, invalid paths, host mode, compact-thread coverage, clarification coverage, and duplicate-safe prompt composition.

## Constraints
- Do not refactor direct worker-inbox execution into a different service or change reply parsing, routing, concurrency, or clarification behavior.
- Do not mount anything for host execution or invalid/missing Drive sources.
- Keep host paths out of persisted agent prompts and user-visible reply content.

## Verification
- Run `pnpm exec vitest run tests/backend/services/worker-inbox-reply-service.test.ts`.
- Confirm direct provider-runner calls receive the expected mount and exactly one Drive notice without changing existing persistent-skill behavior.
- Run `pnpm run lint`.

🌿 Branch Info

Base: feature/CODUX-215-google-drive-project-mount-integration
Head: task/feature-codux-21-t05-codex-4f9d8d30-mrgwysob

---

🤖 Generated by Code UX