Implementation and validation plan

This page preserves the documentation path referenced by the original README and describes the current maintenance sequence. It does not assert that historical work was executed or that pending release checks have passed.

Maintain behavior and evidence

1. Inspect the relevant implementation, callers, configuration and tests; reproduce a reported failure with synthetic data.
2. Make a focused change preserving ordinary files, unsaved edits, encoding/line endings, unrelated resources and existing attribution.
3. Run meaningful affected regression checks, then the reproducible automated gate. Retain original external/native acceptance tests; report their prerequisites and exclusions.
4. Review documentation, exact-case links and screenshots against actual UI and source contracts. Keep current limits and network boundaries explicit.

Prepare a release

1. Use the pinned SDK, locked dependencies and default vulnerability auditing.
2. Complete the build and automated gate for the exact source commit; inspect counts, skips and exclusions.
3. Build into fresh release directories, verify the complete ZIP/checksum and inspect extracted-application smoke evidence.
4. Perform and record applicable native/clean-machine checks from the ledger. Unperformed checks remain open.
5. Publish only complete assets with accurate unsigned/preview limitations and source identity. Change the application version only when explicitly authorized.

The review matrix, validation guide and release guide provide the current scope. Successful publication is not a substitute for native acceptance or trusted signing.