Release v0.3.0 with schema contract v1.1.0

Author: a-a-k

.github/workflows/publish-schema.yml

@@ -73,8 +73,10 @@ jobs:
       - name: Validate schema JSON and $id binding
         shell: bash
         env:
+          MODEL_SCHEMA_VERSION: ${{ steps.contract.outputs.model_schema_version }}
           EXPECTED_MODEL_URI: ${{ steps.contract.outputs.model_schema_uri }}
           EXPECTED_MODEL_DIGEST: ${{ steps.contract.outputs.model_schema_digest }}
+          SNAPSHOT_SCHEMA_VERSION: ${{ steps.contract.outputs.snapshot_schema_version }}
           EXPECTED_SNAPSHOT_URI: ${{ steps.contract.outputs.snapshot_schema_uri }}
           EXPECTED_SNAPSHOT_DIGEST: ${{ steps.contract.outputs.snapshot_schema_digest }}
         run: |
@@ -87,12 +89,12 @@ jobs:
 
           checks = [
               (
-                  Path("api/schema/model.schema.json"),
+                  Path(f"api/schema/model/v{os.environ['MODEL_SCHEMA_VERSION']}/model.schema.json"),
                   os.environ["EXPECTED_MODEL_URI"],
                   os.environ["EXPECTED_MODEL_DIGEST"],
               ),
               (
-                  Path("api/schema/snapshot.schema.json"),
+                  Path(f"api/schema/snapshot/v{os.environ['SNAPSHOT_SCHEMA_VERSION']}/snapshot.schema.json"),
                   os.environ["EXPECTED_SNAPSHOT_URI"],
                   os.environ["EXPECTED_SNAPSHOT_DIGEST"],
               ),
@@ -127,17 +129,15 @@ jobs:
           set -euo pipefail
 
           ROOT="out"
-          MODEL_VERSION_DIR="${ROOT}/schema/model/v${MODEL_SCHEMA_VERSION}"
           MODEL_LATEST_DIR="${ROOT}/schema/model/latest"
-          SNAPSHOT_VERSION_DIR="${ROOT}/schema/snapshot/v${SNAPSHOT_SCHEMA_VERSION}"
           SNAPSHOT_LATEST_DIR="${ROOT}/schema/snapshot/latest"
 
-          mkdir -p "${MODEL_VERSION_DIR}" "${MODEL_LATEST_DIR}" "${SNAPSHOT_VERSION_DIR}" "${SNAPSHOT_LATEST_DIR}" "${ROOT}/schema"
+          mkdir -p "${ROOT}/schema" "${MODEL_LATEST_DIR}" "${SNAPSHOT_LATEST_DIR}"
 
-          cp api/schema/model.schema.json "${MODEL_VERSION_DIR}/model.schema.json"
-          cp api/schema/model.schema.json "${MODEL_LATEST_DIR}/model.schema.json"
-          cp api/schema/snapshot.schema.json "${SNAPSHOT_VERSION_DIR}/snapshot.schema.json"
-          cp api/schema/snapshot.schema.json "${SNAPSHOT_LATEST_DIR}/snapshot.schema.json"
+          cp -R api/schema/model "${ROOT}/schema/"
+          cp -R api/schema/snapshot "${ROOT}/schema/"
+          cp "api/schema/model/v${MODEL_SCHEMA_VERSION}/model.schema.json" "${MODEL_LATEST_DIR}/model.schema.json"
+          cp "api/schema/snapshot/v${SNAPSHOT_SCHEMA_VERSION}/snapshot.schema.json" "${SNAPSHOT_LATEST_DIR}/snapshot.schema.json"
 
           UPDATED_AT="$(date -u +"%Y-%m-%dT%H:%M:%SZ")"
           cat > "${ROOT}/schema/index.json" <<EOF

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Unreleased
 
+## v0.3.0
+
+### Added
+
+- Versioned public schema contract evolution to `io.mb3r.bering.model@1.1.0` and `io.mb3r.bering.snapshot@1.1.0` without mutating the preserved `1.0.0` contracts.
+- Typed public topology metadata for stable edge identity, service placements, shared fate-domain references, edge resilience policy, observed latency/error summaries, policy scope, and richer endpoint fidelity.
+- Versioned contracts-pack and release-manifest plumbing aligned with the new schema tree and pinned `1.1.0` digests.
+- Documentation, migration guidance, examples, and schema publishing workflow updates aligned with the `1.1.0` contract line.
+
 ## v0.2.0
 
 ### Added

README.md

@@ -1,6 +1,6 @@
 # Bering
 
-`Bering v0.2.0` is the current product release of Bering: a discovery and publishing layer for service topology and endpoint contracts.
+`Bering v0.3.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.
 
@@ -14,20 +14,23 @@ Bering turns trace input or explicit topology input into stable JSON artifacts,
 
 ## Where Bering Stops
 
-Bering owns discovery and discovery-side public contracts. It does not own simulation, policy evaluation, gating, chaos execution, or benchmark-specific rules.
+Bering owns discovery and discovery-side public contracts. It does not own simulation math, retry-amplification math, timeout-wave propagation, blast-radius scoring, policy evaluation, gating, or chaos execution.
 
 ## Product Version vs Schema Version
 
 Do not treat the product release tag as the schema contract version.
 
-- 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:
+- Current product release for this repository: `Bering v0.3.0`
+- Current product git tag / GitHub Release: `v0.3.0`
+- Default emitted schema contracts now are:
+  - `io.mb3r.bering.model@1.1.0`
+  - `io.mb3r.bering.snapshot@1.1.0`
+- Previously published contracts remain valid and immutable:
   - `io.mb3r.bering.model@1.0.0`
   - `io.mb3r.bering.snapshot@1.0.0`
-- Schema publishing tag remains separate: `schema-v1.0.0`
+- Schema publishing tag remains separate: `schema-v1.1.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`.
+`bering validate` accepts both the preserved `1.0.0` artifacts and the current `1.1.0` artifacts.
 
 ## Installation
 
@@ -49,7 +52,7 @@ Also packaged today:
 Example:
 
 ```bash
-tar -xzf bering_0.2.0_linux_amd64.tar.gz
+tar -xzf bering_0.3.0_linux_amd64.tar.gz
 ./bering help
 ```
 
@@ -74,7 +77,7 @@ go run ./cmd/bering discover \
   --discovered-at 2026-03-03T00:00:00Z
 ```
 
-Expected result: a deterministic `io.mb3r.bering.model@1.0.0` artifact.
+Expected result: a deterministic `io.mb3r.bering.model@1.1.0` artifact.
 
 ### 2) Validate an artifact
 
@@ -96,7 +99,7 @@ go run ./cmd/bering discover \
   --discovered-at 2026-03-03T00:00:00Z
 ```
 
-Expected result: a model artifact plus an `io.mb3r.bering.snapshot@1.0.0` envelope.
+Expected result: a model artifact plus an `io.mb3r.bering.snapshot@1.1.0` envelope.
 
 ### 4) Run runtime mode
 
@@ -134,20 +137,20 @@ go run ./cmd/sheaft run \
 ### Core model
 
 - `name`: `io.mb3r.bering.model`
-- `version`: `1.0.0`
-- `uri`: `https://mb3r-lab.github.io/Bering/schema/model/v1.0.0/model.schema.json`
-- `digest`: `sha256:272277c093f37580adcd2dded225bd37c86539d642d7910baad7e4228227d1a7`
+- `version`: `1.1.0`
+- `uri`: `https://mb3r-lab.github.io/Bering/schema/model/v1.1.0/model.schema.json`
+- `digest`: `sha256:bc9a60736c9e6bda9599243fd68f293b88f42ade65321d8267369a5c3214779a`
 
-This is the stable topology artifact intended for file-based consumers and tools such as Sheaft.
+This is the stable topology artifact intended for file-based consumers and tools such as Sheaft. It now carries first-class edge ids, typed service placement and shared-fate metadata, typed edge resilience policy, optional observed edge timing summaries, policy scope metadata, and richer endpoint fidelity.
 
 ### Snapshot envelope
 
 - `name`: `io.mb3r.bering.snapshot`
-- `version`: `1.0.0`
-- `uri`: `https://mb3r-lab.github.io/Bering/schema/snapshot/v1.0.0/snapshot.schema.json`
-- `digest`: `sha256:87e4e887ed4a37b72f6136e268b73552eccb92941c4de2c6f3a514dd066ea972`
+- `version`: `1.1.0`
+- `uri`: `https://mb3r-lab.github.io/Bering/schema/snapshot/v1.1.0/snapshot.schema.json`
+- `digest`: `sha256:53b127608b2aaa4fabb352b998cd6b2c5ed558764729a09abea56f4f9b40fa01`
 
-This wraps the model with runtime window metadata, ingest counts, coverage, provenance, and topology diffs.
+This wraps the model with runtime window metadata, ingest counts, coverage, provenance, topology diffs, and discovery-side copies of the same typed placement, resilience, and observed edge metadata.
 
 ### Runtime reconciliation views
 
@@ -158,7 +161,13 @@ Runtime mode also keeps a conservative reconciliation layer for sparse traffic a
 - `guardrail_union`: the conservative default downstream artifact
 - a machine-readable reconciliation report for operators
 
-These runtime views do not change the public `io.mb3r.bering.model@1.0.0` or `io.mb3r.bering.snapshot@1.0.0` contracts.
+These runtime views do not change the public `io.mb3r.bering.model@1.1.0` or `io.mb3r.bering.snapshot@1.1.0` contracts.
+
+### Population Today
+
+- `topology_api` input and discovery overlays are the first-class write surfaces for typed `placements`, `shared_resource_refs`, `resilience`, `observed`, `policy_scope`, and richer endpoint metadata.
+- Trace discovery can derive stable edge ids, endpoint `method` and `path`, and `observed.latency_ms.*` summaries when span timing exists.
+- Generic trace ingestion does not currently infer timeout policies, retry policies, circuit-breaker settings, placement groups, or shared resource references. Those remain out of scope for Bering trace inference today.
 
 ## Release Packaging
 

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`
 
-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`.
+Product releases advance independently from the public schema contracts. As of the current release line, use `v0.3.0` for the product release while the default emitted public schema contracts are `1.1.0` and the preserved `1.0.0` contracts remain available for validation and pinned consumers.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ Dry-run without publishing:
 
 ```bash
 make release-dry-run \
-  VERSION=0.2.0 \
+  VERSION=0.3.0 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)"
 ```
@@ -37,7 +37,7 @@ Full local release payload with OCI publish:
 
 ```bash
 make release-local \
-  VERSION=0.2.0 \
+  VERSION=0.3.0 \
   GIT_SHA="$(git rev-parse HEAD)" \
   BUILD_DATE="$(git show -s --format=%cI HEAD)" \
   IMAGE_REPOSITORY=ghcr.io/mb3r-lab/bering \
@@ -49,8 +49,8 @@ If the chart version must intentionally differ from the app version:
 
 ```bash
 make chart-package \
-  VERSION=0.2.0 \
-  CHART_VERSION=0.2.1 \
+  VERSION=0.3.0 \
+  CHART_VERSION=0.3.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.2.0`, `VERSION=0.2.0` while the emitted public schema contracts remain `1.0.0`.
+For `v0.3.0`, `VERSION=0.3.0` while the default emitted public schema contracts are `1.1.0`.
 
 ## Expected Output
 

VERSIONING.md

@@ -4,10 +4,13 @@ Bering separates product release versioning from public schema contract versioni
 
 For the current published product release:
 
-- product release tag: `v0.2.0`
-- product version in release automation: `0.2.0`
-- schema publishing tag: `schema-v1.0.0`
-- emitted schema contracts:
+- product release tag: `v0.3.0`
+- product version in release automation: `0.3.0`
+- schema publishing tag: `schema-v1.1.0`
+- default emitted schema contracts:
+  - `io.mb3r.bering.model@1.1.0`
+  - `io.mb3r.bering.snapshot@1.1.0`
+- previously published and still valid contracts:
   - `io.mb3r.bering.model@1.0.0`
   - `io.mb3r.bering.snapshot@1.0.0`
 
@@ -23,8 +26,8 @@ App version changes govern the Bering CLI, the runtime service behavior, the ins
 
 Examples:
 
-- product release `v0.2.0` identifies the current Bering release line
-- `dist/release-manifest.json` records `"app_version": "0.2.0"`
+- product release `v0.3.0` identifies the current Bering release line
+- `dist/release-manifest.json` records `"app_version": "0.3.0"`
 
 ## Schema Contract Versions
 
@@ -42,9 +45,10 @@ Each schema contract has its own version, URI, and digest. Those values are inde
 
 Examples:
 
-- 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
+- Bering `v0.3.0` now emits `io.mb3r.bering.model@1.1.0`
+- Bering `v0.3.0` now 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
 
 Rules:
 
@@ -53,6 +57,7 @@ Rules:
 - Breaking schema changes require a new contract major version.
 - Non-breaking schema additions require a new contract minor version.
 - Pure fixes that do not change contract meaning require a new contract patch version.
+- This repository currently keeps the model and snapshot contracts on the same schema version line for publication and default emission.
 
 ## Image Tags
 
@@ -98,4 +103,4 @@ Rules:
 
 - A breaking schema change increments that contract's major version.
 - Existing published contract versions remain valid and immutable.
-- If Bering changes which schema version it emits by default in a way that breaks existing consumers, that is also an app-surface breaking change and should trigger a new app major version.
+- If Bering changes which schema version it emits by default, call that out explicitly in release notes and keep older published contract versions available to validators and pinned consumers.