feat(diff): head each bulk turn with a run-log dispatch banner#33
Merged
Conversation
A fanned-out run's diffs read as one flat wall: every entry repeated the whole breadcrumb inline (`[≡ root ≡] › item › submodule`) at the same weight as the diff body, so turn boundaries never stood out. Group a fanned-out run the way the run log announces a dispatch. Print an inverted `≡ root ≡` chip banner naming the turn once per turn, a `▸ parent › child` hand-off once per submodule path beneath it (root-free, so headers inside a turn read lighter), and the target line once per repo. DiffCollector.Print composes the pieces with three-level dedup; DiffHeader composes the same pieces for full mode. A single-module run keeps its plain `[name]` chip + target header, byte-for-byte unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jul 23, 2026
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
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
A fanned-out run's diffs read as one flat wall: every entry repeated the whole breadcrumb inline (
[≡ root ≡] › item › submodule) at the same weight as the diff body, so turn boundaries never stood out.This heads each bulk turn the way the run log already announces a dispatch:
≡ root ≡chip banner naming the turn, once per turn;▸ parent › childhand-off once per submodule path beneath it — root-free, so headers inside a turn read lighter;DiffCollector.Printcomposes these with three-level dedup;DiffHeadercomposes the same pieces for full mode. A single-module run keeps its plain[name]chip + target header, byte-for-byte unchanged.Before
After
(indigo chip + teal
▸in a real terminal)Testing
go build ./...,go vet ./..., fullgo test ./...— all green.TestDiffHeader_SubmoduleGetsRootFreeHandoffandTestDiffCollector_BannerOncePerTurnHandoffPerSubmodule.loom diffand--quick) to confirm real output.🤖 Generated with Claude Code