Paul BakausandClaude Code 0c18cbc9ef fix: stop treating the child combinator as a prelude boundary when pruning ...

removeSelectorAt walked backward to find the rule prelude and stopped at
any '>', added so the walk would not escape past the <style> open tag.
That same character is the CSS child combinator, so pruning one unused
selector from a list like '.wrap > .orphan, .orphan' cut the prelude
mid-list; when every remaining fragment equaled the flagged selector, the
whole-rule branch then deleted from the cut point and left a dangling
'.wrap >' in source. A '>' now bounds the walk only when it actually
closes a <style ...> tag; combinators are walked through.

Regression tests cover a mid-list combinator prune and the dangling-
fragment shape (verified failing on the previous code).

AI-assisted (Claude Code).

Co-Authored-By: Claude Code <noreply@anthropic.com>

2026-07-28 18:05:41 -07:00

..

agents

Review fidelity against the comp itself, not the builder's summary of it

2026-07-27 15:13:27 -07:00

reference

fix: Cursor notify pattern covers every dispatchable event type

2026-07-27 19:32:30 -07:00

scripts

fix: stop treating the child combinator as a prelude boundary when pruning

2026-07-28 18:05:41 -07:00

SKILL.src.md

The polish ceiling covers the whole cycle, and the handoffs end it

2026-07-25 19:16:17 -07:00