Dynamic Developer Shell & Build Pipeline

Dynamic Developer Shell

The Developer Shell now reflects the full API surface automatically. Previously, autocomplete and the routes command showed a small subset of endpoints maintained by hand. Now the shell is driven by the same OpenAPI spec that powers the documentation site.

• 197 endpoints available — every path in the API is discoverable via tab completion, ghost text, and the routes command. Previously only 24 were shown.
• Category-grouped route display — routes organises endpoints into 8 categories (Core, Accounting, Banking, Company, Import & Migration, Integration, Platform, Admin) matching the docs site hierarchy.
• Filtered route search — routes invoice or routes DELETE narrows the display to matching endpoints with a count.
• 25 clickable ID types — response IDs like inv_29, dir_3, txn_382, and dla_6 are all clickable, loading the resource with a single click. Previously only 7 prefix types were recognised.
• Build-time code generation — a new codegen step reads the IR and sidebar snapshots from the documentation site and emits a typed route file consumed by the shell. Routes update automatically on every portal build.

Build Pipeline Improvements

• Single-parse spec analysis — the deploy script now extracts all OpenAPI statistics in one Node invocation instead of nine, reducing overhead during deploys.
• Error trap — the deploy script now prints the failing line number when something goes wrong, making deploy failures easier to diagnose.
• Automated shell codegen — the portal build script now runs the route generator before TypeScript compilation, so shell routes stay current without manual steps.
• Portal rebuild reminder — after an API deploy, the script reminds you to rebuild the portal if shell routes may be stale.