Task: The IAM reference lookups: account type, tenant type and tenant status

Implement account_type, tenant_type and tenant_status. The three share one shape – a natural text key, a name, a description and a display order – so they are the first proof that three entities of a kind cost three declarations and no new code. Each is bound to the profile that renders its metadata, and each is listed, creatable, editable and deletable.

• All three appear in the IAM navigation with their screens.
• Each is one declaration; any new shared code this needed is recorded as a failure of the shell.
• Field groups, labels and columns come from the generated metadata, not from hand-written lists.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

Superseded on 2026-09-23. This task is a declaration per lookup that the shared shell renders, and both the declaration and the shell are deleted. The journeys the new story defines do not surface these three as screens of their own, because a person picks them inside another screen.