bookwright v1.4.0

Added

• Explicit target/domain API and steps boundaries enforced by architecture self-tests and ADR 0011.
• Typed Sauce Demo, local-user, and database fixtures with source-level ownership checks and ADR 0012.
• Typed, owner-local JUnit state contracts with architecture checks and ADR 0013.
• A minimal Java booking application backed by the same private MySQL service used by database tests.
• An API → DB-over-SSH verification → API cleanup scenario with deterministic data and LIFO fallback cleanup.
• An independent integration quality gate whose results are merged into the published Allure report.
• NEW and EXISTING user fixtures with typed, secret-safe credentials, profiles, and API sessions.
• Local user registration, PBKDF2 password storage, hashed session tokens, authenticated cleanup, and a protected UI page.
• Playwright session-cookie injection and concurrent integration scenarios for new, existing, missing, and rejected sessions.
• A changelog style gate that prevents release-note bullets from repeating their section heading.

Changed

• Split restful-booker health, auth, and bookings from local auth, users, and bookings, with compact target facades for API and UI tests.
• Replaced the monolithic UI steps class with focused Sauce Demo login, inventory, and checkout domains plus local booking UI steps.
• Moved scenario selection out of steps and product tests into immutable fixtures or reproducible per-test data.
• Reduced NamespaceRegistry to scope creation, made generic test-store access internal, and established @WithAuthSession as the single restful-booker auth fixture.
• The isolated local launcher now supports an opt-in integrated Compose profile and dynamically discovers the application port.
• Unrelated local-application scenarios no longer submit a login form; Sauce Demo examples retain it because the public target exposes no supported authentication API.