[sidmohan0]

Prepare the coordinated Core SDK and integration 1.0.0 release with independently versioned FogVault 0.1.0. Dated release notes, exact install instructions and shipped package guides describe the frozen Workspace contract and preserve the separate beta.3 interchange regression, host responsibilities and extension acceptance gates.

The companion publisher defaults to nonpublication and admits only exact-main qualified archives. It validates CI artifact and package hashes, publishes Rust dependencies in order with ordinary Cargo verification, uses the single qualified native Node archive and the three installed Python wheels, and rejects different bytes under an existing version. The FogVault build pin is frozen at f4dc492549b70f0bc44f5c6bf82fe3022353030f; its protected main promotion is required before uploads. Base SDK publishers retain the actual upload archives and SHA-256 receipts; npm publishes those same archives without rebuilding or running lifecycle hooks, so public downloads can be compared to the upload inputs. Python qualification now builds an optimized release wheel, and the base Python publisher no longer skips existing files without review. New npm repository metadata supports the owning project's provenance.

Validation: seven upload-staging tests, 13 publication guard tests, 15 release gate tests, 12 verifier failure tests, legacy failure tests, four wheel metadata tests, three locked native dependency graphs and the Core contract inventory pass. Actual packed npm repository/version/license metadata checks pass. A normal locked Cargo dry run for the staged first dependency fork passed with strict qualified-source and approved-lock comparison. Final PR and exact-main integration/model qualification are pending; previous candidate evidence does not replace those runs. No registry publication is performed by this PR's checks.