@trillioncore/cli 1.0.0-next.2 → 1.0.0-next.3

package/README.md

@@ -51,6 +51,8 @@ MCP uses the same `index` tool with that `path` and `resources: true`. Resource
 
 The catalog describes stored content kinds or approved **active synchronized** PostgreSQL relations, supported operations, schema metadata and known sync timestamps. Resource keys identify catalog entries; they are **not** refs accepted by `get`. Obtain a record ref through normal index/search before reading. Search is lexical across authorized connections, not scoped to the resource just inspected; optional source-type filters do not identify a unique connection.
 
+For native content, `recordSchemas` describes the allowed scalar fields in `get`'s `attributes`, grouped by recognized observed record kind. These field names/types come from the same definitions used to validate stored records. Fields may be absent on individual records; a schema does not prove populated values, complete history, relationship IDs, or SQL support. Empty connections return no observed schemas; unknown kinds remain listed without invented definitions. Table resources retain their separate `relation.columns` metadata.
+
 Respect `operations[].available` and `warnings`. Production synced SQL is currently not wired, so its schemas can be discovered but SQL is explicitly unavailable with `synced_sql_not_configured`. Live PostgreSQL resources are outside this catalog's coverage. No semantic search or actions are advertised. Native connectors retain search/get capabilities when empty; `recordKinds` lists only observed kinds (capped at 100 with an explicit warning). Synced manifests use existing limits of 25 tables/1,000 columns. A successful sync timestamp does not establish complete history or current provider state. Business definitions, currency and attribution are not inferred.
 
 All discovery uses the same organization, live token scope, connection permission and enabled-state checks as existing agent reads. Multiple internal adapters may eventually fulfill a connection's capabilities; this catalog does not introduce a separate user-visible integration for each adapter.

package/dist/index.js

@@ -3856,6 +3856,10 @@ function renderIndex(result) {
       ...catalog.resources.flatMap((resource) => [
         `${resource.name} (${resource.kind})`,
         ...resource.recordKinds ? [`  Observed record kinds: ${resource.recordKinds.join(", ") || "none"}`] : [],
+        ...resource.recordSchemas?.flatMap((schema) => [
+          `  Record attributes: ${schema.kind} (fields may be absent)`,
+          ...schema.fields.map((field) => `    ${field.name}: ${field.type}`)
+        ]) ?? [],
         ...resource.operations.map((operation) => `  ${operation.tool}${operation.target ? ` --target ${operation.target}` : ""}: ${operation.available ? "available" : `unavailable (${operation.reason})`}; scope: ${operation.scope}`),
         ...resource.relation ? [
           `  SQL relation: ${resource.relation.name}; connection: ${catalog.integrationAccountId}`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trillioncore/cli",
-  "version": "1.0.0-next.2",
+  "version": "1.0.0-next.3",
   "description": "Trillioncore v1 CLI: sign in and read your authorized integration records",
   "type": "module",
   "license": "MIT",