@c4a/context-cli 0.7.4 → 0.7.8

package/docs/context-debug-event-v1.schema.json

@@ -21,7 +21,9 @@
         "workflow.action-completed",
         "workflow.scope-opened",
         "workflow.scope-closed",
-        "workflow.stopped"
+        "workflow.stopped",
+        "performance.measurement",
+        "runtime.telemetry"
       ]
     },
     "invocation_id": { "type": "string", "minLength": 1 },

package/docs/debug-tracing.md

@@ -57,7 +57,15 @@ The event stream records:
 - managed workflow action start and completion with deterministic receipts;
 - execution-scope open and close events, including whether a deterministic
   action ran in-process or in a child process and whether every short-lived
-  resource was released;
+  resource was released; normal project write-lock open/close pairs are omitted,
+  while release failures remain visible;
+- performance measurements: errors and operations taking at least one second
+  are written immediately. Short successful operations inside a CLI invocation
+  are aggregated into `cli.completed.data.performance` by operation and relevant
+  cache/read mode (and requested operation for locks). Each total includes count,
+  summed duration, maximum duration, and summed counters. It excludes the slow/error
+  events already written individually; add those when computing an operation total.
+  Direct SDK calls outside a CLI invocation retain individual measurements;
 - the reason and graph position at which a managed loop stopped.
 
 `trace_id` groups the workspace-local debug history, `sequence` defines replay order,
@@ -72,6 +80,14 @@ resource ownership and cleanup observable without changing a Route or adding
 workspace state. Durable knowledge mutations are still audited through the
 normal action receipt, revision, close, and verify results.
 
+Performance summaries live only in command memory until normal or error completion;
+there is no background writer or extra persistent queue. Abruptly killed commands
+may lack their short-operation summary, but invocation, slow-operation and error
+events already written remain available. Summary groups are bounded; overflow
+measurements are recorded individually. Operation durations can be nested, so their
+sum is not total CLI wall time. In particular, write-lock hold time includes the
+protected operation; acquisition duration identifies lock contention.
+
 ## Inspect and export
 
 ```bash

package/indexers/bundles/context-code-indexer/SKILL.md

@@ -4,7 +4,7 @@ description: Context-managed Provider for source-grounded code knowledge. Use on
 metadata:
   context-role: "indexer-provider"
   context-public-entry: "false"
-  context-provider-version: "1.1.1"
+  context-provider-version: "1.2.1"
 ---
 
 # Context Code Indexer
@@ -44,4 +44,13 @@ storage boundaries, partition on those boundaries before authoring. Do not put
 the whole module in one catch-all logical unit, and do not replace semantic
 partitioning with numbered batches.
 
+When revising existing knowledge, start from the supplied current page and the
+confirmed reader purpose. Update changed API facts and parameter/type tables
+without replacing still-valid explanations or prior confirmed contributions.
+When code is unchanged, useful new context can be a local explanatory revision
+without partitioning the whole source again.
+Keep additions within the selected modules; identify newly public objects as
+well as changes to already documented ones. Recommend a retirement or move only
+for the affected content and explain the reader consequence.
+
 The machine-readable authority is `context-indexer.yaml`. Detailed authoring guidance is materialized by Context from the registered Bundle after its file ledger and integrity have been verified.