Refresh documentation for v0.2.0

Author: a-a-k

README.md

@@ -1,6 +1,6 @@
 # Bering
 
-`Bering v0.1.0` is the first public product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
+`Bering v0.2.0` 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.
 
@@ -20,14 +20,14 @@ 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.
 
-- Product release for this repository: `Bering v0.1.0`
-- Product git tag / GitHub Release: `v0.1.0`
+- Current product release for this repository: `Bering v0.2.0`
+- Current product git tag / GitHub Release: `v0.2.0`
 - Public schema contracts emitted by this release remain:
   - `io.mb3r.bering.model@1.0.0`
   - `io.mb3r.bering.snapshot@1.0.0`
 - Schema publishing tag remains separate: `schema-v1.0.0`
 
-In other words: Bering `v0.1.0` ships a first public product release while continuing to emit the already-stable schema contracts at `1.0.0`.
+In other words: Bering `v0.2.0` advances the product release line while continuing to emit the already-stable schema contracts at `1.0.0`.
 
 ## Installation
 
@@ -49,7 +49,7 @@ Also packaged today:
 Example:
 
 ```bash
-tar -xzf bering_0.1.0_linux_amd64.tar.gz
+tar -xzf bering_0.2.0_linux_amd64.tar.gz
 ./bering help
 ```
 

RELEASING.md

@@ -9,7 +9,7 @@ Product releases and schema publishing are separate operations:
 - product release tags: `vX.Y.Z`
 - schema publishing tags: `schema-vA.B.C`
 
-For the first public product release, use `v0.1.0` for the product release and keep the public schema contracts pinned at `1.0.0`.
+Product releases advance independently from the public schema contracts. As of the current release line, use `v0.2.0` for the product release while the public schema contracts remain pinned at `1.0.0`.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ Dry-run without publishing:
 
 ```bash
 make release-dry-run \
-  VERSION=0.1.0 \
+  VERSION=0.2.0 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)"
 ```
@@ -37,20 +37,20 @@ Full local release payload with OCI publish:
 
 ```bash
 make release-local \
-  VERSION=0.1.0 \
+  VERSION=0.2.0 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)" \
-  IMAGE_REPOSITORY=registry.example.com/bering \
-  CHART_OCI_REPOSITORY=oci://registry.example.com/charts \
+  IMAGE_REPOSITORY=ghcr.io/mb3r-lab/bering \
+  CHART_OCI_REPOSITORY=oci://ghcr.io/mb3r-lab/charts \
   PUBLISH_OCI=1
 ```
 
 If the chart version must intentionally differ from the app version:
 
 ```bash
 make chart-package \
-  VERSION=0.1.0 \
-  CHART_VERSION=0.1.1 \
+  VERSION=0.2.0 \
+  CHART_VERSION=0.2.1 \
   ALLOW_CHART_VERSION_MISMATCH=1
 ```
 
@@ -80,7 +80,7 @@ These variables control the release payload:
 - `CHART_VERSION`: optional explicit chart version
 - `ALLOW_CHART_VERSION_MISMATCH=1`: required when `CHART_VERSION != VERSION`
 
-For `v0.1.0`, `VERSION=0.1.0` while the emitted public schema contracts remain `1.0.0`.
+For `v0.2.0`, `VERSION=0.2.0` while the emitted public schema contracts remain `1.0.0`.
 
 ## Expected Output
 

VERSIONING.md

@@ -2,10 +2,10 @@
 
 Bering separates product release versioning from public schema contract versioning.
 
-For the first public product release:
+For the current published product release:
 
-- product release tag: `v0.1.0`
-- product version in release automation: `0.1.0`
+- product release tag: `v0.2.0`
+- product version in release automation: `0.2.0`
 - schema publishing tag: `schema-v1.0.0`
 - emitted schema contracts:
   - `io.mb3r.bering.model@1.0.0`
@@ -23,8 +23,8 @@ App version changes govern the Bering CLI, the runtime service behavior, the ins
 
 Examples:
 
-- product release `v0.1.0` identifies the first public Bering release
-- `dist/release-manifest.json` records `"app_version": "0.1.0"`
+- product release `v0.2.0` identifies the current Bering release line
+- `dist/release-manifest.json` records `"app_version": "0.2.0"`
 
 ## Schema Contract Versions
 
@@ -42,8 +42,8 @@ Each schema contract has its own version, URI, and digest. Those values are inde
 
 Examples:
 
-- Bering `v0.1.0` still emits `io.mb3r.bering.model@1.0.0`
-- Bering `v0.1.0` still emits `io.mb3r.bering.snapshot@1.0.0`
+- Bering `v0.2.0` still emits `io.mb3r.bering.model@1.0.0`
+- Bering `v0.2.0` still emits `io.mb3r.bering.snapshot@1.0.0`
 - `schema-v1.0.0` publishes the schema files to GitHub Pages; it is not a product release tag
 
 Rules:

docs/install.md

@@ -1,6 +1,6 @@
 # Install
 
-Bering `v0.1.0` is the first public product release. It still emits the stable public schema contracts `io.mb3r.bering.model@1.0.0` and `io.mb3r.bering.snapshot@1.0.0`.
+Bering `v0.2.0` is the current product release. It still emits the stable public schema contracts `io.mb3r.bering.model@1.0.0` and `io.mb3r.bering.snapshot@1.0.0`.
 
 ## Binary Archives
 
@@ -14,18 +14,18 @@ Supported release targets:
 - `darwin/arm64`
 - `windows/amd64`
 
-Example release asset names:
+Example release asset names for `v0.2.0`:
 
-- `bering_0.1.0_linux_amd64.tar.gz`
-- `bering_0.1.0_linux_arm64.tar.gz`
-- `bering_0.1.0_darwin_amd64.tar.gz`
-- `bering_0.1.0_darwin_arm64.tar.gz`
-- `bering_0.1.0_windows_amd64.zip`
+- `bering_0.2.0_linux_amd64.tar.gz`
+- `bering_0.2.0_linux_arm64.tar.gz`
+- `bering_0.2.0_darwin_amd64.tar.gz`
+- `bering_0.2.0_darwin_arm64.tar.gz`
+- `bering_0.2.0_windows_amd64.zip`
 
 Example:
 
 ```bash
-tar -xzf bering_0.1.0_linux_amd64.tar.gz
+tar -xzf bering_0.2.0_linux_amd64.tar.gz
 ./bering help
 ```
 
@@ -37,28 +37,28 @@ go build ./cmd/bering
 
 ## OCI Image
 
-Pull the runtime image from any OCI registry:
+Pull the published runtime image:
 
 ```bash
-docker pull registry.example.com/bering:v0.1.0
-docker run --rm registry.example.com/bering:v0.1.0 help
+docker pull ghcr.io/mb3r-lab/bering:v0.2.0
+docker run --rm ghcr.io/mb3r-lab/bering:v0.2.0 help
 ```
 
 The release manifest records all published image references and the final digest in `oci_images`.
 
 ## OCI Helm Chart
 
-Install directly from an OCI registry:
+Install directly from the published OCI chart:
 
 ```bash
-helm install bering oci://registry.example.com/charts/bering --version 0.1.0
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.2.0
 ```
 
 Override the image repository, tag, or digest if you mirror artifacts:
 
 ```bash
-helm install bering oci://registry.example.com/charts/bering --version 0.1.0 \
-  --set image.repository=registry.example.com/bering \
+helm install bering oci://ghcr.io/mb3r-lab/charts/bering --version 0.2.0 \
+  --set image.repository=ghcr.io/mb3r-lab/bering \
   --set image.digest=sha256:...
 ```
 
@@ -67,7 +67,7 @@ helm install bering oci://registry.example.com/charts/bering --version 0.1.0 \
 Download `bering-contracts_<version>.tar.gz` to consume the public schema contracts offline:
 
 ```bash
-tar -xzf bering-contracts_0.1.0.tar.gz
+tar -xzf bering-contracts_0.2.0.tar.gz
 cat contracts-manifest.json
 ```
 

docs/schema-publishing.md

@@ -9,9 +9,9 @@ This workflow is separate from the product release workflow:
 - product release tags: `vX.Y.Z`
 - schema publishing tags: `schema-vA.B.C`
 
-For the first public product release, that means:
+For the current release line, that means:
 
-- product release: `v0.1.0`
+- product release: `v0.2.0`
 - schema publishing: `schema-v1.0.0`
 
 ## One-time repository setup