[JimCollinson]

Summary

• promote the Browser SDK target manifest and all six mapped documentation pages directly from released version 0.1.2 to latest stable release 0.1.4
• pin the exact release commit, npm integrity, package digest, shipped ant-client revision, and WebAssembly digest
• explain the full 0.1.2 to 0.1.4 capability change in human-first language: manifests and share links, private access, large-file retrieval choices, upload recovery, pointers, and media deployment
• update the runnable public-read tutorial to Browser SDK 0.1.4 and patched Vite 8.3.5
• add the dated source, package, capability, runtime, and review evidence record

This is part of the released-truth rollout tracked in #103 and #104. The unpushed 0.1.3 candidate was superseded when 0.1.4 published, so the final range presents one atomic 0.1.2 to 0.1.4 promotion.

Verification

• 107/107 repository tests passed locally and in CI
• 41/41 documentation-guard tests passed
• 35/35 release-following tests passed
• atomic release-baseline validator and exact prose envelope passed
• ADR governance, 90 relative links, 13 external source/release links, and whitespace checks passed
• exact Browser SDK 0.1.4 and Vite 8.3.5 install audited with zero known vulnerabilities
• fresh development and production-preview public reads passed: 138,931 bytes, 782 by 1600 image, expected SHA-256, WebAssembly HTTP 200, no page errors, and restored button
• forced first-WebAssembly HTTP 503 produced the expected initialization error; same-page retry succeeded
• all six GitHub and GitBook checks pass at exact head c8e7bcc1d2bca568d9a0d10eae7f1acbc7122d3a

Review status

• external Claude review: factual memory-budget error corrected; API-like prose rewritten around developer choices; full deployed-baseline capability gap corrected; machine-specific temporary path removed
• final source verification: passed 6/6 targeted criteria for upload recovery, unresolved payments, pointer proof age and finality, manifest-link semantics, and editorial order
• final Craft Review: passed after resolving one ambiguous payment-reconciliation sentence; no findings remain at exact head
• adversarial review: NOT-READY at intermediate head 9e583fc because it was not pushed or CI-tested and because upload/pointer recovery prose omitted safety-critical states. The substantive prose findings were corrected and passed targeted source verification. The exact final head is pushed and CI-green. The milestone adversarial lane was not automatically rerun after remediation, per the review policy.
• clean-context review: blocked before inference because the configured reviewer authentication-status command failed. No model ran. Run ID: eaf1f1bb-268e-4755-b7dc-255d8ef5fb1c. Jim explicitly waived this unavailable lane for PR docs: promote Browser SDK released truth to 0.1.4 #109 and authorized merge on 2026-10-28. The lane remains Not run, never Pass.

Review boundaries

The runtime exercise covers the documented Chromium public-read path and initialization retry. It does not exercise manifests, pointers, wallets, payments, uploads, large-file streaming, media playback, Safari, Firefox, or other operating systems. Those capability descriptions are source-verified against the released package and are not presented as runtime-tested here. Dedicated task guides for those flows remain future documentation work.

Jim authorized merge of exact head c8e7bcc1d2bca568d9a0d10eae7f1acbc7122d3a on 2026-10-28.

[MaidSafe-Hermes]

APPROVED — no material actionable defects found.

Coverage: 2/2 seats reviewed (sol-1 gpt-6.1-sol xhigh; glm-1 z-ai/glm-5.3); both seats agree (two model families).

The six Browser SDK verification blocks and target-manifest.yml consistently identify v0.1.4 and the exact release commit. I checked the changed capability claims against the v0.1.4 README and verified the npm integrity and bundled WASM SHA-256 from the published package. The repository's atomic promotion validator and diff whitespace check pass; all six current PR checks are successful.

Upload/payment recovery, pointer writes, media and large-file streaming are not runtime-tested here, as the sweep record states. That limit is disclosed and is not a defect in this documentation promotion.