task: #3617533 Release Horizon Aid 1.0.0-alpha1

Release Horizon Aid 1.0.0-alpha1, the first release of the Horizon Aid site template recipe.

Issue: https://www.drupal.org/i/3617533

What this changes

• composer.json: version 1.0.x-dev → 1.0.0-alpha1.
• composer.json: all 19 cross-dependencies tightened off 1.0.x-dev to released constraints. Every one of them is a pre-release, and a pre-release sorts below its own release, so ~1.0.0 cannot set a minimum on 1.0.0-rc1: each constraint names its own pre-release instead.
  • ~1.0.0-rc1 — Varbase Admin Base, Varbase AI Base, Varbase API Base, Varbase Auth Base, Varbase Blog Base, Varbase Content Base, Varbase Dev Base, Varbase Editor Base, Varbase i18n Base, Varbase Media Base, Varbase Page Base, Varbase Performance Base, Varbase Security Base, Varbase SEO Base, Varbase Users Base, Varbase Webform Base, Varbase Workflow Base
  • ~1.0.0-alpha2 — Varbase Events Base, Vartheme BS5 Horizon Aid
• config/canvas.page_region.vartheme_bs5_horizonaid.header.yml: the header search icon-toggle placement gains panel: bar and expand_in_editor: true, matching the Varbase Starter default, and its component_version moves to c42c2d3c773c4f6c.
• config/canvas.component.sdc.vartheme_bs5_horizonaid.icon-toggle.yml: re-synced to the component the theme now provides at 1.0.0-alpha2 (active_version: c42c2d3c773c4f6c, adding the expand_in_editor and panel prop definitions). The stale 9b4c690eb740a9bd version is dropped, since nothing references it any more; shipping a stale hash fails Drupal Canvas hydration.
• tests/features/12-search/12-01-header-search.feature: follow the inline bar's own behaviour, see below.
• README.md: version badge → 1.0.0-alpha1.
• CHANGELOG.md: added, with the 1.0.0-alpha1 entry.

Zero x-dev constraints remain.

Why the header search scenarios changed

Turning the panel into an inline bar changes how it is operated, and two scenarios still drove the popover:

• Closing. The bar takes the toggle button's place on the header row while it is open: .icon-toggle__button gets visibility: hidden and the bar carries its own .icon-toggle__close. A second click on the toggle can no longer close it.
• Submitting. The bar is one line of icon, field and close, so the exposed form's .form-actions is clipped to 1×1 by design. Its submit button is not clickable, and the keywords field sits over it.

Both scenarios were therefore failing on a control that is deliberately not clickable, not on broken search. They now close the bar with its close control and send the query with Enter in the field. Verified in a browser that the flow lands on /search?keywords=water with the query carried back into the results filter.

This was reproduced and diagnosed rather than retried away: the same two scenarios failed identically on a plain job retry (22 scenarios, 2 failed, 20 passed twice), and pass 22/22 locally against a real install with the fix.

Verified

• Built a fresh DDEV Varbase 11 host from these constraints and completed the install through the browser's Horizon Aid site-template picker (not drush site:install). Composer resolved the theme to 1.0.0-alpha2.
• Install finished with zero .messages--error; 70 nodes (26 blog, 12 country, 24 event, 3 page, 5 program), 8 Drupal Canvas pages, 248 modules, default theme vartheme_bs5_horizonaid, front page off /user/login.
• Every shipped path returns 200: /, /about, /countries, /programs, /resources, /events, /donate, /impact, /search, /terms-and-conditions.
• /search renders exactly one h1, "Search".
• The header toggle renders icon-toggle--panel-bar, and the component entity reports a single version c42c2d3c773c4f6c on a fresh install, with the placement hydrating against it.
• The whole 12-search bucket passes locally: 22 scenarios (22 passed), 160 steps (160 passed).
• gitlab-ci-local green on Composer validate, YAML lint (493 files, 0 invalid), Cspell, ESLint and the Cucumber dry-run.
• Both install jobs (Varbase and Drupal CMS) pass in CI on these constraints.

AI-Generated: Yes

Checkpoints:

• File an issue
• Addition/Change/Update/Fix
• Testing to ensure no regression
• Automated unit testing coverage
• Automated functional testing coverage
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release