@@ -572,6 +572,34 @@ start in that case. Inspection MUST neither rerun mounting nor modify media.
572572Fresh source-bound performance/resource and physical qualification gates
573573apply to all five changed images; the observer does not waive those gates.
574574
575+ ** Native-USB acquisition-tool output amendment (2026-09-06).** The maintained
576+ host acquisition tool MUST preserve the same single device-generated
577+ ` PYBLE_WORKSPACE_OBSERVATION: ` JSON line when inspecting native-USB refusal
578+ recovery. With deasserted DTR, the pinned native CDC output path may overwrite
579+ pending bytes; a successful short UID response does not prove a longer
580+ unpaced observation print will be complete. For the exact Waveshare and Pico
581+ profiles, generate the observation once, serialize once, require an ASCII
582+ line of at most 1,024 bytes, and emit it through ` sys.stdout.write ` in chunks
583+ of at most 16 characters with a 50 ms delay after each chunk. A 100 ms drain
584+ interval precedes and follows output. No extra framing, per-chunk newlines,
585+ hex encoding, host-created observation fields, or repair of missing bytes is
586+ allowed. The leading and trailing newline and all JSON bytes are unchanged.
587+ The maximum deliberately requested pacing is 3,400 ms; the existing absolute
588+ 12-second stdout read deadline, transcript bound, exact raw-REPL delimiters,
589+ empty-stderr requirement, and outer acquisition deadline remain fail-closed.
590+
591+ This is transient host-test-tool generated inspection code, not firmware image
592+ code or an app workflow change. DTR and RTS remain deasserted, raw-REPL entry
593+ must not soft-reset the VM, the exact physical UID must be checked first, and
594+ the sealed boot getter is called only once for the fresh challenge. All
595+ candidate/source, nonce, actual media readback, advertisement, and publication
596+ gates remain unchanged. The original raw bytes, including failed captures,
597+ must be retained. Other observation transports retain their existing behavior.
598+ An adversarial overwritable-FIFO host test must demonstrate the old long-print
599+ loss and exact paced output under an explicit bounded drain model. A stdout
600+ write return is not delivery proof. Host tests do not establish USB scheduling
601+ guarantees or replace final-candidate HIL.
602+
575603The complete-device erased scan accepts a read status only when it is ` None ` ,
576604boolean ` True ` , or exact integer zero, matching successful native block-read
577605outcomes. Boolean ` False ` is a failed read, not integer-zero success. Floating
0 commit comments