Skip to content

🎨: restore component policy replacement and ordering semantics - #1848

Open
merryman wants to merge 2 commits into
robin/morphic-change-enginefrom
robin/component-policy-runtime
Open

merryman wants to merge 2 commits into
robin/morphic-change-enginefrom
robin/component-policy-runtime

Conversation

@merryman

@merryman merryman commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Component policies could misorder add and replace commands or resolve replacements against the wrong master. Correct command ordering, embedded-part lookup, isolation across masters, and cleanup of dangling ordering anchors. Preserve replacement semantics for plain morphs, parts, and reloaded Text subclasses.

Component-runtime regressions cover chained insertion anchors, replacements without a preceding add, nested type inheritance, embedded parts, cross-master ownership, and reloaded Text classes. Owner/master ancestor scanning can still take quadratic time in hierarchy depth.

Refs #1149. This fixes runtime replacement and ordering semantics; generating replacement expressions remains open.

Extract the policy runtime semantics and component runtime regressions independently of the projectional core.

Extracted unchanged from 590ce0b..17a6068.
This local dry run preserves the original tree and introduces no new
foundation behavior. All higher slices remain absent from this head.
Test embedded-policy lookup, a distinct Text class identity, master scope
boundaries, and dangling runtime ordering references.

Cover plain replacement without an add command. Keep fresh inline parts
as an explicit policy-preservation control: they already bypass the plain
replacement branch.
@merryman
merryman force-pushed the robin/component-policy-runtime branch from 73f2261 to 9b724cc Compare November 5, 2026 10:46

This branch has not been deployed

No deployments
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