Skip to content

✨ Surface billing equivalences on the nav compute gauge #4349

Closed

Description

@PierreBrisorgueil

Surface the configured billing.equivalences on the sidenav compute gauge.

Problem

The nav compute gauge (billing.navComputeGauge.component.vue) shows only raw remaining compute units + reset date (hover: "{remaining} remaining · resets {date}"). Raw units are opaque — a user can't tell what that remaining capacity means in practice.

Goal

Surface billing.equivalences as a human-readable capacity estimate in operation terms — e.g. "~N easy / ~M hard operations remaining" — derived from the equivalence ratios: remaining_units × plan.easyPerPeriod ÷ quota (same for hard). Render via the existing-but-unused BillingEquivalencesChipsComponent (kinds: easy / hard / feature).

Scope (billing module Vue, display-only)

  • billing.navComputeGauge.component.vue — derive the easy/hard estimate from serverConfig.billing.equivalences + current meter remaining/quota.
  • Wire the orphaned billing.equivalencesChips.component.vue (currently 0 imports) to render it.
  • Config-driven → no-op when billing.equivalences is absent. No billing mechanism change (no meter/quota/reset logic touched).

Notes

  • Generic enhancement — benefits any downstream consumer that defines per-plan equivalences in its config.

Created via /dev:issue

Activity

  1. PierreBrisorgueil commented on Jun 18, 2026

    @PierreBrisorgueil
    CollaboratorAuthor

    Edge case for the estimate — one-shot / no-renewal plans. A plan may grant a one-shot total allowance with no per-period equivalence (its easyPerPeriod/hardPerPeriod are 0 / absent). The naive projection remaining × perPeriod ÷ quota then yields 0, which would render "0 easy / 0 hard operations" — wrong. For such plans the gauge estimate must derive from the total remaining grant (and label it as one-shot / no renewal) rather than a per-period ratio. Handle this generically so any plan shape renders a sensible estimate.

  2. PierreBrisorgueil commented on Jun 18, 2026

    @PierreBrisorgueil
    CollaboratorAuthor

    WIP — picking this up for implementation (2026-06-18T13:22Z).

  3. added a commit that references this issue on Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions