docs: prepare v0.3.2 release

Author: a-a-k

CHANGELOG.md

@@ -2,6 +2,17 @@
 
 ## Unreleased
 
+## v0.3.2
+
+Patch release focused on post-audit hardening for the `v0.3.x` discovery/runtime line.
+
+### Fixed
+
+- Product planning docs now point at the tracker-backed capability backlog.
+- Model, snapshot, runtime sink, and reconciliation artifact writes now publish through atomic temp-file replacement instead of in-place overwrites.
+- Runtime HTTP service now applies explicit read-header, read, write, and idle timeouts.
+- Go toolchain and vulnerable dependencies were updated; `govulncheck` reports no active findings for the release code path.
+
 ## v0.3.1
 
 ### Fixed

README.md

@@ -5,10 +5,10 @@
 [![ci](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/Bering/ci.yml?branch=main&label=ci)](https://github.com/MB3R-Lab/Bering/actions/workflows/ci.yml)
 [![publish-schema](https://img.shields.io/github/actions/workflow/status/MB3R-Lab/Bering/publish-schema.yml?branch=main&label=publish-schema)](https://github.com/MB3R-Lab/Bering/actions/workflows/publish-schema.yml)
 [![Go version](https://img.shields.io/github/go-mod/go-version/MB3R-Lab/Bering)](https://github.com/MB3R-Lab/Bering/blob/main/go.mod)
-[![Status](https://img.shields.io/badge/status-current_release-blue)](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.1)
+[![Status](https://img.shields.io/badge/status-current_release-blue)](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.2)
 [![Public schema](https://img.shields.io/badge/public_schema-1.0%20%7C%201.1-blue)](https://github.com/MB3R-Lab/Bering/blob/main/VERSIONING.md)
 
-`Bering v0.3.1` is the current product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
+`Bering v0.3.2` is the current product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
 
 Bering turns trace input or explicit topology input into stable JSON artifacts, and it can also run as a long-lived runtime service that emits rolling discovery snapshots plus conservative reconciliation views for trace gaps.
 
@@ -28,8 +28,8 @@ Bering owns discovery and discovery-side public contracts. It does not own simul
 
 Do not treat the product release tag as the schema contract version.
 
-- Current product release for this repository: `Bering v0.3.1`
-- Current product git tag / GitHub Release: `v0.3.1`
+- Current product release for this repository: `Bering v0.3.2`
+- Current product git tag / GitHub Release: `v0.3.2`
 - Default emitted schema contracts now are:
   - `io.mb3r.bering.model@1.1.0`
   - `io.mb3r.bering.snapshot@1.1.0`
@@ -60,7 +60,7 @@ Also packaged today:
 Example:
 
 ```bash
-tar -xzf bering_0.3.1_linux_amd64.tar.gz
+tar -xzf bering_0.3.2_linux_amd64.tar.gz
 ./bering help
 ```
 

VERSIONING.md

@@ -4,8 +4,8 @@ Bering separates product release versioning from public schema contract versioni
 
 For the current published product release:
 
-- product release tag: `v0.3.1`
-- product version in release automation: `0.3.1`
+- product release tag: `v0.3.2`
+- product version in release automation: `0.3.2`
 - schema publishing tag: `schema-v1.1.0`
 - default emitted schema contracts:
   - `io.mb3r.bering.model@1.1.0`
@@ -26,8 +26,8 @@ App version changes govern the Bering CLI, the runtime service behavior, the ins
 
 Examples:
 
-- product release `v0.3.1` identifies the current Bering release line
-- `dist/release-manifest.json` records `"app_version": "0.3.1"`
+- product release `v0.3.2` identifies the current Bering release line
+- `dist/release-manifest.json` records `"app_version": "0.3.2"`
 
 ## Schema Contract Versions
 
@@ -45,8 +45,8 @@ Each schema contract has its own version, URI, and digest. Those values are inde
 
 Examples:
 
-- Bering `v0.3.1` emits `io.mb3r.bering.model@1.1.0`
-- Bering `v0.3.1` emits `io.mb3r.bering.snapshot@1.1.0`
+- Bering `v0.3.2` emits `io.mb3r.bering.model@1.1.0`
+- Bering `v0.3.2` emits `io.mb3r.bering.snapshot@1.1.0`
 - `bering validate` still accepts `1.0.0` artifacts without mutation or migration
 - `schema-v1.1.0` publishes the schema files to GitHub Pages; it is not a product release tag
 

docs/backlog.md

@@ -8,7 +8,7 @@ Snapshot date: `2026-05-01`
 
 ## Current Product Surface
 
-Bering is the discovery and publication layer for the MB3R toolchain. The current `v0.3.1` release provides:
+Bering is the discovery and publication layer for the MB3R toolchain. The current `v0.3.2` release provides:
 
 - deterministic batch discovery from normalized trace files, OTLP JSON, trace directories, and explicit `topology_api` inputs;
 - runtime OTLP/HTTP and OTLP/gRPC ingest;

docs/install.md

@@ -1,6 +1,6 @@
 # Install
 
-Bering `v0.3.1` is the current product release. It emits `io.mb3r.bering.model@1.1.0` and `io.mb3r.bering.snapshot@1.1.0` by default, while still validating the preserved `1.0.0` contracts.
+Bering `v0.3.2` is the current product release. It emits `io.mb3r.bering.model@1.1.0` and `io.mb3r.bering.snapshot@1.1.0` by default, while still validating the preserved `1.0.0` contracts.
 
 ## Binary Archives
 
@@ -14,18 +14,18 @@ Supported release targets:
 - `darwin/arm64`
 - `windows/amd64`
 
-Example release asset names for `v0.3.1`:
+Example release asset names for `v0.3.2`:
 
-- `bering_0.3.1_linux_amd64.tar.gz`
-- `bering_0.3.1_linux_arm64.tar.gz`
-- `bering_0.3.1_darwin_amd64.tar.gz`
-- `bering_0.3.1_darwin_arm64.tar.gz`
-- `bering_0.3.1_windows_amd64.zip`
+- `bering_0.3.2_linux_amd64.tar.gz`
+- `bering_0.3.2_linux_arm64.tar.gz`
+- `bering_0.3.2_darwin_amd64.tar.gz`
+- `bering_0.3.2_darwin_arm64.tar.gz`
+- `bering_0.3.2_windows_amd64.zip`
 
 Example:
 
 ```bash
-tar -xzf bering_0.3.1_linux_amd64.tar.gz
+tar -xzf bering_0.3.2_linux_amd64.tar.gz
 ./bering help
 ```
 
@@ -40,8 +40,8 @@ go build ./cmd/bering
 Pull the published runtime image:
 
 ```bash
-docker pull ghcr.io/mb3r-lab/bering:v0.3.1
-docker run --rm ghcr.io/mb3r-lab/bering:v0.3.1 help
+docker pull ghcr.io/mb3r-lab/bering:v0.3.2
+docker run --rm ghcr.io/mb3r-lab/bering:v0.3.2 help
 ```
 
 The release manifest records all published image references and the final digest in `oci_images`.
@@ -51,13 +51,13 @@ The release manifest records all published image references and the final digest
 Install directly from the published OCI chart:
 
 ```bash
-helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.1
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.2
 ```
 
 Override the image repository, tag, or digest if you mirror artifacts:
 
 ```bash
-helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.1 \
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.2 \
   --set image.repository=ghcr.io/mb3r-lab/bering \
   --set image.digest=sha256:...
 ```
@@ -67,7 +67,7 @@ helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.1 \
 Download `bering-contracts_<version>.tar.gz` to consume the public schema contracts offline:
 
 ```bash
-tar -xzf bering-contracts_0.3.1.tar.gz
+tar -xzf bering-contracts_0.3.2.tar.gz
 cat contracts-manifest.json
 ```
 

docs/planning/minor-schema-contract-evolution/implementation-note.md

@@ -28,9 +28,9 @@
 ## Release And Publication Boundary
 
 - Product release versioning remains separate from schema contract versioning.
-- The current product line is `v0.3.1`, and it emits `1.1.0` contracts by default.
+- The current product line is `v0.3.2`, and it emits `1.1.0` contracts by default.
 - The schema publication tag used for external publication is `schema-v1.1.0`.
-- The `1.1.0` schema line is now published on GitHub Pages and shipped by the `v0.3.1` product release.
+- The `1.1.0` schema line is now published on GitHub Pages, was introduced in the `v0.3.1` product release, and remains the default emitted line in `v0.3.2`.
 
 ## Explicit Non-Goals For This Minor
 

docs/schema-publishing.md

@@ -11,7 +11,7 @@ This workflow is separate from the product release workflow:
 
 For the current release line, that means:
 
-- product release: `v0.3.1`
+- product release: `v0.3.2`
 - schema publishing: `schema-v1.1.0`
 
 ## One-time repository setup