daemon.go has a default task flow (storage, run credential, model egress, State Store relay, ContainerPool.Acquire, admit, dispatch) and kit_task.go has runKitTask, which repeats the credential, brief and egress steps in its own order and calls KitLauncher.Launch. In the pool, Acquire and AcquireKit/StartKit are two ways to start a container under the same concurrency cap. A fix to one flow does not reach the other; the NATS token leak in both paths is an example.
Wanted
One task flow and one container start in the pool, shaped by #1865.
Done when
daemon has one function that runs a task in a container, and container.Pool has one acquire method.
## Problem
`daemon.go` has a default task flow (storage, run credential, model egress, State Store relay, `ContainerPool.Acquire`, admit, dispatch) and `kit_task.go` has `runKitTask`, which repeats the credential, brief and egress steps in its own order and calls `KitLauncher.Launch`. In the pool, `Acquire` and `AcquireKit`/`StartKit` are two ways to start a container under the same concurrency cap. A fix to one flow does not reach the other; the NATS token leak in both paths is an example.
## Wanted
One task flow and one container start in the pool, shaped by #1865.
## Done when
`daemon` has one function that runs a task in a container, and `container.Pool` has one acquire method.
With #1877 deleting the Kit path, this becomes: confirm only the default flow and `Pool.Acquire` remain. Close once #1877 lands, if nothing is left.
---
_Generated by [Claude Code](https://claude.ai/code)_
Closing: deleting the Kit path in #1877 leaves one run flow and one acquire method, so there is nothing separate to do.
---
_Generated by [Claude Code](https://claude.ai/code)_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
daemon.gohas a default task flow (storage, run credential, model egress, State Store relay,ContainerPool.Acquire, admit, dispatch) andkit_task.gohasrunKitTask, which repeats the credential, brief and egress steps in its own order and callsKitLauncher.Launch. In the pool,AcquireandAcquireKit/StartKitare two ways to start a container under the same concurrency cap. A fix to one flow does not reach the other; the NATS token leak in both paths is an example.Wanted
One task flow and one container start in the pool, shaped by #1865.
Done when
daemonhas one function that runs a task in a container, andcontainer.Poolhas one acquire method.With #1877 deleting the Kit path, this becomes: confirm only the default flow and
Pool.Acquireremain. Close once #1877 lands, if nothing is left.Generated by Claude Code
Closing: deleting the Kit path in #1877 leaves one run flow and one acquire method, so there is nothing separate to do.
Generated by Claude Code