# Famado Care QA Report

## Scope

Validation was performed against the generated theme and repeated against a clean extraction of the final installable ZIP.

## Automated validation

- PHP syntax: every theme PHP file passed `php -l` under PHP 8.4.
- JavaScript syntax: theme-authored and packaged JavaScript passed `node --check` where Node.js was available.
- JSON: `theme.json` and every demo JSON manifest parsed successfully.
- Theme structure: exactly one archive root (`famado/`) with `style.css`, `index.php`, `functions.php`, and required templates.
- Archive safety: no absolute/traversal paths, links, devices, duplicate paths, case-colliding paths, encrypted members, nested archives, or out-of-root files.
- Gutenberg content: 23 non-empty source-page blueprints, 3,724 custom block occurrences, balanced block delimiters, valid block-attribute JSON, no `core/html`, and no unresolved or unknown import-token keys.
- Source coverage: all 23 supplied HTML pages are mapped to imported Pages or record detail content; every non-HTML source asset is retained.
- Asset references: packaged local CSS references resolve; expected external/data/fragment references are excluded from local-path checks.
- WordPress contract: four editable menu locations, top-level Import menu named exactly `Import`, registered REST-enabled content types/taxonomy/meta, nonce/capability-protected importer and form handlers, and direct-access guards on PHP files.
- Package integrity: final ZIP CRC test and SHA-256 verification passed.

## Browser QA

Representative source templates were rendered at 320, 360, 375, 390, 414, 480, 768, 1024, 1280, 1440, and 1920 pixels. The 121 viewport checks covered all three home/header variants, service listing/detail, classic blog/article, contact, FAQ, team, and error layouts.

Observed results:

- Horizontal-overflow failures: 0.
- Broken visible images: 0.
- Console errors: 0.
- Missing main landmarks: 0.
- Pages without one primary H1 in the tested source render: 0.
- Responsive menu interaction failures: 0 of 11 representative templates.

The theme screenshot was rendered from the retained source design at 1200 × 900 and visually inspected.

## Environment boundary

A complete disposable WordPress runtime was not available in the execution environment, so activation, database-backed import execution, outgoing mail delivery, and live Gutenberg editor validation were not claimed as runtime-tested. Those paths were instead checked statically, PHP-linted, validated through their bundled manifests, and covered by the external fail-closed archive installer. The final installation should still be smoke-tested on the target WordPress host before production publication.