graphjin 3.19.0 → 3.19.2

package/README.md

@@ -271,7 +271,7 @@ graphjin mcp add claude http://localhost:8080
 
 1. **Connects to database** - Reads your schema automatically
 2. **Discovers relationships** - Foreign keys become navigable joins
-3. **Exposes metadata** - `gj_*` tables make discovered databases, tables, columns, relationships, functions, and indexes queryable when the GraphJin source is enabled
+3. **Exposes metadata** - Built-in `gj_*` tables make discovered databases, tables, columns, relationships, functions, and indexes queryable when their feature capabilities are enabled
 4. **Indexes source code** - CodeSQL turns tree-sitter syntax trees and database references into a managed SQLite database
 5. **Exposes MCP tools** - Teach any LLM the query syntax
 6. **Runs JS workflows** - Chain multiple GraphJin MCP tools in one reusable workflow
@@ -286,20 +286,16 @@ CodeSQL is a managed source kind for source trees. Configure a source folder and
 ```yaml
 sources:
   - name: app
-    kind: sql
+    kind: database
     type: postgres
     connection_string: postgres://app:secret@db/app
     default: true
 
   - name: code
-    kind: codesql
+    kind: code
     path: /srv/app
     infer_db_refs: true
 
-  - name: graphjin
-    kind: graphjin
-    metadata: true
-
 tables:
   - name: users
     source: app
@@ -324,7 +320,7 @@ query {
 }
 ```
 
-With a `kind: graphjin` source, GraphJin creates a read-only system graph named `graphjin` by default. Schema, catalog, entrypoint, capability, workflow, and system metadata are catalog items in `gj_catalog`; table and column metadata are selected by `kind`. When one CodeSQL source is active, GraphJin links catalog items to code references automatically:
+GraphJin's built-in catalog creates `gj_catalog` according to the deployment-mode defaults; no source entry is required. Schema, catalog, entrypoint, capability, workflow, and system metadata are catalog items; table and column metadata are selected by `kind`. When one CodeSQL source is active, GraphJin links catalog items to code references automatically:
 
 ```graphql
 query {
@@ -579,7 +575,7 @@ GraphJin exposes a catalog-first MCP surface that guides AI models to discover b
 - Act through governed GraphQL roots such as `gj_workflow_execution(insert)`, `gj_workflow(insert/update/delete)`, and `gj_config(id: "current", update: ...)` only when policy exposes them.
 - In source mode, `gj_config` writes must run `mode: "preview"` with `expected_catalog_revision`, then resend the exact same payload with `mode: "apply"` and `preview_id`.
 - Source access and GraphJin root changes should use `source_patches` by exact source name instead of rewriting the full `sources` array.
-- Watches are managed through `gj_watch` / `gj_watch_event` and REST wrappers (`/api/v1/watches`, `/api/v1/watch-events/unseen`). MCP clients can subscribe to `graphjin://watch-events/unseen` for caller-scoped unseen-event notifications; unsubscribing does not pause or delete durable watches.
+- Watches are managed through the unified `gj_watch` lifecycle/review root plus the `gj_watch_event` inbox and REST wrappers (`/api/v1/watches`, `/api/v1/watch-events/unseen`). A deterministic notification is a plain watch; semantic or noisy triage adds inline, tool-free AxFlow in `enrich_json`; only an explicitly requested autonomous action adds workflow/webhook delivery. Review a flow with `flow_review_json` and its `flow_hash`, or a proposed action with `action_review_json` and its `action_hash`. Flow failures deliver the raw notification but never execute autonomous delivery. MCP clients can subscribe to the aggregate `graphjin://watch-events/unseen` resource or the per-watch `graphjin://watch-events/unseen/{watch_id}` template; exact subscriptions keep independent conversations from waking for each other's watches. Unsubscribing does not pause or delete durable watches.
 - Use `/api/v1/watches/cleanup-preview` before `/api/v1/watches/cleanup-apply`. Expired ephemeral watches can be expired automatically, but durable watch deletion is always explicit.
 - Legacy discovery tools are migration shims and are disabled unless `mcp.legacy_discovery: true`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "graphjin",
-  "version": "3.19.0",
+  "version": "3.19.2",
   "description": "GraphJin — one governed graph for AI agents: GraphQL + MCP over your databases, files, APIs, and code",
   "bin": {
     "graphjin": "bin/graphjin.js"