Record completed Core 1.0 publication in public guides

CHANGELOG.md

@@ -17,23 +17,6 @@ Earlier release notes are in [docs/releases](docs/releases/).
 - Regenerate Cargo-owned `Cargo.toml.orig` when staging qualified crates for
   publication, so packages with broad include rules pass normal Cargo verification.
 
-- Retain exact base SDK publication archives and SHA-256 receipts before upload;
-  npm publishes those same archives with lifecycle hooks disabled.
-
-- Build and install the optional Python FogVault wheel with the optimized release
-  profile during qualification, so the tested wheel is the publication artifact.
-
-- Python publication rejects existing distribution files instead of silently
-  accepting them on retry. Partial releases require comparing public checksums
-  and selecting only missing, qualified artifacts.
-
-### Changed
-
-- Identify the source repository in optional Core–FogVault npm package metadata
-  so registry provenance resolves to the owning public project.
-- Document exact Core 1.0 and FogVault 0.1 installation paths, supported package
-  targets and the separate publication/extension-acceptance boundaries.
-
 ## [1.0.0] - 2026-10-30
 
 ### Security
@@ -43,7 +26,7 @@ Earlier release notes are in [docs/releases](docs/releases/).
 
 ### Added
 
-- The Core v1 candidate exposes a Rust-backed Workspace contract identifier in
+- Core v1 exposes a Rust-backed Workspace contract identifier in
   every SDK and checks a reviewed API/type/snapshot inventory alongside installed
   parity. Current v3 writes and v1/v2 reads keep their existing semantics.
 - `cargo dfv check --core-sdk` qualifies actual packed SDK contracts and
@@ -53,15 +36,15 @@ Earlier release notes are in [docs/releases](docs/releases/).
   recovery, conversation and restore-stream flows through the shared Rust owner.
   `cargo dfv build --fogvault-languages` and `check --fogvault-languages` verify
   installed npm/wheel candidates and Node–Python shared-vault interoperability.
-  Future v1 publication requires passing joint native/browser and native-language
-  CI evidence for the exact candidate commit.
+  Publication requires passing joint native/browser and native-language
+  CI evidence for the exact release commit.
 
 - An optional import-only browser reader authenticates supported v1/v2 Core
   reference backups and migrates them into fresh FogVault destinations after
   approval. It preserves source archives and uses the existing legacy crypto;
   compatibility with an unidentified shipping extension is not established.
 
-- Optional Core-owned native Rust and browser FogVault integration candidates
+- Optional Core-owned native Rust and browser FogVault integrations
   save exact Workspace bundles before activation, bind complete heads and record
   identity, revoke Core handles on lock, and require fresh review after uncertain
   saves. Authenticated-bundle recovery stages a fresh destination without
@@ -71,12 +54,17 @@ Earlier release notes are in [docs/releases](docs/releases/).
 
 ### Changed
 
-- Native FogVault Node candidates use checked platform binaries and a single
+- Identify the source repository in optional Core–FogVault npm package metadata
+  so registry provenance resolves to the owning public project.
+- Document exact Core 1.0 and FogVault 0.1 installation paths, supported package
+  targets and the separate publication/extension-acceptance boundaries.
+
+- Native FogVault Node packages use checked platform binaries and a single
   assembled archive; Python wheels include their README and MIT license. Core
   release qualification also verifies real Rust registry-style archives.
 
-- Prepare aligned Core SDK and integration package versions for 1.0.0 without
-  publishing. The exact published beta.3 compatibility regression is retained.
+- Release aligned Core SDK and integration package versions as 1.0.0. The exact
+  published beta.3 compatibility regression is retained.
 - Node's public declarations omit private transport functions that were never
   exported by its public runtime; generated declarations and installed type
   tests enforce that boundary.
@@ -97,6 +85,18 @@ Earlier release notes are in [docs/releases](docs/releases/).
 - Update the documentation site with the Redacted line identity, self-hosted Geist
   fonts, lowercase product names, and matching light and dark themes.
 
+### Fixed
+
+- Retain exact base SDK publication archives and SHA-256 receipts before upload;
+  npm publishes those same archives with lifecycle hooks disabled.
+
+- Build and install the optional Python FogVault wheel with the optimized release
+  profile during qualification, so the tested wheel is the publication artifact.
+
+- Python publication rejects existing distribution files instead of silently
+  accepting them on retry. Partial releases require comparing public checksums
+  and selecting only missing, qualified artifacts.
+
 ## [0.5.0-beta.3] - 2026-10-29
 
 ### Added

README.md

@@ -26,13 +26,13 @@ datafog core is a Rust library with Python, Node.js, and browser WebAssembly bin
 
 Rule-based scanning runs locally without model weights or downloads. Optional local model sessions add datafog and GLiNER2 support in Rust, Python, and Node.js.
 
-**1.0.0 release:** [release notes](docs/releases/1-0-0.mdx) · Publication underway; the coordinated release is complete only after public-registry installation checks pass.
+**Stable:** [1.0.0](https://github.com/DataFog/datafog-core/releases/tag/v1.0.0) · [Release notes](docs/releases/1-0-0.mdx) · Public registry installation checks passed.
 
 Core 1.0 freezes Workspace contract 1 across Rust, Python, Node and browser WASM, with optional native/browser [FogVault integrations](docs/integrations/fogvault.md). Snapshot v3 writes and v1/v2/v3 reads keep their existing semantics. Exact published [0.5.0-beta.3](docs/releases/0-5-0-beta-3.mdx) interchange remains tested; FogVault is independently versioned 0.1.0.
 
 ## Quickstart
 
-Once publication completes, choose the exact 1.0.0 package for your application:
+Choose the exact 1.0.0 package for your application:
 
 | SDK | Install 1.0.0 | Requirements |
 | --- | --- | --- |
@@ -175,7 +175,7 @@ The optional browser adapter uses the maintained FogVault Worker/WASM owner and
 IndexedDB storage. Native Rust, Node and Python owners use the same portable
 vault core through the registered native adapter.
 
-After the coordinated publication completes:
+Install the browser integration:
 
 ```bash
 npm install --save-exact @datafog/wasm@1.0.0 @datafog/fogvault-browser@0.1.0 @datafog/core-fogvault-browser@1.0.0
@@ -190,7 +190,7 @@ npm install --save-exact @datafog/wasm@1.0.0 @datafog/fogvault-browser@0.1.0 @da
 
 Core 1.0 includes optional local sessions for the datafog PII model and GLiNER2 in Rust, Python and Node.js. Model files are provisioned separately; model quality measurements remain separate from SDK correctness.
 
-After publication completes, install the exact 1.0.0 SDK:
+Install the exact 1.0.0 SDK:
 
 ```bash
 python -m pip install 'datafog-core==1.0.0'

docs/contracts/core-v1.md

@@ -7,8 +7,8 @@ Fresh installed Rust/Python/Node/WASM candidates passed 45 workspace cases and
 600 steps; the native registry consumer also passed its ten named cases,
 including exact published beta.3 interoperability.
 
-This is the compatibility policy for the 1.0.0 candidate, not release approval.
-Publication still requires every exact-head platform, unified-package, model and
+This compatibility policy governs the published 1.0.0 release. Each subsequent
+publication still requires every exact-head platform, unified-package, model and
 joint release check. A supported-path failure blocks release and must be fixed
 without silently changing this contract. External provider and shipping-extension
 acceptance remain separate under the owner-approved Core release scope.

docs/core-v1-release-scope.md

@@ -4,6 +4,10 @@ Decision date: October 30, 2026. The owner authorized preparing Core v1 and the
 minimum FogVault packaging needed to consume it. Nothing in this document
 authorizes registry publication, a release tag, or an extension product launch.
 
+Publication was authorized separately. The [1.0.0 release](releases/1-0-0.mdx)
+records the published packages and public-install evidence. The preparation
+decisions below remain the scope policy; extension launch is still separate.
+
 ## What Core v1 commits to
 
 Core is an independently usable SDK, with Rust, Python, native Node and browser

docs/integrations/fogvault-compatibility.md

@@ -2,10 +2,10 @@
 
 **October 30 scope update:** the owner-approved [Core v1 release scope](../core-v1-release-scope.md)
 supersedes the original joint-product launch assumptions recorded below. Core
-SDKs and adapters are 1.0.0 candidates; FogVault is a separate 0.1.0 candidate.
-Its [distribution proof](https://github.com/DataFog/fogvault/blob/staging/docs/packaging.md)
-now covers real archives and an offline registry-only beta.3 consumer. Public
-registry availability remains untested until separately authorized publication.
+SDKs and adapters are published at 1.0.0; FogVault is independently published
+at 0.1.0. Its [distribution proof](https://github.com/DataFog/fogvault/blob/v0.1.0/docs/packaging.md)
+covers real archives and a registry-only beta.3 consumer. Public registry archive
+identity and installation checks are recorded in the [release notes](../releases/1-0-0.mdx).
 G1 and shipping-extension G2/G4 evidence remain unfinished product work; no
 synthetic SDK test is recorded as their acceptance.
 

docs/integrations/fogvault.md

@@ -1,10 +1,11 @@
 # Using Core with FogVault
 
-Core now has optional native Rust, Node, Python and browser integration
-candidates. They keep Core preparation separate from persistence and activate only after the exact
-candidate has been saved. Core's existing 0.5.0-beta.3 packages and Rust 1.88
-minimum are unchanged. These new integration packages remain unpublished 1.0.0
-candidates; this change does not freeze the v1 API or approve a production host.
+Core 1.0 includes optional native Rust, Node, Python and browser integrations.
+They keep Core preparation separate from persistence and activate only after the
+exact candidate has been saved. The integration packages are version 1.0.0;
+FogVault is independently versioned 0.1.0. The reviewed Workspace contract is
+version 1. Core's Rust 1.88 minimum and exact published 0.5.0-beta.3 interchange
+regression remain unchanged. Production-host acceptance remains separate.
 
 ## Start here
 
@@ -80,16 +81,16 @@ are retained in `target/fogvault-language/check-*/`. CI qualifies this installed
 path on Linux, macOS and Windows. It does not qualify production tenant routing,
 physical providers, power cuts or every Python/Node version.
 
-For a future Core v1 release, each existing publish workflow also requires all three
-qualification workflows to have succeeded for the exact candidate commit, including
-all six native/browser scopes and all three native-language OS scopes and the installed browser model SDK scope. Pending,
-failed, incomplete or older-commit evidence blocks publication. This gate does
-not publish packages or waive the remaining release approvals.
+Core v1 and later publish workflows require all three qualification workflows
+for the exact release commit: all six native/browser scopes, all three native
+language OS scopes, the unified native Node archive and the browser model SDK
+scope. Pending, failed, incomplete or older-commit evidence blocks publication.
+This gate does not publish packages or replace release authorization.
 
 Both `--fogvault` and `--fogvault-languages` are required joint qualification
 scopes for changes that affect all maintained integrations. Neither publishes
-packages or changes the existing Core beta.3 minimum. The optional packages stay
-unpublished `1.0.0` candidates until the remaining v1 gates close.
+packages or changes the existing Core beta.3 minimum. Published versions and
+public-install evidence are recorded in the [1.0.0 release](../releases/1-0-0.mdx).
 
 ## Browser extension handoff
 
@@ -124,10 +125,10 @@ contract freeze, installed package/parity checks and exact-candidate joint gates
 External provider preservation and Josh's shipping-site acceptance remain open
 product work; their thresholds have not been lowered or reported as passed.
 
-The integration packages are unpublished 1.0.0 candidates. FogVault is an
-independently versioned 0.1.0 candidate. Its registry graph is verified locally;
-actual public availability and post-publication installation remain later,
-explicitly authorized release actions. CSV is deferred from Core v1.
+Core-owned integration packages 1.0.0 and independently versioned FogVault
+0.1.0 are published. Registry archive identities and public-install behavior are
+verified separately from local candidate packaging. The release records retain
+both sets of evidence. CSV is deferred from Core v1.
 
 [Resource observations](fogvault-resource-budget.md) support one pending
 integrated preparation. They do not establish arbitrary device memory budgets,

docs/releases/1-0-0.mdx

@@ -33,7 +33,7 @@ records their guarantees and limits.
 
 ## Packages and installation
 
-After registry publication completes, install exact stable versions:
+Install exact stable versions from the public registries:
 
 ```bash
 cargo add datafog-core@=1.0.0