v0.19.0

What's Changed

Fixed

• Pinned parisek/styleguide to >=1.11,<1.18 (#89). parisek/styleguide
  1.18.0 (PR parisek/styleguide#144) changed Renderer::render() from
  returning an HTML string plus an http_response_code() side effect to
  returning a Result object carrying the status, but
  Styleguide::renderObserved() — the method FixtureAudit\Auditor uses —
  was not updated to forward that status: it takes only ->body from the
  Result and its own return array has no status key at all.
  Auditor::renderFixture() detects a fixture render failure by resetting
  http_response_code(200) and reading it back after the render (documented
  by Renderer::render() itself as the stable signal); with nothing calling
  http_response_code() any more, Auditor can no longer tell a failed
  render (component/broken's {{ 1 / 0 }}) from a successful one — every
  fixture reads back OK regardless of whether it actually rendered.
  fields-contract's render-failure detection has no other signal to fall
  back on without an upstream change to renderObserved()'s return shape, so
  the constraint is capped below 1.18.0 (last known-good: 1.17.0) until
  parisek/styleguide restores an observable status. Confirmed
  parisek/styleguide 1.17.0 through 1.19.0-adjacent CI drift was the sole
  cause: composer install from a clean checkout of main reproduced the
  same 5 AuditorTest failures purely from the unpinned constraint floating
  onto 1.19.0, with no other change involved.
• fields-migrate on a component now strips the twig front-comment once
  <name>.yaml is written, the same way page/doc migration always has
  (#84). Component migration used to leave the comment on the twig, so every
  migrated component carried its metadata twice — proven downstream on a
  49-component Drupal project where every already-migrated component still
  opened with the same name:/usage:/category: block its <name>.yaml
  already recorded. The strip happens only after the yaml write completes,
  mirroring the existing page/doc write-then-strip order.

Added

• fields-migrate --strip-comment [--write] <component-dir>|--root=<root>
  retires the front-comment on a component that was already migrated before
  the fix above, without re-deriving anything. It removes the comment only
  when every key it carries matches <name>.yaml — normalising a
  comma-separated usage: against a yaml list — and refuses the component,
  per key, when the yaml disagrees or is missing a key, printing what
  differs. Dry run by default, like --rename-structural-types.

Pull Requests

• #88 — fix(migrate): strip a component's twig front-comment after migration
• #90 — fix(deps): cap parisek/styleguide below the render-status regression

Full Changelog: v0.18.1...v0.19.0