docs: sync Bering v0.3.4 compatibility

Author: a-a-k

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## Unreleased
+
+- recorded app-level sync with the published Bering `v0.3.4` release/package in `compatibility-manifest.json`
+- refreshed compatibility docs and README badges to distinguish Bering app-package sync from unchanged `1.0.0` / `1.1.0` schema contract pins
+
 ## v0.2.4 - 2026-05-31
 
 Technical-preview feature release focused on trustable gate evidence, benchmark packaging, and explainable gate decisions for the `v0.2.x` line.

README.md

@@ -7,6 +7,7 @@
 [![Go version](https://img.shields.io/github/go-mod/go-version/MB3R-Lab/Sheaft)](https://github.com/MB3R-Lab/Sheaft/blob/main/go.mod)
 [![Technical preview](https://img.shields.io/badge/preview-v0.2.4-orange)](https://github.com/MB3R-Lab/Sheaft/releases/tag/v0.2.4)
 [![Bering support](https://img.shields.io/badge/Bering-1.0%20%7C%201.1-blue)](https://github.com/MB3R-Lab/Sheaft/blob/main/docs/compatibility-matrix.md)
+[![Bering app](https://img.shields.io/badge/Bering%20app-v0.3.4-informational)](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.4)
 
 Sheaft is a downstream resilience posture engine and CI/CD gate for model artifacts produced by Bering or another compatible upstream producer.
 
@@ -59,6 +60,8 @@ Unknown or mismatched contracts are rejected. There is no silent fallback for un
 
 `1.0.0` remains the baseline semantics line and the reference artifact line for cross-version comparisons. `1.1.0` adds richer typed metadata for timeout, retry, placement, shared-resource, and edge-scoped analysis when the artifact provides it.
 
+The current `main` line has also been app-level synced against the published Bering `v0.3.4` release/package. That sync does not change the accepted Bering schema contract pins.
+
 ## Installation
 
 Preferred path for the current technical preview release:
@@ -139,7 +142,7 @@ sheaft run --model <artifact.json> --analysis <analysis.yaml> --contract-policy
 
 ## Service mode
 
-The long-running service remains experimental in `v0.1.x`, but it is included in the public technical preview.
+The long-running service remains experimental in `v0.2.x`, but it is included in the public technical preview.
 
 The checked-in example is runnable without editing paths:
 
@@ -172,6 +175,7 @@ Sheaft is intentionally downstream of Bering artifacts and schemas.
 - `1.0.0` is kept as the stable fail-stop baseline semantics line.
 - `1.1.0` enables additive path-aware diagnostics and fault-profile analysis when metadata exists.
 - Compatibility metadata is published in [compatibility-manifest.json](compatibility-manifest.json).
+- The current app-level Bering release/package sync target is `v0.3.4`; schema acceptance still comes only from the pinned contracts above.
 - Schema ownership stays with Bering; Sheaft does not redefine those schema versions.
 - `--contract-policy` can narrow or deprecate accepted contracts for a specific project, but it cannot expand support beyond the built-in whitelist.
 

RELEASING.md

@@ -1,6 +1,6 @@
 # Releasing Sheaft
 
-Sheaft release automation is tag-driven and platform-neutral. The `v0.1.x` line is intentionally published as a technical preview, so release notes and README language should stay explicit about what is stable versus experimental.
+Sheaft release automation is tag-driven and platform-neutral. The `0.x` line is intentionally published as a technical preview, so release notes and README language should stay explicit about what is stable versus experimental.
 
 The canonical release contract is the generated payload:
 
@@ -10,14 +10,15 @@ The canonical release contract is the generated payload:
 
 GitHub Releases publish that payload, but GitHub metadata is not the source of truth.
 
-`compatibility-manifest.json` is intentionally checked in because it mirrors the current strict upstream contract pins and is drift-checked in CI. `release-manifest.json` is release-specific and must not be committed from `main`; it is generated during `make release-dry-run`, `make release-local`, and tag-driven release publishing, then uploaded as a release asset.
+`compatibility-manifest.json` is intentionally checked in because it mirrors the current strict upstream contract pins plus tested upstream app release metadata, and is drift-checked in CI. `release-manifest.json` is release-specific and must not be committed from `main`; it is generated during `make release-dry-run`, `make release-local`, and tag-driven release publishing, then uploaded as a release asset.
 
 ## Ownership Boundary
 
 - Bering owns upstream artifact schemas and release metadata.
 - Sheaft stays downstream and only declares compatibility with Bering-produced artifacts.
 - Sheaft must not redefine or silently mutate Bering schema versions.
 - Strict contract validation remains in `internal/modelcontract/contract.go` and is mirrored into `compatibility-manifest.json`.
+- Tested upstream Bering app release/package syncs are recorded in `compatibility-manifest.json`; they do not expand schema acceptance.
 
 ## Version Surfaces
 

compatibility-manifest.json

@@ -46,5 +46,7 @@
       "schema_digest": "sha256:53b127608b2aaa4fabb352b998cd6b2c5ed558764729a09abea56f4f9b40fa01"
     }
   ],
-  "tested_bering_app_versions": []
+  "tested_bering_app_versions": [
+    "v0.3.4"
+  ]
 }

docs/compatibility-matrix.md

@@ -4,6 +4,12 @@ Sheaft is a strict downstream consumer of Bering-produced artifacts. It does not
 
 The machine-readable equivalent of this page is the repo-root `compatibility-manifest.json`.
 
+## Current App-Level Sync
+
+The current `main` line has been synced against the published Bering `v0.3.4` release/package. This is recorded in `compatibility-manifest.json` as `tested_bering_app_versions: ["v0.3.4"]`.
+
+That package sync does not widen or narrow the accepted upstream schema contracts. The strict contract pins remain the `1.0.0` and `1.1.0` Bering model/snapshot lines below.
+
 ## Current Matrix
 
 | Sheaft line | Status | Bering model contract | Model URI | Model digest | Bering snapshot contract | Snapshot URI | Snapshot digest | Notes |
@@ -32,4 +38,4 @@ Overlapping metrics produce diffs. Metrics that are unavailable on one side rema
 
 ## Release Note
 
-This repository currently has no Git tags or published Sheaft release lines. The `main` row therefore represents the active unreleased consumer pin. When versioned Sheaft releases start, add one row per released line and keep `main` as the forward-looking row.
+Published Sheaft releases through `v0.2.4` use the same accepted Bering `1.0.0` and `1.1.0` contract pins. The `main` row represents the active post-`v0.2.4` consumer pin; when a future Sheaft release changes accepted upstream contracts, add one row per released line and keep `main` as the forward-looking row.

docs/compatibility.md

@@ -25,7 +25,9 @@ Runtime truth lives in `internal/modelcontract/contract.go`.
 - required schema digests
 - tested Bering app versions, if known
 
-An empty `tested_bering_app_versions` array means Sheaft has not published an app-level Bering compatibility statement beyond the schema pins that are already required.
+`tested_bering_app_versions` lists Bering product tags this Sheaft line has been app-level synced against. The current line records Bering `v0.3.4`; schema acceptance is still controlled only by `supported_contracts`.
+
+An empty `tested_bering_app_versions` array would mean Sheaft has not published an app-level Bering compatibility statement beyond the schema pins that are already required.
 
 ## How Downstream CI Should Use It
 
@@ -82,6 +84,7 @@ When a contract is still supported globally but deprecated for a given project,
 - Sheaft declares compatibility with Bering `1.0.0` and `1.1.0` model/snapshot release lines.
 - `1.0.0` remains the baseline fail-stop semantics line and the cross-version comparison reference.
 - `1.1.0` enables additive path-aware timeout, retry, placement, shared-resource, and edge-scoped analysis when the artifact carries that metadata.
+- The current app-level Bering release/package sync target is `v0.3.4`; no Bering schema contract pins changed for that package release.
 - Missing advanced metadata is surfaced as unavailable rather than guessed.
 - Changing the Sheaft app version does not automatically widen or narrow compatibility.
 

docs/contract-release-workflow.md

@@ -12,13 +12,20 @@ Keep Sheaft as a strict downstream consumer:
 
 ## Current Upstream Metadata Source
 
-The canonical published Bering release manifest currently consumed by Sheaft is:
+The canonical published Bering schema metadata currently consumed by Sheaft is:
 
 - `https://mb3r-lab.github.io/Bering/schema/index.json`
 
 Sheaft CI verifies that this published metadata matches the currently published `1.1.0` model and snapshot contracts in `internal/modelcontract/contract.go`.
 Published remote schema sync is verified separately for every supported versioned model and snapshot schema mirror.
 
+The current app-level Bering release/package sync target is:
+
+- Release: `https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.4`
+- Release manifest asset: `release-manifest.json` (`sha256:d7f4b3d61ff8e36bd370dadd351e51a2b2803677ae12a5e0fbb81faacfd01e20`)
+- Contracts pack asset: `bering-contracts_0.3.4.tar.gz` (`sha256:3865a8e7152c8a383f34d99334bc392cfd0ec793325b530d392723f67839ddbf`)
+- Schema contract pins consumed by Sheaft remain `1.0.0` and `1.1.0`.
+
 ## Release Policy
 
 ### Non-breaking upstream schema release
@@ -39,6 +46,16 @@ When Bering publishes a new contract line that Sheaft wants to support:
    - compatibility matrix check
    - `go test ./...`
 
+### Upstream app/package release with unchanged schemas
+
+When Bering publishes a product release that keeps the same schema contract lines:
+
+1. confirm the Bering release and package assets are published;
+2. update `tested_bering_app_versions` through the compatibility manifest generator;
+3. update `README.md`, [compatibility matrix](compatibility-matrix.md), and this workflow note with the Bering release/package checkpoint;
+4. regenerate `compatibility-manifest.json`;
+5. run the compatibility-manifest check and `go test ./...`.
+
 ### Breaking upstream schema release
 
 If the new Bering contract is not backward compatible for Sheaft:

docs/release-assets.md

@@ -31,6 +31,7 @@ The GitHub Release also publishes the fixed benchmark slice quality report as re
 `compatibility-manifest.json` answers:
 
 - which upstream Bering contracts does this Sheaft line accept?
+- which Bering app release packages has this Sheaft line been synced against, if known?
 
 `release-manifest.json` answers:
 
@@ -39,6 +40,7 @@ The GitHub Release also publishes the fixed benchmark slice quality report as re
 Keep them separate:
 
 - compatibility changes track Bering schema support
+- tested app-version entries track app-level Bering release/package syncs that keep the same schema pins
 - release-manifest changes track build outputs for a specific Sheaft release
 
 ## CI Consumption Pattern

docs/roadmap.md

@@ -23,6 +23,7 @@ This file captures the repository-side audit refreshed on 2026-05-31: current Gi
 - Active backlog milestone: `Post-v0.2.4 technical preview`
 - Previous release-tracking issue: [#82](https://github.com/MB3R-Lab/Sheaft/issues/82)
 - Current release-tracking issue: [#83](https://github.com/MB3R-Lab/Sheaft/issues/83)
+- Current upstream Bering app/package sync target: [Bering v0.3.4](https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.4), with unchanged `1.0.0` / `1.1.0` schema contract pins.
 - GitHub issue and milestone sync was refreshed on 2026-05-31 after shipping the `v0.2.4` technical-preview release.
 
 ## Latest Release/Package Checkpoint
@@ -197,4 +198,5 @@ Goal: make the Bering -> Sheaft workflow repeatable beyond a technical preview.
 - R4.3 landed on 2026-05-30 as the first trustable-gate documentation step: `docs/assumptions-and-limitations.md` now contains the do-not-trust signal catalogue and detector field shape.
 - R4.1/R4.2 landed on 2026-05-31: `make benchmark-slice` now runs the fixed Sheaft-on-Bering benchmark and emits `quality-report.json`.
 - R9.1 landed on 2026-05-31: gate decisions now include machine-readable why reasons and CLI `--why` output.
+- Bering app/package sync refreshed on 2026-05-31 after Bering `v0.3.4`: `compatibility-manifest.json` now records `tested_bering_app_versions: ["v0.3.4"]`; schema contract pins are unchanged.
 - The next highest-priority repo task is **R9.2: add a debugging toolkit for common contract, path, and policy failures**.

internal/release/compatibility.go

@@ -22,6 +22,7 @@ const (
 	DefaultReleaseSchemaPath            = "api/schema/release-manifest.schema.json"
 	DefaultConfigPackSourceListPath     = "release/packs/default-config-pack.files.txt"
 	DefaultConfigPackMetadataOutputPath = "dist/default-config-pack.json"
+	CurrentTestedBeringAppVersion       = "v0.3.4"
 )
 
 type CompatibilityContract struct {
@@ -98,10 +99,14 @@ func GenerateCompatibilityManifest() CompatibilityManifest {
 		SupportedUpstreamSchemaNames:    schemaNames,
 		SupportedUpstreamSchemaVersions: schemaVersions,
 		SupportedContracts:              supportedContracts,
-		TestedBeringAppVersions:         []string{},
+		TestedBeringAppVersions:         TestedBeringAppVersions(),
 	}
 }
 
+func TestedBeringAppVersions() []string {
+	return []string{CurrentTestedBeringAppVersion}
+}
+
 func (m CompatibilityManifest) Validate() error {
 	if m.SchemaVersion != CompatibilityManifestSchemaVersion {
 		return fmt.Errorf("compatibility manifest schema_version must be %q", CompatibilityManifestSchemaVersion)