Ver mi cuenta

Owner (principal) account exposure — backoffice-legacy-parity Increment 4. Guard: only populated when the owner relation is explicitly eager-loaded (UserController::index/getUserDetails via ->with('owner:id,name,email')). Consumers that don't eager-load it (e.g. /me, front/account) always get null here — the resource NEVER lazy-loads the relation itself, so no N+1 is possible regardless of caller.

Effective feature versions — beta-program-catalog-membership. Map of feature_key => bool (true = effective version is beta), resolved via VersionCheckService::isUserMigratedBatch() precedence (own row -> owner row -> catalog default_version, same as isUserMigrated() per feature, batched — see that method's docblock for the query-budget rationale). Unlike feature_versions above, this is not gated by whenLoaded — the service performs its own cached lookup rather than relying on an eager-loaded relation. Lets agents (read-only) see the version they inherit from their owner without exposing the admin-gated catalog endpoints. Scoped to the GET /me and GET /user(+/v1 alias) endpoints — the two self-serialization routes that need it per design.md D11 — rather than computed unconditionally on every UserResource serialization. Admin/agent LIST endpoints (GET /users, GET /users/agents) also render via UserResource; computing this per row there would still cost extra queries with no caching benefit across distinct users, confirmed empirically to blow the pre-existing /users N+1 smoke-test budget (35 queries) even for a single self-referencing admin row inside the list. Path-gating avoids paying that cost anywhere it isn't needed.

workspaces-and-roles Inc 2 (design.md D2, tasks.md 2.8). Same path-gating as effective_feature_versions above (GET /me, GET /user only) to avoid an extra per-row cache lookup on list endpoints (GET /users, GET /users/agents) that also serialize via UserResource.

Progreso de uso del panel. Va con whenLoaded para que la lista del backoffice no dispare una consulta por fila: sin el eager load la clave no aparece, en vez de aparecer con un cero inventado.

Dormant state — billing-dormant-account. Resolution order:

1. subscriptions relation is loaded (AuthController, /me route) → filter in PHP.
2. dormant_row side-channel set by UserController::getUserDetails() → back-compat.
3. Neither loaded → defaults to false / null.

Dormant provider + eligibility — dormant-hotmart-support D6. dormant_provider is always resolvable (plain column read); it mirrors the same binary criterion BillingDormantService uses to branch dormant.

Hotmart -> Stripe migration saved without a linked subscription (plan-change-full-mac-grant-and-stripe-migration-close, D6). The boolean is harmless everywhere; the reason code is only emitted to admins (backoffice).

MAC enforcement fields — mac-rollover-and-admin Inc 5. mac_enforcement_enabled: cast to bool so null (pre-migration) renders as false. available_mac_buckets_sum: single extra query; acceptable on /me (single user).