Staging Acceptance

Readiness checks, native test runner and production acceptance evidence.

Recorded baseline

On 12 October 2026, the supplied GitHub Actions screenshot for stardetha/stardetha-one run #5, commit bd79809, showed all five jobs successful. That run covered the 0.24.1 baseline: platform tests using SQLite and PostgreSQL, MariaDB 10.11 and MySQL 8.0 including competing-worker tests, and native WordPress fixtures for PHP 8.1/WordPress 6.4 and PHP 8.3/WordPress 6.8. These WordPress versions are compatibility fixtures, not deployment recommendations.

Earlier native test output reported 193 tests/920 assertions for PostgreSQL and 196 tests/933 assertions for each MySQL-family job. The green rerun used PHPUnit directly with --fail-on-skipped and --display-all-issues. The previous Artisan command's nonzero exit despite passed assertions remains unexplained; no tests or skip guards were removed.

Hostinger staging readiness reported zero failures and zero warnings. Registration, verification, reset and login were confirmed by the operator. PayFast sandbox checkout and renewal were exercised. Following the multipart hotfix, the actual resend returned HTTP 200, with the same license expiry and original receipt. Scheduler and backup/restore checks were also exercised. This records the observed staging evidence, not blanket production approval or an exhaustive database audit.

Scope of 0.24.3

This release changes the main plugin version metadata and the One License screen's update guidance. It does not change translation, licensing, metering, storage, updater logic or database schema. Documentation and the docs viewer are synchronized separately. The 0.24.3 package has not yet passed the real-host update test described in staging-update.html.

Remaining real-host acceptance

Back up the WordPress site and database, preserve salts/options, and use the existing sandbox installation. Publish the reviewed 0.24.3 plugin ZIP through the One importer, discover it through WordPress, and install through the normal update control. Confirm active state, site binding, license expiry, language/provider settings and an existing translated page. Confirm the new License screen text. This is separate from fixture-based CI, which intercepts HTTP.

Also exercise withdrawal or failed-download refusal without losing the installed plugin, and rehearse rollback. Any configured payment provider needs its own sandbox acceptance; only PayFast is evidenced in this staging session. Keep live payments disabled until the remaining acceptance and operational decisions are complete.

Never run destructive test suites against the One or WordPress service databases. The native fixtures use dedicated disposable databases and test-only keys.