@carllee1983/dbcli 1.51.0 → 1.51.1

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "dbcli-agent",
-  "version": "1.51.0",
+  "version": "1.51.1",
   "description": "Database CLI skill and command reference for AI agents.",
   "contextFileName": "AGENTS.md"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@carllee1983/dbcli",
-  "version": "1.51.0",
+  "version": "1.51.1",
   "description": "Database CLI for AI agents",
   "type": "module",
   "publishConfig": {

package/plugins/dbcli-agent/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "dbcli-agent",
-  "version": "1.51.0",
+  "version": "1.51.1",
   "description": "Database CLI skill and command reference for AI agents",
   "author": {
     "name": "Carl Lee",

package/plugins/dbcli-agent/skills/dbcli/SKILL.md

@@ -82,6 +82,16 @@ warnings) go to stderr so stdout stays parseable — when piping JSON into a par
 use `2>/dev/null` or leave stderr alone. **Never `2>&1`**: it merges those lines back
 into stdout and the parse fails.
 
+**Business-language discovery:** When a user uses a business alias, metric, recurring
+term, or relationship/join intent instead of a physical table or field name, first run
+`dbcli skill context --format json`. If it includes `semantic`, treat that reviewed
+section as the governed vocabulary; use `dbcli semantic search <terms> --format json`
+to look up a specific term. If no semantic section exists or search returns no result,
+fall back to `blacklist` → `schema` mapping and tell the user that optional
+`dbcli.semantic.json` can make future requests consistent. Never create, update, or
+migrate that file without an explicit human request; semantic vocabulary never replaces
+schema confirmation or the normal query/write safety gates.
+
 ## Agent Task Packs
 
 When the user asks for a database workflow ("diagnose this slow query", "audit
@@ -552,7 +562,7 @@ schema. Raw `query` / `export` invocations render a sortable table only.
 - **Health / growth:** `check --all` (huge tables skipped unless `--include-large`); consult schema `sizeCategory` before ad-hoc queries.
 - **Codegen from live DB:** `schema --format json` to drive an ORM; cross-check once with `dbcli query`.
 - **Integration truth:** `query` before → run app → `query` after. Unit-test mocks are not a substitute.
-- **Natural language requests** (e.g. "update order to shipped"): pick `query` vs DML, map terms → columns via `schema` (and enum values in data), respect blacklist and `sizeCategory`, **always `--dry-run` writes first**.
+- **Natural language requests** (e.g. "update order to shipped"): follow **Business-language discovery** first when the request uses business terminology; then pick `query` vs DML, map terms → columns via `schema` (and enum values in data), respect blacklist and `sizeCategory`, **always `--dry-run` writes first**.
 
 ## Notes
 

package/plugins/dbcli-agent/skills/dbcli/reference.md

@@ -2197,6 +2197,14 @@ project root. It supplies business names and descriptions to an agent, but is
 not a query language: these commands are offline, read-only, and never execute
 SQL or contact an LLM.
 
+When an agent receives a business term, metric, alias, or relationship/join intent,
+it should first inspect `dbcli skill context --format json`. If that output includes
+`semantic`, use the reviewed vocabulary and use `semantic search <terms>` for a
+specific lookup. When the section is absent or search has no result, fall back to the
+blacklist-filtered schema and tell the user that `dbcli.semantic.json` is an optional
+way to make future terminology consistent. Do not create, update, or migrate the file
+without an explicit human request.
+
 ```bash
 dbcli semantic validate
 dbcli semantic validate --format json

package/skills/dbcli/SKILL.md

@@ -82,6 +82,16 @@ warnings) go to stderr so stdout stays parseable — when piping JSON into a par
 use `2>/dev/null` or leave stderr alone. **Never `2>&1`**: it merges those lines back
 into stdout and the parse fails.
 
+**Business-language discovery:** When a user uses a business alias, metric, recurring
+term, or relationship/join intent instead of a physical table or field name, first run
+`dbcli skill context --format json`. If it includes `semantic`, treat that reviewed
+section as the governed vocabulary; use `dbcli semantic search <terms> --format json`
+to look up a specific term. If no semantic section exists or search returns no result,
+fall back to `blacklist` → `schema` mapping and tell the user that optional
+`dbcli.semantic.json` can make future requests consistent. Never create, update, or
+migrate that file without an explicit human request; semantic vocabulary never replaces
+schema confirmation or the normal query/write safety gates.
+
 ## Agent Task Packs
 
 When the user asks for a database workflow ("diagnose this slow query", "audit
@@ -552,7 +562,7 @@ schema. Raw `query` / `export` invocations render a sortable table only.
 - **Health / growth:** `check --all` (huge tables skipped unless `--include-large`); consult schema `sizeCategory` before ad-hoc queries.
 - **Codegen from live DB:** `schema --format json` to drive an ORM; cross-check once with `dbcli query`.
 - **Integration truth:** `query` before → run app → `query` after. Unit-test mocks are not a substitute.
-- **Natural language requests** (e.g. "update order to shipped"): pick `query` vs DML, map terms → columns via `schema` (and enum values in data), respect blacklist and `sizeCategory`, **always `--dry-run` writes first**.
+- **Natural language requests** (e.g. "update order to shipped"): follow **Business-language discovery** first when the request uses business terminology; then pick `query` vs DML, map terms → columns via `schema` (and enum values in data), respect blacklist and `sizeCategory`, **always `--dry-run` writes first**.
 
 ## Notes
 

package/skills/dbcli/reference.md

@@ -2197,6 +2197,14 @@ project root. It supplies business names and descriptions to an agent, but is
 not a query language: these commands are offline, read-only, and never execute
 SQL or contact an LLM.
 
+When an agent receives a business term, metric, alias, or relationship/join intent,
+it should first inspect `dbcli skill context --format json`. If that output includes
+`semantic`, use the reviewed vocabulary and use `semantic search <terms>` for a
+specific lookup. When the section is absent or search has no result, fall back to the
+blacklist-filtered schema and tell the user that `dbcli.semantic.json` is an optional
+way to make future terminology consistent. Do not create, update, or migrate the file
+without an explicit human request.
+
 ```bash
 dbcli semantic validate
 dbcli semantic validate --format json