fix(canvas): place new terminals near Home in free space - #76
Merged
Merged
Conversation
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
2 participants
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.
New terminals currently use
sessions.lengthfor placement, so with about 40 open cards the next one appears roughly 10,000 canvas pixels below Home even when nearby space is free. New terminal and agent cards now take the nearest free slot in a compact two-dimensional search around Home, avoiding existing canvas cards and reusing space after cards move or close. Pending launches reserve their slots, while an explicit drop position still takes precedence.Validation: 8 focused placement tests (including 45-card growth and freed-slot reuse) and the full 859-test suite passed;
npm run typecheck,npm run build, andgit diff --checkpassed.