Skip to content

fix: allow sibling placement inside repeated markup containers - #58

Open
MelmacAlpha wants to merge 1 commit into
flowtricks:mainfrom
MelmacAlpha:codex/repeated-markup-sibling-placement
Open

MelmacAlpha wants to merge 1 commit into
flowtricks:mainfrom
MelmacAlpha:codex/repeated-markup-sibling-placement

Conversation

@MelmacAlpha

@MelmacAlpha MelmacAlpha commented Oct 25, 2026 •

Copy link
Copy Markdown

Navigator moves beside elements inside repeated markup containers were rejected and could fall back to a whole-page diff that exceeded the resource limit. Determine sibling placement from the immediate source parent so moves within an element or component preserve the original bytes and loop bindings. Direct JavaScript return roots remain protected.

Adds 50 IPC regression cases covering sibling and edge placement, nested scopes, exact Undo, external writers, and code-owned return roots, and updates the contract documentation.

Validation: the complete local pre-push gate passed all 382 test suites, including strict TypeScript, ESLint, production builds, and Studio verification.

made-with-codex-gray-animated

Use the immediate source parent to distinguish ordinary markup children from JavaScript return roots. This keeps navigator moves within map containers on the byte relocation path instead of falling back to a whole-page diff and hitting its resource limit.

Add 50 IPC regression cases for sibling and edge placement, nested scopes, exact Undo, external writers and code-owned return roots. The full local gate passes all 382 suites; the live hpmaas renderer move applies in two splices and Undo restores its original bytes.
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