Skip to content

(CODUX-215) Propagate Drive context through provider execution - #2942

Merged
numnx merged 1 commit into
feature/CODUX-215-google-drive-project-mount-integrationfrom
task/feature-codux-21-t04-codex-a3f625ce-mrgwyqs4
Jul 11, 2026
Merged

(CODUX-215) Propagate Drive context through provider execution#2942
numnx merged 1 commit into
feature/CODUX-215-google-drive-project-mount-integrationfrom
task/feature-codux-21-t04-codex-a3f625ce-mrgwyqs4

Conversation

@numnx

@numnx numnx commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

🧩 Task: Propagate Drive context through provider execution

Automated task PR opened by Code UX for T04.

📋 Summary

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

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:05:59 UTC
Finished 2026-07-11 22:12:02 UTC
Duration 6m 4s

📊 Token Usage

Metric Value
Input tokens 117,580
Cached input tokens 2,970,368
Output tokens 12,455
Total tokens 3,100,403
Invocations 1
Tool calls 32
Active time 5m 24s

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

✅ 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
Integrate Google Drive context into the shared provider execution path and every production constructor that can launch planning, setup, task, QA, CI, merge, or Project Manager containers.

## Scope
- `src/services/provider-execution-service.ts`
- `src/services/planning-agent-service.ts`
- `src/services/project-setup-service.ts`
- `src/services/virtual-worker-service.ts`
- `src/services/quality-assurance-service.ts`
- `src/services/cli-workflow-service.ts`
- `src/services/cli-workflow/pipeline/pipeline-context.ts`
- `src/services/cli-workflow/pipeline/execute-provider-stage.ts`
- `src/app/dependency-factory/dashboard-factory.ts`
- `src/app/dependency-factory/sprint-factory.ts`
- `tests/backend/services/provider-execution-service.test.ts`
- `tests/backend/services/planning-agent-service.test.ts`
- `tests/backend/services/project-setup-service.test.ts`
- `tests/backend/services/virtual-worker-service.test.ts`
- `tests/backend/services/quality-assurance-service.test.ts`
- `tests/backend/services/cli-workflow-service.test.ts`
- `tests/backend/services/chat-management-action-service.test.ts` for the shared Project Manager route.

## Implementation Requirements
1. Give `ProviderExecutionService` access to the effective project/sprint settings and resolve Google Drive runtime context once before provider retries or session continuation; compose the notice once and pass the same mount to every provider attempt.
2. Thread the resolver or settings dependency through the dashboard and sprint factories, planning/setup fallbacks, virtual-worker and QA services, and CLI workflow pipeline so task workers and shared Project Manager execution use the same behavior.
3. Verify that the dashboard chat path through `ChatThreadRuntimeService` and `ChatManagementActionService`, task coding, planning, project setup, QA, CI repair, merge repair, and resumed invocations all receive the mount only when Docker mode and a valid linked directory are present.
4. Preserve persistent-skill prompt/mount composition, MCP filtering, invocation audit messages, retry prompts, effective sprint overrides, and provider telemetry while adding focused regression coverage for prompt idempotency and mount forwarding.

## Constraints
- Do not duplicate Google Drive-specific logic in each provider route; centralize resolution and prompt composition at the provider execution boundary.
- Use sprint-effective settings when a sprint id is available and project-effective settings otherwise.
- Do not claim Drive availability or expose a mount for host-mode execution, invalid paths, disabled settings, or unscoped invocations.
- Do not modify provider routing policy, task scheduling, Git behavior, or Project Manager message semantics.

## Verification
- Run `pnpm exec vitest run tests/backend/services/provider-execution-service.test.ts tests/backend/services/planning-agent-service.test.ts tests/backend/services/project-setup-service.test.ts tests/backend/services/virtual-worker-service.test.ts tests/backend/services/quality-assurance-service.test.ts tests/backend/services/cli-workflow-service.test.ts tests/backend/services/chat-management-action-service.test.ts`.
- Assert that worker and Project Manager prompts contain one Drive notice, retries retain one notice, read-only/read-write mounts are forwarded correctly, and missing settings leave existing calls unchanged.
- Run `pnpm run lint`.
🌿 Branch Info

Base: feature/CODUX-215-google-drive-project-mount-integration
Head: task/feature-codux-21-t04-codex-a3f625ce-mrgwyqs4


🤖 Generated by Code UX

@numnx
numnx merged commit be14b0f into feature/CODUX-215-google-drive-project-mount-integration Jul 11, 2026
20 checks passed
@numnx
numnx deleted the task/feature-codux-21-t04-codex-a3f625ce-mrgwyqs4 branch July 11, 2026 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant