[sanchuanhehe]

WS53 combines its control-core and application images, so the existing WS63 image addresses and packaging defaults cannot safely describe an application-only update. This adds experimental WS53 LoaderBoot inspection and a preserved-sector application planner for the verified 4 MiB layout (application entry 0x45d300).

The planner checks partition bounds and overlaps, plaintext/uncompressed metadata, and the existing body hash. It emits changed complete sectors with original recovery bytes, placing the combined-header update last and preserving control firmware, calibration/NV, and unrelated regions. It does not access hardware, validate signatures, or change security policy; callers must independently establish that signature verification is disabled and qualify the Flash-linked application.

Validation:

• 24 library tests, 2 vendor-parity tests, and 1 doctest passed; formatting and all-target/all-feature Clippy passed.
• On the qualified WS53 A board, hisiflash applied a generated three-sector Rust application plan, verified the entire Flash by readback, and observed serial-reset and physical-reset startup. DSLogic measured 32 GPIO transitions at 10 ms intervals and matched the same ELF's QEMU scenario.
• Actual power-cycle cold boot and restoration after this application update remain unverified; this is a draft, not general WS53 qualification.

Tests use synthetic data. No private Flash backups or vendor firmware blobs are included. Existing WS63/BS2X defaults are unchanged.