# Validation record — 4.8.0 review fixes

Recorded October 8, 2026. This is a focused validation record, not a security
certification or a claim that every integration has been tested.

## Environment

- Two disposable WordPress 7.1.3 installations, one for Free and one for Pro.
- PHP 8.2.29 and MySQL 8.4.0, using a dedicated local socket-only database.
- Network requests and email delivery blocked on the test sites; automatic
  cron disabled. No real customers, production database, or provider keys.
- Pro activation and these shared behaviors were checked without a paid
  license; paid provider workflows were not exercised.

## Recorded checks

| Check | Result |
| --- | --- |
| Fresh installation and plugin activation | Free and Pro passed on WordPress 7.1.3 |
| PHP syntax checks | 708 PHP files across both packages; zero failures |
| Focused integration runner | 31 assertions passed for each edition |
| Plugin/theme coexistence | Both editions activated with Astra 4.14.0, Elementor 4.3.4, and LiteSpeed Cache 7.9.1; the regression runner passed again |
| Public HTTP rendering | Booking and staff pages returned 200; both had the Yatoon Apple touch icon |
| Manifest HTTP responses | Booking/staff manifests returned 200 and valid JSON with the default icons for both editions |
| PO syntax/counts | GNU msgfmt accepted all seven catalogs in each edition; 3,258 translated / 5,725 total messages per catalog (56.9%) |

The first cold-start check exposed translations being requested before `init`
by cron schedule labels. Activator, job queue, and backup schedule labels now
use untranslated display names before `init` and translated names afterward.
Scheduling keys and intervals are unchanged. This case is covered by the runner.

## Reproduce

See `tests/README.md` for the guarded WP-CLI runner. For catalog checks:

```sh
msgfmt --statistics -o /dev/null wp-content/plugins/yatoon-booking-system/languages/yatoon-booking-system-es_ES.po
```

For a complete static scan, install the official WordPress Plugin Check plugin:

```sh
wp plugin check yatoon-booking-system --mode=update --format=strict-json
```

## Static scan and limits

The complete Plugin Check 2.1.0 scan taken during this review reported 203
errors and 1,469 warnings in the existing codebase. Many are static rule
findings about indirect prepared SQL, exception text, translator comments,
or global naming. They are not all proven vulnerabilities, and they have
not all been individually dismissed or repaired. The full scan is **not
clean**, and the numerical review score does not replace manual triage.

The modified review query prepares both date values; the appointment grouping
expression is internal. Job exception text is sanitized before storage and
escaped when Operations renders it. Narrow annotations document these verified
data flows rather than changing their runtime behavior.

Activation with Elementor is not a full visual editor interaction test.
LiteSpeed's plugin loaded, but the PHP development server did not provide the
LiteSpeed cache engine, so server caching/delayed-script behavior is unverified.
External OAuth, payments, Square/Vagaro, mail/SMS delivery, complete booking and
refund flows, browser installation, all themes/builders, and PHP 7.4 runtime
compatibility were not re-certified by this patch. Additional manual acceptance
tests should be run on the intended host with its own sandbox providers.

Large settings/migration files remain a maintenance concern, not a confirmed
functional defect. Splitting them needs broader migration and admin-flow
coverage than this focused regression runner provides.
