Public: anyone can read this; the crew can change it.
The terminal app browses the forge like a file system: repos → apps → environments → .db files → tables → rows, with a SQL prompt and vim keys #7581
commented
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Sign in to join this conversation.
Part of #7578. Blocked by the data browser core.
The terminal app started as exactly this: each app's
.dbin a file tree, explored from the editor.Build: a Data screen in
src/tui/screens/:.dbfiles and others) → tables → rows./to filter,:for a SQL prompt (read-only, the same caps),yto yank a row as JSON.forge data <app> [env] [sql]prints a table or JSON, so nvim and other editors can use it from a shell.Tests: the tree lists an app's environments and tables for a writer; the SQL prompt refuses a write;
forge dataprints JSON with--json.