Implement run orchestration in df-agent-channel #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "iter1/run-orchestration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
New crate df-agent-channel (openspec iter1-run-orchestration): the
control-plane side of the agent protocol, mounted by
dark-factory serve.(URI SAN, peer IP via SandboxProvider::resolve_identity). TLS material
is reloaded on rotation (checked at most every 10 s), handshakes are
bounded in time and count.
persistence with cumulative acks, dedup and gap detection, transcript
storage with blob extraction, prompt (re-)delivery and wall-clock Cancel
counted from the runtime's first Hello. Effects of committed messages
run even before a gap; tool calls and credentials are refused once the
run ended.
tick, background provisioning, provider events, connect timeout and
hard stop; continuation summary keeps the newest messages.
forge is called outside any transaction), PR lifecycle (draft on push,
ready + completion summary on completion), Git credential grants.
drains provisioning, main waits SHUTDOWN_GRACE before aborting.
holds the df-core sections; Helm configmap sets agent.tls.
iter1-sandbox-provisioning and iter1-integration-plugins land.
variant for tests. Remote Bazel is blocked by a pre-existing toolchain
issue (docs/bazel-remote-toolchain.md); verified locally.
docs/tech_debt.md.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com