Matching development SDK and acceptance
The website development SDK comes from one committed core and includes ESM,Worker,WASM,TypeScript,script runner and contract. Native attachments provide C ABI1 headers/examples and AndroidJava/JNI sources. QuickJS is embedded in the map library when built with the script feature; the desktop application is not required.
The repository tool tools/sdk-bundle/build.py packages verified Linux x86_64 and AndroidARM64 libraries,web SDK,source attachments and licenses into a new external directory,with SHA-256 inventories. It checks build inputs,actual C exports,ABI/runtime flags and Android linking evidence, rejecting mixed versions or overwriting old bundles. Build products stay outside Git.
Linux has actual dynamic-library/script and software-GPU acceptance. Browser main-thread and strict Worker runs share scripts and display evidence. AndroidAPI24+ has ARM64/JNI compilation and LinuxJVM host evidence; phoneGPU/system acceptance remains pending. Windows/macOS are validated externally; iOS and the mobileGIS application are not connected.
Local development bundles and production website builds do not imply formal npm/native publication or online deployment. Version inventories retain those distinctions. See matching webSDK,nativeAPI,Androidhost and compatibility.
Current effective-metadata development delivery: core8fc51305dd67f3b0a18381ccb90ba73b8a6337f7, SDK 0.3.0-dev.8fc51305. The same58 checks and13 observed phases passed in Native, main-thread and Worker hosts atDPR1/2, totaling78 real frames. Actual20-resource sequences match; all four browser hosts use137 calls, with zero final cancellations/unexpected errors under recursive Worker instrumentation and three explicitly verified expected source failures. Integrated CPU/actual software Vulkan, workspace/seven-crate wasm boundaries and affected metadata/refresh/URL/DEM regressions passed; eight pinned official-loader observations retain their source SHA. Application102/data49 cases, locked check and matching Native/core/application WASM and Android API24 ARM64/JNI are complete; the233-entry script-contract WASM retains its bytes. Archive SqsMap-SDK-0.3.0-dev.8fc51305-metadata-resolution.tar.gz has649 manifest files plus bundle.json,38292708 bytes,SHA256 1ba4205f34aee57579b288a4c14763ded44bc8c55658d98101de364b55aaa24b; the independent read-only verifier checked every member. Fixed74/MVT/DEM/template archives retain their SHA. Bilingual HTTP and four-repository synchronization are recorded separately. MLT/other full metadata, device/external validation,mobile GIS/iOS and formal release remain pending.
Current tile-template development delivery: core16498121bf45c5253114b36ff7d3e65da899a195, SDK 0.3.0-dev.16498121. The same130 checks and9 observed phases passed in Native, main-thread and Worker hosts atDPR1/2, totaling54 real frames. Three source types share39 actual resource calls; all four browser combinations use111 calls with zero errors. Official30-input/90-world-copy comparisons, common-source/independent-URL CPU cases, actual software Vulkan, workspace/seven-crate wasm boundaries, four metadata cases and the DEM regression passed. Application102/data49 cases, locked check, matching Native/core/application WASM and Android API24 ARM64/JNI are complete. The233-entry script-contract WASM retains its bytes. Archive SqsMap-SDK-0.3.0-dev.16498121-tile-url-templates.tar.gz contains642 manifest files plus bundle.json,38267917 bytes,SHA256 178588aaf79866bd387cd9dbef978c0d45015b69bc6f3e38f247c763144d8332; the independent read-only verifier checked every member. Fixed74/MVT/DEM archives remain byte-identical. Bilingual production HTTP and four-repository synchronization are recorded separately. Full source parameters/MLT, devices/external validation, mobile GIS/iOS and formal release remain pending.
Current source-coverage development delivery:
Matching core 570706f9336c919b76cf4c2cac1a316e13f5de44, development SDK 0.3.0-dev.570706f9. The same 84-check/eight-phase input passed Native, main thread and Worker, with 24 actual observed frames. Both browser hosts used 181 calls; protocol traces match Native and browser errors are empty. New coverage CPU, existing parent/raster CPU and one integrated software-Vulkan case passed, together with 102 application tests, 49 data tests and the locked check. Native, core/application WASM and Android API24 ARM64/JNI match. The 233-entry script contract is unchanged; its existing WASM retains the original SHA.
Development archive SqsMap-SDK-0.3.0-dev.570706f9-vector-coverage.tar.gz contains 624 inventory files plus bundle.json, 38243826 bytes, SHA256 5c82c0fb34c3ba8e473b55128096ca4194844061bc1bc34da07862484aa32a7c. The standalone read-only verifier checked every member, exact Native/Android libraries, shared script/HTML/five PBFs and WASM. The fixed stage74 archive and SHA remain unchanged. Production website HTTP and four-repository Git are recorded separately. Android is build/link verified; external/device acceptance, full capabilities and formal release remain incomplete.
Fixed stage74 core 5576072e946eb146bb77f923fa3d5adbee3b84aa, development SDK 0.3.0-dev.5576072e. Shared label placement history and collision fades passed local public acceptance: the same 84-check/13-phase script passed Native, main-thread, and Worker at DPR1/2, with 845 actual observed frames. Coverage includes target queries, required/optional groups, real linear timing, reversal, full style replacement, and original identity/anchor continuity across MVT parent/child handoff with a nonzero 2400ms fade window. The raw C ABI passed 16 steps. Complete HTML passed four real buttons, four phases/30 frames, an original ID74 click, and 200ms stable-idle checks. The integrated CPU and final software-Vulkan case passed, together with relevant APP/native/script typing, dependency, generated-contract, and WASM checks.
Archive SqsMap-SDK-0.3.0-dev.5576072e-fixed74.tar.gz: 624 inventory files plus bundle.json, 38224421 bytes, SHA256 b74d766d98aa3f881efdd925efedc32ff27aa8707fed94a6225529c3dadabf2c. The tar was independently reopened to verify every size/SHA and exact Native/Android libraries, examples, and declarations. Linux Native, core/application/script WASM, and Android API24 ARM64/JNI match this core. Android is build/link verified, not device accepted. The 19 bilingual production-preview HTTP checks and four-repository Git synchronization are complete. Full style/vector/DEM, mobile GIS/iOS, phone/hardware GPU, external Windows/macOS acceptance, formal publication, and deployment remain incomplete.
Current DEM development delivery: core0762741e6c8e5f5b6b00ba140a999ed0b51fa54a, SDK 0.3.0-dev.0762741e. The same29 checks and10 observed phases passed in Native, main-thread and Worker hosts, totaling30 real frames. Each browser host uses103 calls, with identical protocol sequences and no browser errors. Integrated CPU/actual software Vulkan, affected regressions, workspace all-targets and seven-crate wasm boundaries passed; application102/data49 cases, locked check, matching core/application WASM and Android API24 ARM64/JNI are complete. The233-entry script contract is unchanged and its compiled bytes retain their SHA. New archive SqsMap-SDK-0.3.0-dev.0762741e-dem-coverage.tar.gz contains633 manifest files plus bundle.json,38253092 bytes, SHA256 3c85d3a504557743d55f3c562cf21117babb6b265002d2c3487f82b1f985bbf4. The independent read-only verifier checked every member; fixed74 and MVT archives remain byte-identical. Bilingual production HTTP and four-repository synchronization are recorded separately. External/device validation, mobile GIS/iOS, full capabilities and formal release remain pending.
Standalone archive verification
Download the Python verifier and run it with Python 3.10 or later. It requires neither third-party packages nor this application. It compares every inventory entry, file length and SHA256 without extracting or executing SDK contents. Use the archive SHA256 provided separately by the publisher to check your download:
python verify-sdk.py SqsMap-SDK-0.3.0-dev.8fc51305-metadata-resolution.tar.gz --sha256 1ba4205f34aee57579b288a4c14763ded44bc8c55658d98101de364b55aaa24b
Exit code 0 means success and 1 means failure; both return a JSON result. Omitting --sha256 checks internal archive consistency only. Platform fields report the bundle's recorded status and do not rerun device acceptance. Inventories and hashes do not replace release signatures. Adding this separate verifier does not change the fixed archive.
2026-10-15 bounded acceptance of existing products
Fixed SDK 0.3.0-dev.8fc51305 and application implementation ca7491fb passed a bounded recheck: 649 archive files, 58 Linux Native checks/13 frames, 87 public script-page checks across main-thread and Worker hosts, nine local-DEM application/engine Worker frames, and 14 bilingual page/attachment HTTP checks. Actual workbench UI actions covered GeoTIFF opening, surface mode, tilt, globe round-trip and workspace reload. The application WASM SHA256 remains fa226ae8f11b29b1b5cb59594538525201fbe6ad6f11972ead03b5520cd6caaa.
Nothing was compiled or repackaged. Native llvmpipe and browser SwiftShader were explicitly selected; initial device/compositor failures and the driver misclassification of an expected 404 cancellation remain recorded. This is software-backend evidence. Acceptance ran serially with two CPU cores, 8GiB memory and zero swap; the final browser session peaked at about 765MiB, and its services were closed. See repository files docs/engineering/archive/SQS_MAP_API_ACCEPTANCE.md and tools/fixed-version-acceptance/results.json.
Later geometry-edit changes fetched during synchronization (core 6d21152a, application a5beb62a) are outside this fixed-product acceptance. Engine enhancements, mobile GIS/iOS, device/external acceptance, formal release and online deployment remain incomplete; automatic continuation is disabled by the task scope. This editorial update was not rebuilt or deployed; the HTTP evidence covers the pre-existing production preview before this addition.