Repository navigation
Define console account and operator dashboard API contracts #215
Description
Activity
- added
on Sep 25, 2026 - added 9 commits that reference this issue
on Oct 5, 2026 Completed through #380, #407 and console MR !10, merged as
a94f286c4cf41f501ee613da7bab8257e34ce761.- Authenticated roles and economic capabilities drive available payment actions. Usage & orders shows authoritative TEST grants, reservations, consumption and remaining allowance, plus cursor-paginated intent history and run links. Exact TEST and USDC units remain distinct; unavailable or disabled data is never displayed as a zero balance.
- Owned-node inventory reports connection and dispatcher admission separately. Host drain is explicitly unavailable under the current protocol: offline or dispatcher maintenance does not mean drained. The console preserves local host maintenance instructions.
- Owners can inspect recorded earnings and up to 100 recent payout/refund transfers, preserving pending, confirmed and unknown states. Backend tests reject another account's inventory/earnings access. Disabled payouts expose no actionable payout flow; this change adds no account top-up or payout request action.
The UI-facing contracts and acceptance criteria are covered. Core main CI passed all 16 jobs, including ownership and accounting tests. Console candidate 517273 and merged main 517278 passed both automated jobs, including 88 frontend tests, lint and build; the tested and merged trees match. Deployment remains manual and unrun. Monetary activation, production payments and deployed login verification are not claimed by this closure.
The mockup contains a user balance/add-credit flow and an operator view with owned nodes, earnings and payout history. The inspected user response is ID/name; the balance route is commented out and there are no operator dashboard routes. These screens should not be populated with invented balances or unrestricted operator actions.
Proposed scope:
Acceptance: ordinary users cannot view another operator's data; disabled monetary settlement exposes no actionable payout flow; all displayed amounts reconcile to backend records and distinguish pending from settled.
This issue defines the UI-facing read/action contracts, not a duplicate implementation of the underlying ledgers or payout engine. Coordinate with #83 (non-monetary credits), #80 (payout reconciliation), #78 (earnings consistency), #87 (monetary activation) and #10 (console integration).
Evidence: source inspection of routes.go and api_models.go during the companion console redesign. No new runtime backend defect is claimed.