Skip to content

chore(runtime): remove Runlet sidechannel progress tracking - #216

Open
danielkov wants to merge 1 commit into
assess/acp-runlet-sidechannelfrom
feat/remove-runlet-sidechannel
Open

chore(runtime): remove Runlet sidechannel progress tracking#216
danielkov wants to merge 1 commit into
assess/acp-runlet-sidechannelfrom
feat/remove-runlet-sidechannel

Conversation

@danielkov

Copy link
Copy Markdown
Contributor

Summary

Remove Runlet-specific observation and stderr progress tracking now that nested tool calls use canonical ACP lifecycle notifications. This is the second PR in the stack, based on #215.

Motivation

Source-node matching and duplicate child lifecycle events are no longer needed to display nested compose activity. Removing them leaves ACP as the source of tool-call identity, content, and status.

Impact

The TUI retains grouped child calls and a bounded, neutral source view, without binding, loop, or retry-state annotations. General stderr diagnostics continue to carry session attachment, storage, compaction, subagent lifecycle, usage, activity, and cleanup information.

Technical details

The runtime delegates directly to RunletBackend.execute. Both observed-tool invocation paths retain canonical ACP projection.

The general diagnostic writer moves to its own module, preserving bounded publication, loss invalidation, heartbeat fairness, and leases. Its existing runlet_transport health tag remains unchanged. ACP capacity and terminal-display limits no longer depend on the removed progress model.

@kit-code-agent kit-code-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found. The changes look good to merge.

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