# MapleJockey v0.4 validation

17 November 2026. Private, local preview.

## Result

151 functional and event/rendering-harness checks passed with no failures. Catalogue structure, generated font embedding and 27 specified text/background contrast pairs also passed. The retained disk rehearsal was independently rechecked: all eight source hashes still match and the run-owned restored candidate is absent after rollback.

Real-browser layout, keyboard, mobile, native file selection and download checks remain blocked. No provider migration has been executed. This release is ready for local review, not represented as fully browser-validated or approved for production cutover.

## Interface changes

- Lato headings and Noto Sans body text, following the typeface pairing in [Canada.ca typography guidance](https://design.canada.ca/styles/typography.html), reviewed 17 November 2026. Fonts and their licence notices are embedded into each standalone HTML file. No font CDN is used.
- Compact directory, guide, pilot and assessment headings. Promotional hero copy is removed. Necessary evidence limitations remain available in records, disclosures and the method page.
- Initial/monogram markers removed from tool cards. The upper-right label gives the category, including Password manager for 1Password and Agency reporting for AgencyAnalytics.
- Higher-contrast grey text, restrained borders and reduced decorative spacing. Directory secondary text measures 7.037:1 on the page and 7.487:1 on white cards using opaque sRGB colour calculations.
- Canadian English and independent MapleJockey branding retained. The font choice does not imply government affiliation or full Canada.ca design-system conformance.

## Verified scope

| Check | Passed | Evidence |
|---|---:|---|
| File-pilot core and adversarial cases | 35 | core-and-negative.txt |
| Assessment core | 10 | assessment-core.txt |
| Independent assessment checks | 17 | assessment-independent.txt |
| Internal reporting application | 12 | model test log |
| Pilot event/rendering harness | 18 | pilot-ui.txt |
| Directory event/rendering harness | 59 | directory-ui.txt |
| Total functional/harness checks | 151 | non_browser_checks.json |

The harnesses use the real application logic with DOM stubs. They verify rendering output and handler behaviour, including negative inputs and state invalidation, without proving native browser interaction.

Additional checks are deliberately separate from the total:

- Catalogue: 45 entries, 270 complete claims, all six dimensions present, unique claim IDs, resolved source references and five structurally complete migration guides. These checks verify structure, not supplier truth or current plan eligibility.
- Contrast: 27 specified opaque pairs pass 4.5:1. `contrast-results.json` lists each pair. This is not a rendered accessibility audit; focus visibility, zoom, opacity and unlisted combinations remain outside the result.
- Generated output: all three HTML files contain the actual three webfont faces, copyright/licence notices, Canadian locale, no unfilled build markers and a policy denying application network connections. Font data URLs are explicitly allowed. See `build-checks.json`.
- Disk evidence: independent SHA-256 confirms eight retained source files. Cleanup state is observed, while the historical sequence and timings remain those in `pilot/results/disk-rehearsal.json`. No historical evidence was rewritten as a new migration.
- Packaging: every archive member is checked against `SHA256SUMS.json` after ZIP creation. Hashes detect accidental differences, not publisher authenticity.

## Remaining validation gates

| Gate | Status and next evidence |
|---|---|
| Desktop and mobile layout, zoom, keyboard and focus | Blocked here. Installed Chromium fails to create its process socket. The separate cloud-browser tool rejects local file URLs by policy. No bypass was attempted. Test the extracted HTML files in a permitted desktop browser at 1440, 768 and 390 px, with keyboard-only navigation and 200% zoom. |
| Native import/export and printing | Unverified in a browser. Exercise synthetic export, file re-import, report download, print and malformed-input rejection using a permitted local browser. Handler checks already pass. |
| Live supplier migration | Not tested. Requires the exact source/destination accounts, scoped authorisation, non-sensitive subset, role matrix, accepted losses and rollback boundary. |
| Binary/SVG application behaviour | Not tested. Byte equality is verified; application compatibility requires the actual consuming software. |
| Provider controls and business acceptance | Unknown or not signed off. Resolve evidence for the actual tenancy and contract. Automated passes do not fill operator or owner signatures. |

## Reproduce from the package

Using an existing Node installation:

```sh
node --test pilot/tests/*.test.mjs pilot/review/negative.test.mjs
node pilot/ui/smoke-test.mjs
node expansion/ui/smoke-test.mjs
node pilot/review/inspect_disk_evidence.mjs
node review/review_core.mjs
node pilot/ui/build.mjs
node expansion/ui/build.mjs
```

From `maplejockey`, run `node --test tests/*.test.js` and `node build.mjs`. With existing Python, run `python3 expansion/checks/validate_data.py` and `python3 validation_v04/check_contrast.py` from the package root. Bundled font CSS is used directly by the application builds; optional font regeneration is documented in `assets/README.md`.

Catalogue supplier evidence and the Internal reporting application retain their recorded dates and scopes. No source/destination vendor account, production service or public deployment was changed.
