fix: Add empty line before result marker for visual continuity (#73) #76
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
Fixes the visual continuity issue in docker isolation mode by adding an empty line before the result marker (✓/✗) after command output.
Fixes #73
Problem
When running commands in docker isolation mode, the output lacked visual separation between the command output and the result marker:
Before:
After:
Solution
The fix ensures all commands (virtual and actual) follow a consistent visual pattern:
$ ...)✓or✗)Changes
console.log()before result marker indocker-utils.jsprintln!()before result marker inisolation.rsTest Plan
cd js && bun test- 54 tests passcd rust && cargo test- 22 output_blocks tests pass🤖 Generated with Claude Code