[Index] Delivery status and active backlog

[a-a-k]

Purpose

Pinned delivery index and active backlog source of truth for MB3R-Lab/Bering.

Current status

Synced on 2026-05-31 after shipping v0.3.4, publishing the release/package payload, and syncing downstream Sheaft to the new Bering app release.

• Latest product release: v0.3.4
• Product release commit: 78beb48bd8c13d391d5a83583e889b88681cdb25
• Latest implementation commit on main: 78beb48bd8c13d391d5a83583e889b88681cdb25
• Capability backlog commits: dec1c01, 179e94c
• Release prep commit: 78beb48
• Bering CI checkpoints:
  • CI run 26717221207 passed on main
  • Release dry-run 26717223851 passed on main
  • Release run 26717376967 passed for tag v0.3.4
• Downstream Sheaft sync: MB3R-Lab/Sheaft@64ea26a records tested_bering_app_versions: ["v0.3.4"]
• Sheaft CI checkpoints for the sync commit:
  • ci-template-smoke run 26717682013 passed
  • schema-contract run 26717682015 passed
  • release-dry-run run 26717682014 passed
• Completed backlog milestone: Post-v0.3.3 product capability backlog
• Preserved public schema contracts remain published and valid:
  • io.mb3r.bering.model@1.0.0
  • io.mb3r.bering.snapshot@1.0.0
• Current default public schema contracts:
  • io.mb3r.bering.model@1.1.0
  • io.mb3r.bering.snapshot@1.1.0
• Schema publishing tag remains separate: schema-v1.1.0
• Tracked backlog work lives in GitHub Issues and Milestones, not in checked-in planning files.

Release/package checkpoint

The published v0.3.4 release payload is the current package baseline.

• Release URL: https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.4
• Published at: 2026-05-31T16:04:30Z
• Release manifest asset: release-manifest.json (sha256:d7f4b3d61ff8e36bd370dadd351e51a2b2803677ae12a5e0fbb81faacfd01e20)
• Contracts pack asset: bering-contracts_0.3.4.tar.gz (sha256:3865a8e7152c8a383f34d99334bc392cfd0ec793325b530d392723f67839ddbf)
• Helm chart package asset: bering-0.3.4.tgz (sha256:86130a896f445a1b70b58ea4776a8a62a3e941dd76888ea8ac96cc1fed61ab60)
• Release checksums asset: release-checksums.txt (sha256:becfe40d94c4344775818192529b626fa7441ecbb2ba0ca97bc1479066945f45)
• OCI image: ghcr.io/mb3r-lab/bering:v0.3.4 (sha256:a825e7eb7d8a97610dd22cfea725e747e5b77f27663ed2972ac2978ee60d392d)
• OCI chart: ghcr.io/mb3r-lab/charts/bering:0.3.4 (sha256:0345b8908732b9bcf4a2982136e320eecb3158c0eea0684136e30760b4baeb19)

Closed milestones and major delivery tracks

• Milestone EPIC: [MVP] Bering bootstrap + delivery #1: MVP
• Milestone TASK: Repo scaffold (Go module + base layout + governance files) #2: Minor: Evidence-Weighted Reconciliation for Trace Gaps
• Milestone TASK: CI (lint/test/build) + Makefile + optional Dockerfile #3: Minor: Versioned Bering Schema Contract Evolution
• Milestone EPIC: [MVP] Canonical schema + contract validation #4: Post-v0.3.3 product capability backlog
• EPIC: [MVP] Bering bootstrap + delivery #1 EPIC: [MVP] Bering bootstrap + delivery
• EPIC: [MVP] Canonical schema + contract validation #4 EPIC: [MVP] Canonical schema + contract validation
• EPIC: [MVP] Trace connector + discovery core v0 #7 EPIC: [MVP] Trace connector + discovery core v0
• EPIC: [MVP] CLI discover + deterministic artifact + examples/docs #12 EPIC: [MVP] CLI discover + canonical deterministic artifact + examples/docs
• EPIC: Runtime discovery follow-ups #21 EPIC: Runtime discovery follow-ups
• Umbrella: evidence-weighted reconciliation for missing trace gaps #28 EPIC: Umbrella: evidence-weighted reconciliation for missing trace gaps
• EPIC: Versioned Bering schema contract evolution #36 EPIC: Versioned Bering schema contract evolution

Completed post-v0.3.3 capability backlog

1. #39 Signal quality and coverage report for every emitted artifact.
2. #40 Enrichment onboarding docs and examples for trace-only to overlay/topology_api upgrades.
3. #41 Operator-facing reconciliation summary.
4. #42 Reference non-trace adapter example built around the existing topology_api contract.

Active product capability backlog

No open implementation items are currently assigned. Open new GitHub issues and assign a milestone before starting the next backlog slice.

Maintenance rule

• Keep this issue pinned.
• Assign this issue to the active backlog milestone only while it has open tracked work.
• Update the current status, release/package checkpoint, and active backlog sections when concrete issues open or close.
• Do not duplicate active backlog lists into checked-in repository files.
• Use issues, milestones, ADRs, and docs for their distinct scopes.

[a-a-k]

Backlog audit as of 2026-03-11: repo state matches the index. Open implementation work remains #22 (OTLP/gRPC ingest) and #23 (first non-trace adapter). Based on current code shape, #22 is the next task in work because it extends the existing runtime ingest path with lower design risk than introducing a new non-trace source contract.

[a-a-k]

Backlog audit update: implementation work for #22 is complete locally and verified with go test ./..., but the issue remains open until the change is committed and merged. The only remaining unstarted implementation task after that is #23.

[a-a-k]

Backlog audit update: the two remaining implementation tasks, #22 and #23, are now both implemented locally and verified with go test ./.... The open backlog is now effectively merge/close-out work rather than new implementation scope.

[a-a-k]

Backlog actualized on 2026-03-14 after the public release cut. v0.1.0 is published, both public schema contracts are live on GitHub Pages, and there are currently no open implementation issues in the tracker.

[a-a-k]

Backlog update (2026-05-01): technical audit follow-ups completed on main.

Completed:

• 9fdb2b1 fix: publish artifacts with atomic writes - model/snapshot/runtime/reconciliation artifact writes no longer overwrite targets in place.
• 9103462 fix: harden runtime http timeouts - runtime HTTP server now has read-header/read/write/idle timeouts.
• b13d40b fix: update go toolchain and vulnerable deps - Go toolchain moved to 1.26.2, google.golang.org/grpc to 1.79.3, golang.org/x/net to 0.51.0.

Verification:

• go test ./...
• go vet ./...
• go run golang.org/x/vuln/cmd/govulncheck@latest ./... -> No vulnerabilities found.

Product backlog remains unchanged: #39 and #40 stay P0; #41 and #42 stay P1.

[a-a-k]

Release update (2026-05-01): Bering v0.3.2 is published.

Release: https://github.com/MB3R-Lab/Bering/releases/tag/v0.3.2
Release workflow: https://github.com/MB3R-Lab/Bering/actions/runs/25205309382

Published packages/artifacts verified:

• GitHub Release assets include binaries, SBOMs, contracts pack, chart metadata, OCI image metadata, release manifest, release notes, and checksums.
• OCI image ghcr.io/mb3r-lab/bering:v0.3.2 resolves to sha256:98e443461bf59d92cc19b20f425602de91b22a272ecd9a79df5cc20f96c735a8.
• OCI chart oci://ghcr.io/mb3r-lab/charts/bering --version 0.3.2 resolves to sha256:dc44313bf64467a4eadb71837cebc047fd4059633aa36ac4e01d84b487ebf50c.

The product capability backlog remains open as tracked above; this patch release closes the technical hardening slice only.