Publish the verified SFV6 binary with the restored scene, DDE sharpness, and shutter indicators.
Constraint: keep the factory branch as a single root-level lvgl_demo file.
Rejected: pushing the source tree to the delivery branch; factory consumes the binary artifact.
Confidence: high
Scope-risk: narrow
Directive: preserve this modified build until the next explicitly requested reference release.
Tested: source commit 14cd2e0; clean AArch64 build and SFV6 regression checks; size 20084248 bytes; SHA256 261d853e3dbcdced547ff416c3ce74256259944ff419e4f59420d56f9ba00eaf.
Not-tested: physical device interaction.
Delivers the freshly built SFV6 LVGL demo for device-side key upgrade testing.\n\nConstraint: Factory branch must remain a single root-level lvgl_demo binary\nRejected: Source-tree handoff | The factory SFV6 branch consumes the binary directly\nConfidence: high\nScope-risk: narrow\nDirective: Keep this branch binary-only and retain the tested UI version in release commits\nTested: SFV6 regression scripts, Python compile checks, git diff --check, clean AArch64 make all\nNot-tested: Physical device key upgrade and slot switch\nUI-Version: U1.0.13\nSource-Branch: paseo-sfv6-workspace\nPush-Time: 2026-07-31 06:01:24 UTC\nBinary-SHA256: 5fd6f985fb91b768ccbac76e608da7f85cd3db86ee0fddcfe9d0f4ed73868c67
Constraint: factory delivery branch must contain only lvgl_demo
Rejected: pushing the source tree to the factory binary branch
Confidence: high
Scope-risk: narrow
Directive: preserve normal fast-forward release history for sequential device testing
Tested: local clean AArch64 build; upgrade archive regression and full checks; local SHA256
Not-tested: device checkslot payload installation and reboot
Source-Branch: paseo-sfv6-workspace
Source-Commit: 836945e8134688dd8164473bd982f6a3f904417f
Push-Time: 2026-07-28 16:23:27 +0800
Binary-SHA256: 8da43fbed302b94832474f6672697a172af02f51ce03376c632a142b24d8a2b3
Constraint: Factory branch must contain exactly one root-level lvgl_demo.
Rejected: Rewrite branch history | Preserve modified and original builds as sequential recoverable commits.
Confidence: high
Scope-risk: narrow
Directive: Publish any later original build as a new SFV6 commit; do not overwrite or force-push.
Tested: Clean AArch64 build; all SV6 and SFV6 regression scripts; ELF and SHA256 verification.
Not-tested: Physical SFV6 device behavior.
chnjinlei