Skip to content

Upstream's new ProviderTurnStartService memory test fails: the fork's InlineShellStore isn't provided #70

Closed

Description

@tannerpolley

Found 2026-10-20. apps/server/src/orchestration-v2/ProviderTurnStartService.memory.test.ts arrived with today's upstream sync (upstream pingdotgg#22117, 4f5ff17). All 5 of its tests fail on main: the fork's ProviderTurnStartService requires the fork's InlineShellStore (78beec8, inline shell runs), and upstream's test layer doesn't provide it.

Fix (modular, #24): the fork's dependency on InlineShellStore inside the upstream service should be optional, through Effect.serviceOption or a small fork hook, so upstream's test layers keep working unchanged. Alternatively, provide it from a fork-owned test harness. Don't edit upstream's test file.

Process gap: the sync ran tests only for files the merge touched, so a newly added upstream test that exercises fork-modified services was never run. The daily sync's checks should also run every test file the sync added or changed under apps/server.

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    on Oct 20, 2026
  2. tannerpolley commented on Oct 21, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code status: Done

    Issue: #70 Upstream's new ProviderTurnStartService memory test fails: the fork's InlineShellStore isn't provided

    Thread: thread:delegated-task:command%3Amcp%3A667e5306-5428-4b55-a9f6-4ae3fcb3609b%3Adelegate-task%3Aissue-70-worker-1

    Model: gpt-6.1-sol

    Branch: issue-70-upstreams-new-providerturnstartservice

    Updated: 2026-10-21T00:48:05.368Z

  3. tannerpolley commented on Oct 21, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: done

    Issue: #70 Upstream's new ProviderTurnStartService memory test fails: the fork's InlineShellStore isn't provided
    Thread: thread:delegated-task:command%3Amcp%3A667e5306-5428-4b55-a9f6-4ae3fcb3609b%3Adelegate-task%3Aissue-70-worker-1
    Model: gpt-6.1-sol
    Branch: issue-70-upstreams-new-providerturnstartservice
    Completed: 2026-10-21T00:48:04.712Z

    Implemented and pushed the fix for #70.

    • Branch: issue-70-upstreams-new-providerturnstartservice
    • Commit: b9f6efde30
    • Working tree: clean; remote branch matches the commit.
    • Commit includes Closes #70 and the requested co-author trailer.

    ProviderTurnStartService now reads InlineShellStore through Effect.serviceOption and removes it from the layer’s required dependencies. When absent, it uses the original provider session directly. When present, it retains the existing inline-shell delivery and error handling.

    Production wiring in runtimeLayer.ts is unchanged and still provides InlineShellStore.layer. The existing fork test confirming shell output injection into provider prompts passes. Upstream’s memory test file is unchanged.

    Validation passed:

    • 51 tests across five files: both requested ProviderTurnStartService files, InlineShellStore, InlineShellRuns, and InlineShellLaunch.
    • Server tsc-rs --noEmit: exit 0; advisory suggestions only.
    • Changed-file formatting and lint: exit 0; lint reported four existing unused-symbol warnings.
    • git diff --check: passed.

    Other upstream service constructors with hard fork-only dependencies found:

    • ProviderTurnControlService → InlineShellStore
    • ProjectService → SidebarLayoutService
    • WorktreeMcpService → ThreadWorkspaceService

    Those dependencies remain unchanged and have explicit test-layer provisions. The scan also found fork-only lookups in environment and preview MCP handlers, outside service constructors.

    No servers, live userdata, repo-wide checks, PR creation, or merge were performed. Review and integration remain with the parent task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions