@zephytiju/juntai-usage-cost-ui
v1.0.1
Published
Cost & Usage-owned Console search and revision-detail destinations
Readme
Juntai Usage & Cost UI
Owning-service Console Micro-UI for Usage search/window detail and Cost-record search/detail. The browser uses only the public JuntaiUsageCostService read contracts; tenant identity and usage.read/cost.read authorization remain server-side.
Canonical Console routes:
/services/platform.cost-and-usage/usage/services/platform.cost-and-usage/usage/windows/{windowId}?revision={revision}/services/platform.cost-and-usage/cost/services/platform.cost-and-usage/cost/records/{recordId}?revision={revision}
The package is independently owned by this repository. It has no source,
build, test, or release dependency on JuntaiUsageCostService; protected reads
continue to use that service's public same-origin API contract.
Verification
npm ci
npm audit
npm run verifynpm run verify enforces the repository boundary, TypeScript contract,
behavior and accessibility suites, package allowlist, and an anonymous clean
consumer install that registers all four lazy routes. See
MIGRATION.md for source traceability.
Release
An immutable vX.Y.Z tag must exactly match package.json. The release
workflow verifies the tag is on main, re-runs every gate, packs the exact
tarball, publishes through npm trusted publishing when the version is absent,
and compares the public registry tarball byte-for-byte before recording the
GitHub release receipt.
Console SDK compatibility (1.0.1)
The supported Console SDK range is >=2.1.0 <=2.2.0. CI verifies both endpoint releases; all domain routes, generated client dependencies and behavior remain unchanged.
