Explore the console for the first time
fix(how-to): add dated Correction callouts to 20 of 28 how-to/ articles, worst ratio of any category — two systemic defects (wrong Doorman A/B/C tier semantics across 5 articles; fictional 4-tier pairing model + /v1/tokens API across 4 articles, real model is 3-role User/Admin/Interface via /v1/invite+/v1/pair), plus fictional CLI commands/routes across 11 more articles for fleet nodes, GIS API, exports, ledger reading, deployment, key rotation, and binary-download auth; several already-self-corrected articles independently re-confirmed accurate
@@ -48,6 +48,8 @@ The status bar at the top of the screen shows the system's current state at a gl - **SLM tier** — the Doorman tier in use: `A` (DataGraph live), `B` (SLM only), or `C` (local fallback) - **Session duration** — time since the console was launched **Correction (2026-08-02, verified against canonical `origin/main`):** two rows above don't match the real status bar (`app-console-keys/src/widgets/status_bar.rs`). (1) The real bar shows `username@tenant │ MBA LINK state │ active-slot │ elapsed [pending pairs]` — no `INPUT`/`USER`/`READ` auth-state field exists; the real pairing-role model is `User`/`Admin`/`Interface` (see [[pair-a-new-device]] for the full finding). (2) No SLM-tier field exists in the status bar at all, and real Tier A/B/C semantics are local model/Yo-Yo GPU burst/external API — DataGraph availability is a separate field. **Flagged, not resolved.** If the auth state reads `READ` and you expected `INPUT` or `USER`, the device has not completed the pairing sequence for the requested tier. See [[pair-a-new-device]] to resolve. ## Step 3: Navigate to the Doorman health slot