@c4a/context-cli 0.7.1 → 0.7.4

package/providers/context/provider.yaml

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

package/providers/context/resources/dialogue/human-gates.md

@@ -18,9 +18,9 @@ payload keys, and `source_ref` values exact.
 
 When two or three fixed choices exist, prefer the host's native choice UI. If
 none is available, present concise A/B/C choices with one impact sentence each.
-Labels must describe user outcomes, not SDK factories or internal route names.
-Do not start with raw TypeScript, placeholder commands, `alignProse`,
-`compileProse`, `reviewValidity`, `kbPackage`, or `llmsPackage`.
+Labels must describe user outcomes, not SDK factories, parser calls, schema
+names, or internal route names. Do not start with raw TypeScript or placeholder
+commands.
 
 An explicit fully managed request in the current conversation resolves only
 delegatable gates. Use the returned managed route without asking those

package/providers/context/resources/manuals/reference/package-templates.md

@@ -354,9 +354,8 @@ src-N#span:<heading-hint> L<start>-<end>@<span-hash>
 
 The code symbol form includes the source-relative file so same-name symbols in
 different files resolve to one exact symbol-index row. Consumers should still
-treat the complete `source_ref` as opaque. Production codeindex pages keep
-`candidate_fingerprint` at the top level and do not duplicate this evidence in
-`code_origin`.
+treat the complete `source_ref` as opaque. Production pages do not expose
+Candidate fingerprints, Indexer digests, or `code_origin`.
 
 `#span:` refs retain source snapshot line ranges for human review, diffing, and
 stable re-pinning. They resolve against committed file/lark document snapshots,