Found while building the MCP gateway (PR #349, #267).
Two related gaps in the path-based DB access:
- Building components have no `rux get` route. The real collections are `clouds, frames, labels, log, materials, meshes, panoramas, projects` — components are only reachable via `rux export csv`, which the MCP gateway now uses as a documented stopgap (`tools/rux-mcp/src/rux_mcp/components.py`).
- `rux get --help` is stale: it advertises `components` and `passports` as collections, but neither resolves (passports actually live under `materials`).
Fix: add a `components` router (`apps/rux/src/database/` — the 8 existing `*_router.cpp` files are the template, and since #249/#345 they are linkable from tests), and regenerate the help text from the actual router table so it cannot drift again.
category=CLI estimate=4h
🤖 Generated with Claude Code
Found while building the MCP gateway (PR #349, #267).
Two related gaps in the path-based DB access:
Fix: add a `components` router (`apps/rux/src/database/` — the 8 existing `*_router.cpp` files are the template, and since #249/#345 they are linkable from tests), and regenerate the help text from the actual router table so it cannot drift again.
category=CLI estimate=4h
🤖 Generated with Claude Code