chore(runtime): remove Runlet sidechannel progress tracking - #216
Merged
Merged
Conversation
![kit-code-agent[bot]](https://avatars.githubusercontent.com/in/4797102?s=60&v=4){kind=small}
danielkov
added this pull request to stack #217
September 14, 2026 08:53
stack merge was automatically disabled
September 14, 2026 08:53
Pull Request is not mergeable
danielkov
force-pushed
the
feat/remove-runlet-sidechannel
branch
from
September 14, 2026 08:53
16c31a4 to
b83b553
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_transporthealth tag remains unchanged. ACP capacity and terminal-display limits no longer depend on the removed progress model.