v2.14.1

Fixed

• Block bindings in post content resolve against the record — HasRenderedBlockContent::renderContent() (the rendered_content accessor visual-editor's core/post-content block reads) now renders with a visual-editor BindingContext for the model. custom_field, post_core and relation bindings inside a record's body previously fell back to their static values on the front end, because the accessor runs before the template's own render sets a binding context. Soft integration as before: with no visual-editor installed nothing changes, and visual-editor versions before 1.14.0 ignore the context.
• text / link / border palette slugs no longer override picked colors — those slugs' .has-{slug}-color rules share their class name with the has-text-color / has-link-color / has-border-color block-support markers, so GlobalStylesEmitter forced the slug's color onto every block with a custom color (e.g. a button with a palette text color rendered in the theme's text color). Each of those slugs now gets an exact .has-{slug}-color-preset rule (visual-editor 1.14.1's Blade renderer adds that class to blocks that pick the slug as their text color), and the .has-{slug}-color rule becomes a zero-specificity fallback for other markup: it skips elements with an inline color:, requires has-text-color for link / border, and is emitted last with text after link / border, so a block that picked text and also has a link or border color keeps its text color. The emitter's cache schema version moves to v5, so cached CSS regenerates on upgrade. Pairs with visual-editor 1.14.1.