Anthony Ettinger 3d155af970 vault + teams: filter secrets by category, export to CSV, simpler help (#195) ... Every secret now has a category derived from its name (db, social, server, api, cloud, finance, crypto, ai, email, messaging, storage, dns, analytics, devtools, auth, config, other). One rule table in @logicsrc/opencreds serves both vaults; services win over generic words, so STRIPE_WEBHOOK_SECRET is finance, not auth. Checked against the 1,208 distinct key names in the profullstack team: 74 fall to "other". Team vaults (where the shared .env secrets live): - teams categories [team] the filter words, with per-category counts - teams secrets <team> [project] [env] --category/-c --search/-s names + categories, never decrypts; --format csv - teams export <team> [project] [env] --category -o file.csv [--yes] decrypts into team,project,env,category,key, value,updated_at (0600); skips vaults without a grant and names them Personal vault (OpenCreds): - vault list --category, and the category column in list output - vault export --format csv: one flat row per item, keeps key/account secrets that a Bitwarden CSV drops; --category on every export format DX: - examples in `logicsrc vault help` / -h / --help that start by saying which of the two vaults you want, plus examples on teams and each subcommand - password prompts go to stderr, so eval "$(logicsrc vault unlock)" works - hints name the command you actually ran (logicsrc vault init, not opencreds init) Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>		2026-09-23 21:08:08 -07:00
..
src	vault + teams: filter secrets by category, export to CSV, simpler help (#195)	2026-09-23 21:08:08 -07:00
package.json	OpenFleet reference implementation: @logicsrc/openfleet, logicsrc fleet, and Claude Code hooks (#185)	2026-09-13 10:58:55 +00:00
tsconfig.json