mirror of
https://github.com/JackChen-me/open-multi-agent.git
synced 2026-10-22 11:02:59 -05:00
Jack Chen
676dea125b
* ci(release-smoke): verify the published OTel adapter against the released core @open-multi-agent/otel rides its own version track and carries no git tag, so the post-publish smoke test covered core and create-oma-app but never otel. Add an otel-consumer job that reads the otel version from the release commit, installs it alongside the released core in a clean consumer, asserts npm resolved the core we just published rather than quietly falling back to an older one the dependency range still allows, and exports a span through createOtelTraceSink. When otel did not change in a release, its version is already live from an earlier one and the job still proves the pairing holds against the new core. * docs(release): document the three-package release process The repository publishes three packages with independent version tracks, a fixed publish order, and template pins that must move with the core version. None of that was written down, so it had to be reconstructed from package manifests, git tags, and the workflows each time. Record what ships, the ordered steps and why each depends on the previous one, what a release commit must contain, and what CI proves before merge versus what release-smoke proves after publish. * docs(agents): sharpen the architecture map and link the release guide Replace the per-area entry point table with the directory layout plus the published export surface, which stays accurate as subsystems move. Mark the subsystem documentation table as a curated selection rather than a complete index of docs/, and add the routing, scheduling, consensus, recovery, and replay docs to it. Link the new release guide, and add the Claude Code shim next to the existing packages/create-oma-app/AGENTS.md so package-level rules load there the same way they do at the repository root.