[spec-parity] accounts: reach parity (3 req) #208

Closed
opened 2026-07-15 13:43:05 +00:00 by stephen · 1 comment
Owner

fj does not yet satisfy 3 requirement(s) of the accounts capability in the fjord-client-spec. Closing them keeps this client in sync with the spec.

Spec: https://rasterhub.com/rasterstate/fjord-client-spec/src/branch/main/openspec/specs/accounts/spec.md

Requirements to reach parity (3):

  • Organize accounts into user-named groups
  • Preserve the account selection across a session-expiry sign-out
  • Restore the previously-picked instance after re-authentication

Each requirement's SHALL statement and WHEN/THEN scenarios are in the linked spec. Derived from the per-requirement Parity: lines; see fjord-client-spec PARITY-GAPS.md.

`fj` does not yet satisfy 3 requirement(s) of the **`accounts`** capability in the [fjord-client-spec](https://rasterhub.com/rasterstate/fjord-client-spec). Closing them keeps this client in sync with the spec. **Spec:** https://rasterhub.com/rasterstate/fjord-client-spec/src/branch/main/openspec/specs/accounts/spec.md **Requirements to reach parity (3):** - Organize accounts into user-named groups - Preserve the account selection across a session-expiry sign-out - Restore the previously-picked instance after re-authentication Each requirement's SHALL statement and WHEN/THEN scenarios are in the linked spec. Derived from the per-requirement `Parity:` lines; see fjord-client-spec `PARITY-GAPS.md`.
Author
Owner

Shipped in v0.6.0. fj auth group keeps user-named groups, and a Fjord Account re-login checks the remembered instance against a fresh listing, keeping it when present and ready and otherwise printing the ready instances with the fj instances use <id> hint. The fjord-client-spec status review records all three requirements as met for a CLI.

Shipped in v0.6.0. `fj auth group` keeps user-named groups, and a Fjord Account re-login checks the remembered instance against a fresh listing, keeping it when present and ready and otherwise printing the ready instances with the `fj instances use <id>` hint. The fjord-client-spec status review records all three requirements as met for a CLI.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rasterstate/fj#208
No description provided.