Repository navigation
Description
Operators cannot determine which open native runs still depend on a legacy version branch. Per-run VersionMarkerRecorded history is available, but no namespace-scoped counts and fleet query expose it.
This is the native Server slice of accepted organization #220, using General's three-state decision. Workflow owns the shared contract and embedded implementation; Server owns the equivalent native endpoint/query and its regression coverage.
Required outcome:
- Implement the shared read-only interface for one namespace, workflow type, change point and agreed version boundary. Return authoritative legacy/current/unknown counts and the paged run list.
- Include only open runs. Missing markers and unavailable history/provenance remain unknown, never zero legacy use or permission to remove a branch.
- Preserve exact marker identity, tenant isolation, consistent counts and deterministic pagination across supported native backends.
- Cover legacy/current/missing markers, closed runs, unavailable provenance, validation, namespace isolation, count/filter behavior and stable pages with real API/query regressions.
- Document the native interface in the control-plane specification. Obtain normal exact-head source/Security/CI and accepted-main evidence. Published endpoint qualification and CLI/Waterline/guide adoption remain separately attributable outcomes before organization-wide delivery.
Use existing retained rows/history; this work does not change marker production, persistence/schema, worker protocol or definition-authoring admission. No #980 collector/clock/promotion path, #1204 replay or release action is selected. General retains the cross-repository handoff. This issue stays finite and open until its stated native outcome is evidenced.
Activity
rmcdaniel commentedon Nov 14, 2026
The native implementation follows Workflow's immutable v1 contract at 60c42603 and response schema. Transport is
GET /api/workflows/version-usage, discovered through literalcapabilities.workflow_version_usage=trueon/api/cluster/info. Missing/false capability is unsupported, not an empty result. Published 3.10/3.11 do not claim this new capability.Native namespace echo is always the selected namespace string, including
default. Invalid parameters or mismatched/malformed cursors use HTTP 422 withreason=validation_failedand the existing error arrays. Authentication/storage failures remain errors; 404/405 must not become zero counts. Query identity and all database predicates remain namespace-scoped and byte-exact. Counts and page share one read-only database snapshot; continuations retain the shared live keyset semantics and first-page upper ID.The source implementation and classifier/HTTP tests are in progress on
feat/server-220-version-usage; its first bounded source check is running. No published availability, producer/schema migration, installed consumer acceptance or #980/#1204 action is implied. The draft PR will carry the implementation and exact checks.rmcdaniel commentedon Nov 14, 2026
The native source implementation is integrated by #1221 at accepted main
c40707776ba0ae424985024d2ea341a6bdbe71c9. Its complete treecb7a571b399a141d97a0893cacdfa3a6b24dd14bequals reviewed/testede1729e222fd56e7d8b3181663969df76a49d38f9; normal merge parents are verified and the remote topic branch is absent.All 63 exact-head checks succeed, with one declared skip, including complete native/backend/corpus qualification, feature qualification, CodeQL and Sonar. Independent Security and shared-contract parity reviews pass. The queue accepted that same tree. Focused checks cover 17 reader/cursor unit cases and 12 HTTP cases on SQLite, MariaDB and PostgreSQL 17.
The collision-free
GET /api/workflow-version-usageroute andworkflow_version_usagecapability now implement the native legacy/current/unknown source contract. Unknown ownership/history remains counted; cursors are authenticated and namespace/query bound. The native guide describes the live counts and paging limits. The pinned shared description is byte-identical to the newly accepted Workflow main contract.This records source delivery. Published endpoint qualification and CLI/Waterline/guide adoption remain separately attributable outcomes under durable-workflow/.github#220; #1220 remains open for the published-runtime follow-through. No release or installed-consumer acceptance is claimed by this source merge.