@@ -141,12 +141,13 @@ instructions.
141141
142142Until the first firmware selector passes the complete qualified-release gate in
143143§7, the repository README and home page MUST NOT describe either current profile
144- or its browser image as qualified. The one-time ` v0.4.1 ` public-beta selector MAY
145- make the exact ` esp32-4mb ` and ` esp32-s3-n16r8 ` images available under the
146- exception in §7, but every active installer state MUST visibly say ** unqualified
147- beta** , ** HIL pending** , and ** use at your own risk** before profile selection and
148- again beside the install action. It MUST NOT say or imply that the beta is
149- access-controlled. The home-page target cards MUST identify the constraints as
144+ or its browser image as qualified. The exact audited ` v0.4.2 ` public-beta
145+ selector MAY make the ` esp32-4mb ` and ` esp32-s3-n16r8 ` images available under
146+ the exception in §7, but every active installer state MUST visibly say
147+ ** unqualified beta** , ** HIL pending** , and ** use at your own risk** before
148+ profile selection and again beside the install action. It MUST NOT say or imply
149+ that the beta is access-controlled. The home-page target cards MUST identify
150+ the constraints as
150151` esp32-4mb ` (classic ESP32, 4 MiB external SPI flash, no PSRAM assumed) and
151152` esp32-s3-n16r8 ` (ESP32-S3, 16 MiB flash, 8 MiB ** Octal** PSRAM), and give each
152153the truthful public-beta/pending-HIL state while that selector is active.
@@ -156,14 +157,18 @@ recovery commands.
156157
157158The repository README, home-page hero, provisioning workflow, exact-profile
158159cards, TestFlight callout, support getting-started guide, and public roadmap
159- MUST agree with that current state. Each current-profile status MUST name
160- ` v0.4.1 ` , ** unqualified beta** , and ** HIL pending** ; installation instructions
161- MUST direct users to the enabled ` /flash ` action while preserving the exact
162- profile, backup, erase, cable/power, and port acknowledgements. The home and
163- support surfaces MUST include ** use at your own risk** . The roadmap MAY shorten
164- the warning, but MUST put complete HIL qualification for the same two exact
165- profiles in near-term work rather than claim they are qualified now. Every one
166- of those surfaces MUST keep C3 explicitly unavailable.
160+ MUST agree with the build-selected installer state. While the exact beta
161+ selector is active, each current-profile status MUST name ` v0.4.2 ` ,
162+ ** unqualified beta** , and ** HIL pending** ; installation instructions MUST direct
163+ users to the enabled ` /flash ` action while preserving the exact profile, backup,
164+ erase, cable/power, and port acknowledgements. The home and support surfaces
165+ MUST include ** use at your own risk** . When no selector is active, including an
166+ explicit installer-disable deployment, the generated home and support pages
167+ MUST instead say that the installer is unavailable and MUST NOT claim that the
168+ beta is available. The roadmap MAY shorten the warning, but MUST put complete
169+ HIL qualification for the same two exact profiles in near-term work rather than
170+ claim they are qualified now. Every one of those surfaces MUST keep C3
171+ explicitly unavailable.
167172
168173README getting-started instructions MUST gate destructive flashing on ` /flash `
169174showing an active version, exact profile, and enabled install action. While the
@@ -173,7 +178,7 @@ what is visible; it MUST NOT claim that a physical board is pictured when the
173178capture shows only the app.
174179
175180The wide social card MUST describe the workflow as one-time USB setup followed
176- by everyday use over BLE. If it advertises the enabled ` v0.4.1 ` web flasher, it
181+ by everyday use over BLE. If it advertises the enabled ` v0.4.2 ` web flasher, it
177182MUST visibly call it an unqualified beta with HIL pending. Its mechanically
178183rendered PNG and authored SVG MUST remain paired by reviewed content and
179184exact-dimension tests.
@@ -320,23 +325,30 @@ VPS origin. The origin MUST:
320325 firmware 4xx/5xx with ` Cache-Control: no-store ` , and use the selected
321326 ` release.json ` SHA-256 as the deterministic cache key for both verification
322327 and ESP Web Tools retrieval;
323- - serve ` /firmware/v0.4.1 / ` only while the exact attested public-beta selector
328+ - serve ` /firmware/v0.4.2 / ` only while the exact audited public-beta selector
324329 defined in §7 is active; its successful immutable responses use the ordinary
325330 versioned-firmware cache policy, while every missing/error response remains
326331 ` no-store ` ;
327332- use a valid origin certificate with Cloudflare ** Full (strict)** TLS, never
328333 Flexible mode; and
329334- expose only the required web and key-authenticated administration ports.
330335
331- After the first qualified public installer is activated, an ordinary
332- website-only deployment MUST preserve that exact immutable selected release.
336+ After a public installer is activated, an ordinary website-only deployment MUST
337+ preserve that exact immutable selected release.
333338The deployment obtains the selector and firmware tree from the current managed
334339release over the authenticated deployment transport, validates them through
335340the preserved-public staged-release and checksum gates, and embeds the selector
336341at build time. That carry-forward gate repeats the self-contained bundle,
337- schema, HIL, profile, artifact, path, size, digest, descriptor, and annotated-tag
338- checks. It does not repeat the source/build license audit because the exact
339- immutable bytes already passed that audit during their original activation.
342+ schema, HIL, profile, artifact, path, size, digest, descriptor, and
343+ annotated-tag checks. A preserved qualified release does not repeat the
344+ source/build license audit because the exact immutable bytes already passed that
345+ audit during its original activation. The exact ` v0.4.2 ` public beta is a fresh
346+ pending candidate and MUST instead repeat canonical ` --audited-candidate `
347+ validation with its retained license-evidence directory and exact build root on
348+ every deployment that carries it forward. That validation MUST receive the
349+ exact firmware-source checkout recorded by the release, rather than substituting
350+ the later website checkout. A preserved qualified release MUST NOT require
351+ those retained beta source/build/evidence inputs.
340352It MUST NOT infer availability from the mere presence of a firmware directory
341353or accept a caller-supplied selector.
342354
@@ -379,28 +391,34 @@ selector, release metadata, public firmware paths, or recovery commands.
379391ESP Web Tools' family detection is necessary but not sufficient to establish
380392memory-profile or silicon-revision compatibility.
381393
382- One narrow pre-qualification exception exists for the already manually tested
383- ` v0.4.1 ` bytes . A build-time selector MAY use deployment mode ` public-beta ` only
394+ One narrow pre-qualification exception exists for the fresh audited ` v0.4.2 `
395+ candidate . A build-time selector MAY use deployment mode ` public-beta ` only
384396when all of these facts are true:
385397
386- - ` version ` is exactly ` 0.4.1 ` , ` releaseJson.sha256 ` is exactly
387- ` 8b84fbb65a0463d20369e1d86dac566ca7a2039ebc30f9186f55c05421962445 ` ,
398+ - ` version ` is exactly ` 0.4.2 ` , ` releaseJson.sha256 ` is exactly
399+ ` 5d1b0db8c4b90cccf054cd244530afb3b9112d489aa02f7c5da650e92161acde ` ,
388400 ` hilStatus ` is ` pending ` , and ` accessControlled ` is ` false ` ;
389401- the selector contains exactly ` esp32-4mb ` and ` esp32-s3-n16r8 ` with the
390402 frozen paths, offsets, memory requirements, and silicon windows; C3 is absent;
391403- the same-origin ` release.json ` , schema, manifests, firmware, documents, and
392404 ` SHA256SUMS ` pass the existing path, shape, size, and SHA-256 integrity checks;
393- and
405+ - the canonical release tool accepts the exact bundle with
406+ ` validate --audited-candidate ` , the retained license-evidence directory, and
407+ the exact release-build root, using the exact firmware-source checkout
408+ recorded by the release as ` --repo-root ` ; the annotated ` firmware-v0.4.2 ` tag
409+ exists and peels directly to ` release.json ` provenance; and
394410- ` /flash ` visibly labels the firmware an ** unqualified beta** , says full HIL is
395411 pending and installation is at the user's risk, and never calls it protected,
396412 access-controlled, qualified, validated, or generally available.
397413
398- This exception attests only the identity and integrity of the retained bytes;
399- it does not manufacture HIL evidence. It MUST NOT accept another version or
414+ This exception attests the identity, integrity, provenance, and audited-candidate
415+ license state of the exact bytes; it does not manufacture HIL evidence. It MUST
416+ NOT accept another version or
400417digest, broaden either profile, enable C3, or satisfy any qualified-release
401418gate. Removing or replacing the beta requires an explicit deployment action and
402419production smoke verification. A later website-only deployment MAY carry the
403- same exact beta selector and byte tree forward through the same integrity gate.
420+ same exact beta selector and byte tree forward only by repeating the same
421+ audited-candidate, license-evidence, annotated-tag, and integrity gates.
404422
405423Except for that exact transitional beta, the ` /flash ` action MUST fail closed
406424and remain explicitly unavailable until all of the following are true for one
0 commit comments