Decisions

Architecture decision records: the reasoning behind the parts of this tool that look odd until you know why.

• 1. Security model — why the risk marker is on verbs and on output rather than on the query language.
• 2. Accounts and profiles — why credentials and organisations are separate entities, and why there is no use-context.
• 3. Output ladder — why the default view is terse, its field order fixed, and every list ends with a tally.
• 4. Own HTTP client — why the official client was dropped.
• 5. Rust and a Python wheel — why a compiled binary, and why it is still installable with uvx.
• 6. Agent surface — why the skill is split into small files instead of one large reference.
• 7. Yandex Wiki — why Wiki reads live behind this binary as one command group, and why its lists tally without a total.
• 8. Device sign-in — why login goes through a shared OAuth application whose secret ships inside the binary.