What

Reconcile this epic with the actual ecosystem state. As of 2026-05-09, the v1.0 release-prep epics for six dependency libraries are CLOSED, while two top-tier epics remain OPEN:

The epic body still says "All 8 repositories at version 0.x.x — no API stability guarantees", which contradicts the closed dependency epics. Either the dependencies actually shipped v1.0 (making the body stale) or the epics were closed prematurely (making the dependency claims stale).

Part of #639.

Why

• An OPEN tracking epic with a stale body misleads consumers and contributors about ecosystem readiness.
• network_system #964 and pacs_system #1095 are still OPEN — their dependencies show CLOSED, so we cannot tell from issue state alone whether the dependencies are actually shippable.
• This mismatch needs a single audit pass to either update Track ecosystem-wide v1.0 API stabilization readiness #639 to current reality, reopen prematurely-closed dependency epics, or close Track ecosystem-wide v1.0 API stabilization readiness #639 itself if the work has effectively wrapped up.

Where

• This issue (Track ecosystem-wide v1.0 API stabilization readiness #639)
• Each ecosystem repository's tags and releases page
• Each repository's CHANGELOG.md and version macros (e.g. *_VERSION_MAJOR)

How

Approach

1. For each of the 8 repositories, look up the latest release tag (gh release list --repo <repo>) and the version macro in source.
2. Build a state matrix: epic state vs. tag state vs. version macro vs. CHANGELOG.
3. Decide for each row: (a) v1.0 actually shipped — update Track ecosystem-wide v1.0 API stabilization readiness #639 body and remove from "blockers"; (b) epic closed prematurely — reopen with a stale-state explanation; (c) v1.0 in progress under a different epic — link the active epic.
4. Update Track ecosystem-wide v1.0 API stabilization readiness #639's body and version table to reflect reality. Close Track ecosystem-wide v1.0 API stabilization readiness #639 if the only remaining open epics (#964, #1095) fully subsume the ecosystem-wide tracking.

Acceptance Criteria

• State matrix committed as a comment on this sub-issue (8 rows: epic, tag, macro, CHANGELOG)
• Track ecosystem-wide v1.0 API stabilization readiness #639 body updated to reflect actual current state (or a justification for closing Track ecosystem-wide v1.0 API stabilization readiness #639 added)
• Any prematurely-closed dependency epic reopened with an explanation comment
• Decision recorded: keep Track ecosystem-wide v1.0 API stabilization readiness #639 OPEN with refreshed body, or close Track ecosystem-wide v1.0 API stabilization readiness #639 in favor of the per-repo epics