Validation
The release was checked on 28 October 2026 with an isolated, newly authored Sample Hardware company. The source pins and extraction boundaries are in provenance.
Runtime and source
A fresh Python 3.12 virtual environment installed the locked CPU dependencies; pip check passed. The actual Node 22.21.1 executable was checksum-verified. The two original services started from a fresh owned directory, generated their SQLite databases, rendered the original widget and communicated through their authenticated company-scoped HTTP bridge.
The final proof runs the source files verified against the release candidate. It uses six authored catalogue articles, two initial requests and generated hardware images. The launcher clears inherited provider configuration and installs a Python socket boundary that permits loopback. Browser requests are independently restricted to loopback. The retained pure JavaScript pricing engine runs locally.
Tests
- 300 manufacturer, recipient and mount checks cover company scope, capabilities, roles, files, correspondence, immutable snapshots, renderer pinning, publication, restore, staff command retry and private credential/origin handling.
- 402 Orders checks and 11 subtests cover the retained generic producer, stores, pricing, specifications, contracts and native request flows. Eleven optional acceptance checks are skipped in the CPU environment.
- Python source parses, native JavaScript syntax, the agent skill format and local guide/source links pass their gates.
Client catalogue, client research fixtures and owner-bound operations scripts are identified in provenance/omitted-client-material.json. Their original source remains with its owner. Generic engine tests and required shared SDK dependencies are included.
Browser and persisted workflows
The actual Orders, Customers, Products and Configurator screens were checked at 1600, 390 and 320 pixels. All twelve views rendered without JavaScript errors, failed requests, external requests, broken images or horizontal page overflow. The public configurator also rendered its three authored product illustrations.
The running source saved a lever price of €26, published it to the public catalogue, then restored the original immutable version and its €24 price. Previously saved order snapshots retained their exact values. A staff command submitted twice created one order. The original text specification remained attached to that order.
To repeat the browser check after starting a fresh sample:
.venv/bin/pip install playwright
.venv/bin/python -m playwright install chromium
.venv/bin/python tools/check_browser.py \
--code-file .local/first-result/owner-code.txt
The check consumes a local one-use code. Its screenshots and report stay in .local/browser-proof/; it writes no session-cookie export.
Preview and integration boundary
The hosted native mode runs these same services and databases. A real browse membership opens automatically and supplies read-only actor capabilities. The application serves actual API reads, the original quote calculator, native assets and saved renderer under the configured base path. Main-window fetch remains native. Server guards hold writes and observer/session escalation; the scoped native cookie is HttpOnly and SameSite Strict, with Secure on the configured HTTPS origin. The owner mode remains editable.
The mounted real backend was checked across Orders, Customers, Products, Team chat and Configurator at 1600 and 390 pixels, plus order-detail navigation: zero console/page errors, failed assets, broken images or external requests. The quote handler returns €48 gross for two €24 lever sets; the authoritative order count remains two. Twenty-one mount contracts cover URL normalization, canonical JSON writes, font CORS, cookie scope, streaming and read-only enforcement. Deployment records the single-server contract.
Recipient-hosted OpenAI, managed authentication, funding, SMTP, Chatwoot, catalogue scraping and production deployment need their own provider configuration and acceptance. Their source and admission mechanisms are retained; the release proof covers local CPU workflows. The optional PostgreSQL journal is included as source and migrations; this result exercises SQLite.
The secret scan has one known finding in the byte-pinned upstream Mermaid bundle. Its exact rule, path, line and file hash are recorded in provenance/secret-scan-disposition.json; all other findings require review. The source archive excludes private state, cookies, credentials, databases, uploads and dependency environments.