# Final Release Notes — v13

## Release status

v13 is a release-candidate handoff build. Feature/module development from the supplied GDP portal documentation is broadly complete at MVC/source level. The next required activity is not more feature coding; it is staging validation in a PHP/MySQL environment.

## Major completed areas

- Company & Sites
- Customers / Suppliers / Qualifications / Reopening
- Product Master and Batch / Stock traceability
- Orders, Dispatch, Purchase Requests, Goods Receiving
- GDP QMS: Deviations, CAPA, Change Control, SOPs, Document Control, Forms & Templates, Risk, Complaints
- Inspection strength: Recalls, Falsified Medicines, Defective Stock, Audits, GDP Gap Analysis, MHRA Inspection History
- People & Training: Training Matrix, SOP Read & Sign, Training Records
- Premises & Equipment: Asset Register, Fridges/Loggers, Calibration, Contractors, Premises Checks, Cleaning, Pest Control, Fire & Safety
- Accounts & Tax: Dashboard, Payment Tracker, VAT, Credit Notes, Accountant Export Pack, Accounting Integration Stubs
- Advanced tools: AI Report Writer, QR-style labels, Cold-chain Import, System Health
- Handoff docs and scripts: release checklist, route coverage, preflight, SQL audit, staging test templates, cPanel guide, go-live runbook, security guide, backup/restore scripts

## Critical validation requirement

This package was assembled in a sandbox without PHP CLI/MySQL CLI. Static checks pass, but production use requires a staging run:

```bash
cd mvc
./scripts/static_preflight.sh
./scripts/php_lint_all.sh
DB_NAME=aarjay_gdp_regression MYSQL_USER=root ./scripts/test_install_sql.sh
BASE_URL=https://your-staging-url.example ./scripts/regression_smoke_test.sh
```

Then open `/system-health` as admin.

## Handoff decision

Do not deploy directly to production without:

1. `install.sql` import success
2. PHP syntax lint success
3. Smoke route test success
4. Manual create/edit/view workflow test success
5. Admin password change
6. Permissions matrix review
7. Backup and rollback plan

## Next after v13

If staging regression passes: deploy to production.

If staging regression fails: fix runtime issues only, then package a patch release.
