fix(docker): add missing t3code.Dockerfile

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer

[la14-1]

Why: Users running `spawn t3code --beta docker`, `--beta sandbox`, or in the `fast_provision` experiment group hit a runtime failure — `ghcr.io/openrouterteam/spawn-t3code:latest` doesn't exist because the Dockerfile was never added when t3code was introduced.

What

Adds `sh/docker/t3code.Dockerfile` following the exact same pattern as `pi.Dockerfile`:

• Base: `ubuntu:24.04`
• Runtime: Node.js 22 via n
• Install: `npm install -g t3`

All 9 other agents already have their Dockerfiles. This is the only one missing.

What's not included

The `.github/workflows/docker.yml` matrix update (adding `t3code` to the build matrix) is tracked in #3418 and requires human review — workflow files are off-limits for automated agents.

Checklist

• Dockerfile follows same structure as all other agent Dockerfiles
• install command matches `manifest.json` agents[`t3code`].install (`npm install -g t3`)

-- refactor/code-health

[la14-1]

CI status: Mock Tests failure is pre-existing — digitalocean-token.test.ts:118 (fetch mock count mismatch). This is the same flaky test addressed by #3406, not introduced by this PR. ShellCheck, Biome Lint, Unit Tests, and macOS Compatibility all pass. Branch is mergeable with no conflicts.

-- refactor/pr-maintainer

[la14-1]

Fixed failing digitalocean-token test (callCount mismatch at line 118 — Expected: 2, Received: 4).

Root cause: When telemetry.test.ts runs before digitalocean-token.test.ts, the telemetry singleton gets initialized with _enabled = true. During doApi's 401 recovery flow, logWarn() calls captureWarning() which fires fetch() to PostHog (fire-and-forget). This added 2 extra fetch calls that the test's callCount was counting.

Fix: Filter out PostHog telemetry URLs from the call count, so only DigitalOcean-related fetches are asserted.

-- refactor/pr-maintainer

[la14-1]

Rebased on main and resolved merge conflict in packages/cli/src/__tests__/digitalocean-token.test.ts. The conflict was between this PR's test fix and the one from #3425 (already merged to main) — kept the main version's relaxed assertion (toBeGreaterThanOrEqual(2)).

Branch is now clean and mergeable.

-- refactor/pr-maintainer