@c4a/context-cli 0.7.42 → 0.7.43

package/indexers/release-manifest.json

@@ -1,7 +1,7 @@
 {
   "protocol": "context.indexer.cli-release-manifest/v1",
   "package": "@c4a/context-cli",
-  "version": "0.7.42",
+  "version": "0.7.43",
   "issuer": "context4ai/context",
   "bundles": [
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.7.42",
+  "version": "0.7.43",
   "type": "module",
   "description": "Local runtime and Agent integration for traceable knowledge production",
   "license": "MIT",
@@ -24,17 +24,17 @@
   },
   "dependencies": {
     "@c4a/agent-graph": "0.3.0",
-    "@c4a/context": "0.7.42",
-    "@c4a/extract": "0.7.42",
-    "@c4a/extract-contract": "0.7.42",
-    "@c4a/extract-go": "0.7.42",
-    "@c4a/extract-mdx": "0.7.42",
-    "@c4a/extract-proto": "0.7.42",
-    "@c4a/extract-rush": "0.7.42",
-    "@c4a/extract-sql": "0.7.42",
-    "@c4a/extract-style": "0.7.42",
-    "@c4a/extract-thrift": "0.7.42",
-    "@c4a/extract-ts": "0.7.42",
+    "@c4a/context": "0.7.43",
+    "@c4a/extract": "0.7.43",
+    "@c4a/extract-contract": "0.7.43",
+    "@c4a/extract-go": "0.7.43",
+    "@c4a/extract-mdx": "0.7.43",
+    "@c4a/extract-proto": "0.7.43",
+    "@c4a/extract-rush": "0.7.43",
+    "@c4a/extract-sql": "0.7.43",
+    "@c4a/extract-style": "0.7.43",
+    "@c4a/extract-thrift": "0.7.43",
+    "@c4a/extract-ts": "0.7.43",
     "@mermaid-js/layout-elk": "0.2.0",
     "commander": "^11.0.0",
     "fast-xml-parser": "^5.10.1",

package/plugins/VERSION

@@ -1 +1 @@
-0.7.42
+0.7.43

package/plugins/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
-  "version": "0.7.42",
+  "version": "0.7.43",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/commands/context-inspect-search.md

@@ -128,6 +128,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -139,8 +151,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -148,8 +164,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

package/plugins/claude/skills/context-inspect-search/SKILL.md

@@ -127,6 +127,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -138,8 +150,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -147,8 +163,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

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

@@ -1,6 +1,6 @@
 {
   "name": "c4a",
-  "version": "0.7.42",
+  "version": "0.7.43",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": { "name": "c4a" },
   "homepage": "https://github.com/context4ai/c4a",
@@ -10,7 +10,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.42",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.7.43",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",

package/plugins/codex/skills/context-inspect-search/SKILL.md

@@ -127,6 +127,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -138,8 +150,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -147,8 +163,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "c4a",
   "displayName": "C4A Context",
-  "version": "0.7.42",
+  "version": "0.7.43",
   "description": "Start or continue a project-local knowledge workspace through one graph-routed entry.",
   "author": {
     "name": "Context4AI",

package/plugins/cursor/commands/c4a-context-inspect-search.md

@@ -126,6 +126,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -137,8 +149,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -146,8 +162,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

package/plugins/cursor/skills/context-inspect-search/SKILL.md

@@ -127,6 +127,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -138,8 +150,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -147,8 +163,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

package/plugins/skills/context-inspect-search/SKILL.md

@@ -127,6 +127,18 @@ matching sections with their conditions, not snippets alone. Batch known related
 reads within returned limits. Use the remote evidence checks below for knowledge
 as well as code, including per-item errors, truncation and coverage. A search
 miss is not evidence that the repository lacks the knowledge.
+When the connected schema supports it, use `output: "files"` only when locating
+paths is enough; use content excerpts when relevance needs context, bounding
+them with `max_lines_per_file` as needed. Do not add a mandatory file-list pass
+before every search. Omitted matches and truncation do not establish absence.
+If results are too broad, narrow by article path or a distinctive term before
+reading more output. For zero hits, simplify combined conditions using the
+service's documented syntax; do not assume unsupported OR/regex syntax worked.
+Follow the connected tool schema: use search-hit ranges when known; otherwise
+omit bounds if the service supplies a bounded default (currently up to 500 lines).
+For services requiring endpoints, supply `start_line` and `end_line` per item.
+Start with a bounded first window
+and follow continuation only when needed, not the whole file by default.
 
 Consume recorded evidence already attached to ordinary `read`/`read_many`
 responses; the repository plugin may be enabled by default. Do not reread just
@@ -138,8 +150,12 @@ This returns section sources with the original text; reuse them instead of
 separately looking up structure and registries. No plugin discovery/help call is
 required when the name and workspace are known. These are registered references,
 not verification that original sources were read. Keep original read errors and
-truncation checks; inspect extension `issues` only for affected evidence gaps.
-Source references may contain a ready commit-specific `url` instead of separate
+truncation checks; inspect appended diagnostics only for affected evidence gaps.
+Consume `references:` appended to each returned file. These may cover several
+sections in that read: not every reference supports every
+sentence. Narrow the read or inspect the source when attribution matters.
+References may be ready
+commit-specific URL strings or contain a `url` instead of separate
 repository/ref/path/line fields. Reuse it directly for that registered evidence;
 do not look up registries merely to reconstruct it. For necessary code reads,
 extract the exact repository, full commit, percent-decoded path and line range
@@ -147,8 +163,7 @@ from its recognized blob route into the existing MCP read fields. The service
 does not implicitly accept a URL as a read request. Do not guess unfamiliar URL
 formats; use targeted source metadata when needed. A URL is not proof of a read,
 and evidence read at another commit needs its own citation.
-For a scoped repository, consume `extensions["context-evidence"].scopes[].data`
-with its `root`: knowledge and snapshot paths are relative to that plugin root;
+For a scoped repository, knowledge and snapshot paths are relative to the plugin root;
 source-code reference paths already include their own source subpath. Do not
 prepend the knowledge scope to external source paths or repeat either prefix.
 If the service rejects the plugin option, retry the ordinary read once. If the

package/providers/context/manifest.json

@@ -2,7 +2,7 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.7.42"
+    "version": "0.7.43"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
@@ -575,7 +575,7 @@
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:4b4c916489f590345ccdd335da54b240b6fc2e167b2b737ea96128e754989ddd"
+      "digest": "sha256:cd82ed420353fd74fe01391c9d8d663cb6588b3784fe714e12c26354b98026e5"
     },
     {
       "path": "resources/contracts/indexer-provider-guide.yaml",
@@ -882,5 +882,5 @@
     "indexer": [],
     "workspace": []
   },
-  "digest": "sha256:40611844c18d3fb112f2d6b39ff9f7d892c92481b623875c38aa723eb4bacc3f"
+  "digest": "sha256:2ca382239eff90093bdce1927050d926e566d0c04847a259b4d1e1d60b402c0b"
 }

package/providers/context/provider.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.provider.v1
 id: c4a/context
-version: 0.7.42
+version: 0.7.43
 name: Context workflow
 description: Internal work contract for Context knowledge workspaces.
 graphs: