horizonaid 1.0.0

Automated Functional Acceptance Testing Features

Setup Horizon Aid Locally with:

The Drupal CMS installer with DDEV

mkdir ~/workspace/projects/my-drupal-site-horizonaid && cd ~/workspace/projects/my-drupal-site-horizonaid
ddev config --project-type=drupal11 --docroot=web
ddev composer create-project drupal/cms
ddev launch

Highlighted important changes

• First stable release. No functional change to the recipe from 1.0.0-rc1.
• Installs on Drupal CMS with no extra configuration. A stock drupal/cms root ships minimum-stability: stable. While every published version was a pre-release, a site builder had to run composer config minimum-stability dev before drupal/horizonaid would resolve. The stability setting was the gate rather than the version constraint: ~1 normalizes to a lower bound of 1.0.0.0-dev and an upper bound below 2.0.0.0, so it already admitted a pre-release once stability permitted. With 1.0.0, composer require drupal/horizonaid works on an untouched Drupal CMS root.
• Every cross-dependency names a stable constraint: the sixteen varbase_*_base recipes and Vartheme BS5 Horizon Aid 1.0.0, all at ~1.0.0, all resolving to a published stable release. A stable Horizon Aid requires no pre-release.

Added

• test: #3621203 Name the color-contrast and page-has-heading-one accessibility rules in the home page regression scenarios, with an explicit single-h1 assertion.

Verified

• Browser installs on both supported bases, a plain Drupal CMS root and a drupal/varbase_project root, each reaching the shipped state with no rescue cache rebuild: every page 200, 70 nodes, 8 Canvas pages, 74 media items, 25 taxonomy terms, 248 enabled extensions, home page 21 images with 0 broken and 0 console errors. All eight Canvas page editors mount cleanly.