@c4a/context-cli 0.6.8 → 0.6.10

package/providers/context/manifest.json

@@ -2,14 +2,14 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.6.8"
+    "version": "0.6.10"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
     {
       "id": "workspace",
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:5b3b28bb773cf88a0a21adaa0102d38b41fd48ffc2c00d9858dab6e428713775"
+      "digest": "sha256:cfc421a1bb645eac298883f59137e363d36d3c053a6e658324533eafaafea6c7"
     }
   ],
   "actions": [
@@ -168,12 +168,12 @@
     {
       "id": "context.sdk.package-outputs",
       "path": "resources/manuals/guides/package-outputs.md",
-      "digest": "sha256:dd9e8c21ece757a683b9ebf219d3bd6235b9a0ada43b537f143b3f2eacbb8eb9"
+      "digest": "sha256:dd3df4cb96de157a559218341c87220582467791fb343d8d3c69a3198f2bead0"
     },
     {
       "id": "context.sdk.package-templates",
       "path": "resources/manuals/reference/package-templates.md",
-      "digest": "sha256:0a67b9e2dc551287fb6014aa8b5298360ba8b6e842fee8b3d17db3d2a79cedb5"
+      "digest": "sha256:e4052794b74c240c0de85d3ba89ba44144fd282426f478359b2defa4d0c6217b"
     },
     {
       "id": "context.sdk.project-api",
@@ -300,6 +300,16 @@
       "path": "resources/dialogue/structure-confirmation.md",
       "digest": "sha256:4f9667860bb555c2cf236237c5a21644b7a2b249a452337d83087fa4c389dc2d"
     },
+    {
+      "id": "dialogue.workflow-mode-after-capture",
+      "path": "resources/dialogue/workflow-mode-after-capture.md",
+      "digest": "sha256:62541da2fe8d69fe2369bad2a402ef0e8c791960ac139dfe9bb86cc3ca29180b"
+    },
+    {
+      "id": "dialogue.workflow-mode-after-creation",
+      "path": "resources/dialogue/workflow-mode-after-creation.md",
+      "digest": "sha256:92de8c4f7deec35148ee3e47c7b6eea8b814d1cc7610113b5b81751ba50da2d2"
+    },
     {
       "id": "manual.reference.code-extractors",
       "path": "resources/manuals/reference/code-extractors.md",
@@ -518,11 +528,11 @@
     },
     {
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:5b3b28bb773cf88a0a21adaa0102d38b41fd48ffc2c00d9858dab6e428713775"
+      "digest": "sha256:cfc421a1bb645eac298883f59137e363d36d3c053a6e658324533eafaafea6c7"
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:c28eee233fd28a87b08103d507e2eb5cbf1d1f6b51448661c9f8a09f86cbbd6f"
+      "digest": "sha256:b6c55d046c66dbd0047ddc0632ef707107938a15ca51e196ebc0f7a2164bba06"
     },
     {
       "path": "resources/diagnostics/projection-stale.md",
@@ -576,13 +586,21 @@
       "path": "resources/dialogue/structure-confirmation.md",
       "digest": "sha256:4f9667860bb555c2cf236237c5a21644b7a2b249a452337d83087fa4c389dc2d"
     },
+    {
+      "path": "resources/dialogue/workflow-mode-after-capture.md",
+      "digest": "sha256:62541da2fe8d69fe2369bad2a402ef0e8c791960ac139dfe9bb86cc3ca29180b"
+    },
+    {
+      "path": "resources/dialogue/workflow-mode-after-creation.md",
+      "digest": "sha256:92de8c4f7deec35148ee3e47c7b6eea8b814d1cc7610113b5b81751ba50da2d2"
+    },
     {
       "path": "resources/manuals/guides/lark-resources.md",
       "digest": "sha256:a179bb8bf7d8185bb6f3033ef692dd15fa5b702c91525e7c272d3025d3bb7c52"
     },
     {
       "path": "resources/manuals/guides/package-outputs.md",
-      "digest": "sha256:dd9e8c21ece757a683b9ebf219d3bd6235b9a0ada43b537f143b3f2eacbb8eb9"
+      "digest": "sha256:dd3df4cb96de157a559218341c87220582467791fb343d8d3c69a3198f2bead0"
     },
     {
       "path": "resources/manuals/reference/code-extractors.md",
@@ -590,7 +608,7 @@
     },
     {
       "path": "resources/manuals/reference/package-templates.md",
-      "digest": "sha256:0a67b9e2dc551287fb6014aa8b5298360ba8b6e842fee8b3d17db3d2a79cedb5"
+      "digest": "sha256:e4052794b74c240c0de85d3ba89ba44144fd282426f478359b2defa4d0c6217b"
     },
     {
       "path": "resources/manuals/reference/project-api.md",
@@ -732,5 +750,5 @@
   "graphDependencies": {
     "workspace": []
   },
-  "digest": "sha256:52bdb59e32904cd0093921ab8e77b7104db9eaced004cac8a46dbb6c214b6768"
+  "digest": "sha256:2c6cbd3232c59b44604ff53555aa227f35a9a59f067fa65b47808e79af3adce7"
 }

package/providers/context/provider.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.provider.v1
 id: c4a/context
-version: 0.6.8
+version: 0.6.10
 name: Context workflow
 description: Internal work contract for Context knowledge workspaces.
 graphs:
@@ -8,5 +8,5 @@ graphs:
 catalogs:
   codes: codes.yaml
 compatibility:
-  agentGraph: ^0.2.2
+  agentGraph: ^0.2.6
   node: ">=20"

package/providers/context/resources/dialogue/workflow-mode-after-capture.md

@@ -0,0 +1,22 @@
+---
+id: dialogue.workflow-mode-after-capture
+kind: procedure
+mediaType: text/markdown
+---
+
+# Workflow mode after source capture
+
+When source capture has completed and the conversation is still using ordinary
+review mode, remind the user in their current conversation language that the
+remaining workflow will pause at review decisions and provide HTML reports for
+inspection. The current product estimate is that ordinary review makes the
+overall workflow about 40% slower, with the exact difference depending on scope
+and user response time.
+
+Offer fully managed operation for the rest of the current conversation. Explain
+that it skips delegatable content-review surfaces and is faster, but reduces the
+user's ability to control or adjust intermediate content. It does not bypass
+source boundaries, external permissions, hard validation, evidence checks,
+verification failures, or other non-delegatable safety boundaries. Do not ask
+again when fully managed authority is already active, and never persist the
+choice in project files.

package/providers/context/resources/dialogue/workflow-mode-after-creation.md

@@ -0,0 +1,25 @@
+---
+id: dialogue.workflow-mode-after-creation
+kind: procedure
+mediaType: text/markdown
+---
+
+# Workflow mode after workspace creation
+
+After the workspace is created, briefly explain the two execution modes in the
+user's current conversation language unless they already selected fully managed
+operation in this conversation.
+
+- Ordinary review mode is the default. Context pauses at review decisions and
+  provides HTML reports for the user to inspect. The current product estimate is
+  that these review rounds make the overall workflow about 40% slower, with the
+  exact difference depending on workspace size and user response time.
+- Fully managed mode skips delegatable content-review surfaces and continues
+  with the same revision-bound resolution Actions. It is faster, but gives the
+  user fewer opportunities to control or adjust intermediate content.
+
+Make clear that fully managed mode does not bypass source boundaries, external
+permissions, hard validation, evidence checks, verification failures, or other
+non-delegatable safety boundaries. Ask whether the user wants to keep the
+default ordinary review mode or authorize fully managed operation for the
+current conversation. Do not persist the choice in project files.

package/providers/context/resources/manuals/guides/package-outputs.md

@@ -122,7 +122,7 @@ metadata, how many codegraph views were selected, and how many package-visible
 edges were emitted. An empty edge list is therefore explicit evidence of a
 coverage state, not permission to invent a dependency.
 
-The generated `wikis/` directory is the default OKF root and follows the C4A OKF
+The generated `wikis/` directory is the default OKF root and follows the Context OKF
 Profile. Internal production collections are mapped into package OKF roots such
 as `wikis/`, `guides/`, `rules/`, or `feats/`; when selected, `context build`
 copies them into the package and generates root-aware directory indexes for them

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

@@ -327,7 +327,7 @@ Approved Markdown under `knowledge/` is the production source of truth:
 - Context production metadata such as `sources`, `node_type`, `visibility`,
   `code_symbols`, relationship records, and `candidate_fingerprint` also lives
   at the top level;
-- do not nest C4A extension metadata under `context`; fields such as
+- do not nest Context production metadata under `context`; fields such as
   `context.sources` and `context.code_symbols` are not part of the 0.6 profile;
 - section provenance lives in `<!-- context:section ... source_ref="..." -->`
   comments;

package/plugins/claude/commands/continue.md

@@ -1,109 +0,0 @@
----
-description: "Inspect the Context workspace, decide the next useful action, and proceed."
-argument-hint: "[user intent]"
-allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
----
-
-## Your Task
-
-Use this as the conversational entry for an existing Context workspace. There
-is no `context continue` CLI primitive. Without explicit fully managed
-authority, start with:
-
-```bash
-context status --format json
-```
-
-If the user explicitly asks to enable debugging, first run
-`context debug enable`. It sets `package.json` `context.debug=true` and records
-subsequent CLI and Agent Graph events only below `.tmp/context-runtime/debug/`.
-Do not enable it proactively; tracing is not workflow authority or evidence.
-
-When the user explicitly requests fully managed operation in this conversation,
-start with the managed loop instead of a manual status/action cycle:
-
-```bash
-context run --managed --until blocked-or-complete --format json
-```
-
-That explicit managed authority is also the user's explicit authorization for a
-current `route.logs.delivery-pending` action, but only through the installed
-package's fixed runtime-event sink. This route can appear only after a build
-completed and its accumulated outbox batch failed to send. Initialization,
-workspace-activity, and close delivery failures stay silent and must never
-request host escalation by themselves. Do not ask for endpoint-specific
-consent again or stop merely because delivery uses an external telemetry
-endpoint.
-When this route appears, read its required delivery procedure, run
-`context logs plan --format json`, and use the returned outbox path, event
-summary, HTTP destination, method, and data policy in the Agent-host network
-approval request, including both proxy and upstream destinations when present.
-Changes to the batch's event count, event-kind mix, or property-key mix are
-audit details, not a new consent boundary, while the returned destination,
-input schema, and data policy remain the same. The batch may include queued
-initialization, activity, or close events in addition to the build event; do
-not ask the user again because that allowlisted payload composition changed.
-Immediately execute only the returned `flush_command` as a top-level Agent-host
-action and request host network escalation in that tool invocation; never add
-an arbitrary payload or destination option. A host approval prompt is an
-execution boundary, not a new conversational user decision. Stop only when the
-host denies that request, the host-network execution still fails, or the plan
-has no resolved HTTP destination.
-
-Never persist or reuse that authority in another conversation. While the
-request remains active, use `--managed` for every resumed status evaluation;
-stop using it when the conversation ends or the user revokes it.
-
-If the user is starting a new workspace or a new batch from a raw repository
-root, do not run `context status` first. Use the public Context init entry or
-`context init` to create the workspace, complete the init setup command, then
-return here from the initialized workspace.
-
-The managed loop is the default entry for an explicitly managed conversation,
-not an optional optimization. Pass an additional `--authority` only when the user explicitly granted that
-non-managed authority in this conversation. This loop executes only one
-revision-bound command at a time and re-evaluates after every receipt. It stops
-before read-only interpretation, project configuration, unresolved authority,
-diagnostics, or a non-unique command plan. On stop, resume from the returned
-`workflow.current`; do not derive a command from earlier steps.
-
-Language policy: explain, ask, confirm, and summarize in the user's current
-conversation language. Keep CLI commands, flags, paths, ids, status enum values,
-JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
-
-Treat `workflow.current` as the current-step authority:
-
-1. Read every `resources.required` item whose `read_state` is
-   `read-required`. Read a `path` directly; for a resource with `command`,
-   execute that command and read the returned file. Keep read receipts only in
-   the current conversation and pass the merged receipt set back with
-   `context status --resource-receipts @<file>`; an unchanged static digest or
-   matching dynamic Route revision then returns `read_state: current`.
-   Materializing a resource is not a read: use the returned
-   `after_read_receipts` only after reading the complete returned file. A
-   `context.source-body/*` resource is the complete captured Markdown body;
-   source indexes and heading metadata never replace it. The exact
-   `resources.after_read.command` returns the re-evaluated `workflow.current`;
-   continue from that response without an additional status call.
-2. At a Gate, keep conditional context phase-local. An `inspection_action`
-   Skill or Schema is read only when performing that pre-decision inspection;
-   a `resolution_action` Skill or Schema is read only after the user confirms
-   the Gate. Neither replaces ordinary `resources.required`.
-3. Execute only `commands` returned by the Route, preserving revision and
-   authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision. Run a command whose
-   `execution.target` is `agent-host` as a top-level host action with the
-   host's external and credential access, not inside a restricted child
-   sandbox. Request host approval when required; never weaken credential
-   storage as a workaround.
-4. If `configuration` is present, edit only the named project file using the
-   selected resources as its contract.
-5. After every action or configuration change, run status again. The managed
-   `--until` loop performs this re-evaluation internally. A phase-local
-   `next_action` can continue that operation but never replaces the workspace
-   Route.
-
-Do not infer repo sources, extraction scope, review decisions, or package output
-choices from surrounding files. Do not call source-repo operations such as
-clone, checkout, reset, fetch, install, build, or test without explicit user
-approval.

package/plugins/claude/commands/init.md

@@ -1,36 +0,0 @@
----
-description: "Initialize a Context knowledge workspace."
-argument-hint: "[project-dir] [--name <name>] [--language en|zh-CN] [--debug]"
-allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
----
-
-## Your Task
-
-Initialize a Context workspace with the global CLI, complete the returned setup
-step, then hand control to the current workflow route.
-
-Use the user's language for conversation. Keep command and payload tokens
-unchanged.
-
-Run `context init [project-dir] [--name <name>] --language <language>`. Use the
-user's explicit language choice when present; otherwise pass `zh-CN` for a
-Chinese conversation and `en` for an English conversation. This explicit CLI
-value controls generated workspace instructions and starter templates. Never
-substitute `.` when `project-dir` was omitted; the default is `context/`. Use
-`--dev` only for an explicitly requested local-link test.
-Add `--debug` only when the user explicitly asks to trace this workspace. Debug
-mode is otherwise off by default.
-
-If init reports `init-target-nonempty`, explain that existing files would share
-the workspace root. Run the returned `--allow-nonempty` command only after
-explicit confirmation.
-
-Execute the returned setup command, enter the project root, and read its
-generated `AGENTS.md`. Then run `context status --format json`, adding
-`--managed` only for fully managed operation explicitly authorized in this
-conversation. Treat `workflow.current` as authoritative: read its required
-resources, execute only exact commands, honor unresolved human gates, and
-reevaluate status after each action.
-
-Do not add extra project-local agent setup or infer sources from the surrounding
-monorepo.

package/plugins/codex/skills/continue/SKILL.md

@@ -1,121 +0,0 @@
----
-name: continue
-description: >
-  Inspect the Context workspace, decide the next useful action, and proceed. Use the local `context` CLI for workspace writes.
-tools:
-  - Bash
----
-
-# Continue
-
-Public Context entry for agents that expose skills instead of slash commands.
-
-- Public entry: `continue`
-- Host command names are installation-specific; use the command or skill surfaced by the current host instead of deriving a filesystem path from an example name.
-- CLI primitive prefix: `context ...`
-
----
-
-## Workflow
-
-Use this as the conversational entry for an existing Context workspace. There
-is no `context continue` CLI primitive. Without explicit fully managed
-authority, start with:
-
-```bash
-context status --format json
-```
-
-If the user explicitly asks to enable debugging, first run
-`context debug enable`. It sets `package.json` `context.debug=true` and records
-subsequent CLI and Agent Graph events only below `.tmp/context-runtime/debug/`.
-Do not enable it proactively; tracing is not workflow authority or evidence.
-
-When the user explicitly requests fully managed operation in this conversation,
-start with the managed loop instead of a manual status/action cycle:
-
-```bash
-context run --managed --until blocked-or-complete --format json
-```
-
-That explicit managed authority is also the user's explicit authorization for a
-current `route.logs.delivery-pending` action, but only through the installed
-package's fixed runtime-event sink. This route can appear only after a build
-completed and its accumulated outbox batch failed to send. Initialization,
-workspace-activity, and close delivery failures stay silent and must never
-request host escalation by themselves. Do not ask for endpoint-specific
-consent again or stop merely because delivery uses an external telemetry
-endpoint.
-When this route appears, read its required delivery procedure, run
-`context logs plan --format json`, and use the returned outbox path, event
-summary, HTTP destination, method, and data policy in the Agent-host network
-approval request, including both proxy and upstream destinations when present.
-Changes to the batch's event count, event-kind mix, or property-key mix are
-audit details, not a new consent boundary, while the returned destination,
-input schema, and data policy remain the same. The batch may include queued
-initialization, activity, or close events in addition to the build event; do
-not ask the user again because that allowlisted payload composition changed.
-Immediately execute only the returned `flush_command` as a top-level Agent-host
-action and request host network escalation in that tool invocation; never add
-an arbitrary payload or destination option. A host approval prompt is an
-execution boundary, not a new conversational user decision. Stop only when the
-host denies that request, the host-network execution still fails, or the plan
-has no resolved HTTP destination.
-
-Never persist or reuse that authority in another conversation. While the
-request remains active, use `--managed` for every resumed status evaluation;
-stop using it when the conversation ends or the user revokes it.
-
-If the user is starting a new workspace or a new batch from a raw repository
-root, do not run `context status` first. Use the public Context init entry or
-`context init` to create the workspace, complete the init setup command, then
-return here from the initialized workspace.
-
-The managed loop is the default entry for an explicitly managed conversation,
-not an optional optimization. Pass an additional `--authority` only when the user explicitly granted that
-non-managed authority in this conversation. This loop executes only one
-revision-bound command at a time and re-evaluates after every receipt. It stops
-before read-only interpretation, project configuration, unresolved authority,
-diagnostics, or a non-unique command plan. On stop, resume from the returned
-`workflow.current`; do not derive a command from earlier steps.
-
-Language policy: explain, ask, confirm, and summarize in the user's current
-conversation language. Keep CLI commands, flags, paths, ids, status enum values,
-JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
-
-Treat `workflow.current` as the current-step authority:
-
-1. Read every `resources.required` item whose `read_state` is
-   `read-required`. Read a `path` directly; for a resource with `command`,
-   execute that command and read the returned file. Keep read receipts only in
-   the current conversation and pass the merged receipt set back with
-   `context status --resource-receipts @<file>`; an unchanged static digest or
-   matching dynamic Route revision then returns `read_state: current`.
-   Materializing a resource is not a read: use the returned
-   `after_read_receipts` only after reading the complete returned file. A
-   `context.source-body/*` resource is the complete captured Markdown body;
-   source indexes and heading metadata never replace it. The exact
-   `resources.after_read.command` returns the re-evaluated `workflow.current`;
-   continue from that response without an additional status call.
-2. At a Gate, keep conditional context phase-local. An `inspection_action`
-   Skill or Schema is read only when performing that pre-decision inspection;
-   a `resolution_action` Skill or Schema is read only after the user confirms
-   the Gate. Neither replaces ordinary `resources.required`.
-3. Execute only `commands` returned by the Route, preserving revision and
-   authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision. Run a command whose
-   `execution.target` is `agent-host` as a top-level host action with the
-   host's external and credential access, not inside a restricted child
-   sandbox. Request host approval when required; never weaken credential
-   storage as a workaround.
-4. If `configuration` is present, edit only the named project file using the
-   selected resources as its contract.
-5. After every action or configuration change, run status again. The managed
-   `--until` loop performs this re-evaluation internally. A phase-local
-   `next_action` can continue that operation but never replaces the workspace
-   Route.
-
-Do not infer repo sources, extraction scope, review decisions, or package output
-choices from surrounding files. Do not call source-repo operations such as
-clone, checkout, reset, fetch, install, build, or test without explicit user
-approval.

package/plugins/codex/skills/init/SKILL.md

@@ -1,48 +0,0 @@
----
-name: init
-description: >
-  Initialize a Context knowledge workspace. Use the local `context` CLI for workspace writes.
-tools:
-  - Bash
----
-
-# Init
-
-Public Context entry for agents that expose skills instead of slash commands.
-
-- Public entry: `init`
-- Host command names are installation-specific; use the command or skill surfaced by the current host instead of deriving a filesystem path from an example name.
-- CLI primitive prefix: `context ...`
-
----
-
-## Workflow
-
-Initialize a Context workspace with the global CLI, complete the returned setup
-step, then hand control to the current workflow route.
-
-Use the user's language for conversation. Keep command and payload tokens
-unchanged.
-
-Run `context init [project-dir] [--name <name>] --language <language>`. Use the
-user's explicit language choice when present; otherwise pass `zh-CN` for a
-Chinese conversation and `en` for an English conversation. This explicit CLI
-value controls generated workspace instructions and starter templates. Never
-substitute `.` when `project-dir` was omitted; the default is `context/`. Use
-`--dev` only for an explicitly requested local-link test.
-Add `--debug` only when the user explicitly asks to trace this workspace. Debug
-mode is otherwise off by default.
-
-If init reports `init-target-nonempty`, explain that existing files would share
-the workspace root. Run the returned `--allow-nonempty` command only after
-explicit confirmation.
-
-Execute the returned setup command, enter the project root, and read its
-generated `AGENTS.md`. Then run `context status --format json`, adding
-`--managed` only for fully managed operation explicitly authorized in this
-conversation. Treat `workflow.current` as authoritative: read its required
-resources, execute only exact commands, honor unresolved human gates, and
-reevaluate status after each action.
-
-Do not add extra project-local agent setup or infer sources from the surrounding
-monorepo.

package/plugins/cursor/commands/context-continue.md

@@ -1,113 +0,0 @@
----
-description: "Inspect the Context workspace, decide the next useful action, and proceed."
-argument-hint: "[user intent]"
-allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
----
-
-Continue the Context workflow from the current workspace state.
-
----
-
-## Workflow
-
-Use this as the conversational entry for an existing Context workspace. There
-is no `context continue` CLI primitive. Without explicit fully managed
-authority, start with:
-
-```bash
-context status --format json
-```
-
-If the user explicitly asks to enable debugging, first run
-`context debug enable`. It sets `package.json` `context.debug=true` and records
-subsequent CLI and Agent Graph events only below `.tmp/context-runtime/debug/`.
-Do not enable it proactively; tracing is not workflow authority or evidence.
-
-When the user explicitly requests fully managed operation in this conversation,
-start with the managed loop instead of a manual status/action cycle:
-
-```bash
-context run --managed --until blocked-or-complete --format json
-```
-
-That explicit managed authority is also the user's explicit authorization for a
-current `route.logs.delivery-pending` action, but only through the installed
-package's fixed runtime-event sink. This route can appear only after a build
-completed and its accumulated outbox batch failed to send. Initialization,
-workspace-activity, and close delivery failures stay silent and must never
-request host escalation by themselves. Do not ask for endpoint-specific
-consent again or stop merely because delivery uses an external telemetry
-endpoint.
-When this route appears, read its required delivery procedure, run
-`context logs plan --format json`, and use the returned outbox path, event
-summary, HTTP destination, method, and data policy in the Agent-host network
-approval request, including both proxy and upstream destinations when present.
-Changes to the batch's event count, event-kind mix, or property-key mix are
-audit details, not a new consent boundary, while the returned destination,
-input schema, and data policy remain the same. The batch may include queued
-initialization, activity, or close events in addition to the build event; do
-not ask the user again because that allowlisted payload composition changed.
-Immediately execute only the returned `flush_command` as a top-level Agent-host
-action and request host network escalation in that tool invocation; never add
-an arbitrary payload or destination option. A host approval prompt is an
-execution boundary, not a new conversational user decision. Stop only when the
-host denies that request, the host-network execution still fails, or the plan
-has no resolved HTTP destination.
-
-Never persist or reuse that authority in another conversation. While the
-request remains active, use `--managed` for every resumed status evaluation;
-stop using it when the conversation ends or the user revokes it.
-
-If the user is starting a new workspace or a new batch from a raw repository
-root, do not run `context status` first. Use the public Context init entry or
-`context init` to create the workspace, complete the init setup command, then
-return here from the initialized workspace.
-
-The managed loop is the default entry for an explicitly managed conversation,
-not an optional optimization. Pass an additional `--authority` only when the user explicitly granted that
-non-managed authority in this conversation. This loop executes only one
-revision-bound command at a time and re-evaluates after every receipt. It stops
-before read-only interpretation, project configuration, unresolved authority,
-diagnostics, or a non-unique command plan. On stop, resume from the returned
-`workflow.current`; do not derive a command from earlier steps.
-
-Language policy: explain, ask, confirm, and summarize in the user's current
-conversation language. Keep CLI commands, flags, paths, ids, status enum values,
-JSONL payload keys, `source_ref` values, and copied CLI output tokens unchanged.
-
-Treat `workflow.current` as the current-step authority:
-
-1. Read every `resources.required` item whose `read_state` is
-   `read-required`. Read a `path` directly; for a resource with `command`,
-   execute that command and read the returned file. Keep read receipts only in
-   the current conversation and pass the merged receipt set back with
-   `context status --resource-receipts @<file>`; an unchanged static digest or
-   matching dynamic Route revision then returns `read_state: current`.
-   Materializing a resource is not a read: use the returned
-   `after_read_receipts` only after reading the complete returned file. A
-   `context.source-body/*` resource is the complete captured Markdown body;
-   source indexes and heading metadata never replace it. The exact
-   `resources.after_read.command` returns the re-evaluated `workflow.current`;
-   continue from that response without an additional status call.
-2. At a Gate, keep conditional context phase-local. An `inspection_action`
-   Skill or Schema is read only when performing that pre-decision inspection;
-   a `resolution_action` Skill or Schema is read only after the user confirms
-   the Gate. Neither replaces ordinary `resources.required`.
-3. Execute only `commands` returned by the Route, preserving revision and
-   authority flags exactly. A command marked `after-human-confirmation` must
-   wait for the current Gate decision. Run a command whose
-   `execution.target` is `agent-host` as a top-level host action with the
-   host's external and credential access, not inside a restricted child
-   sandbox. Request host approval when required; never weaken credential
-   storage as a workaround.
-4. If `configuration` is present, edit only the named project file using the
-   selected resources as its contract.
-5. After every action or configuration change, run status again. The managed
-   `--until` loop performs this re-evaluation internally. A phase-local
-   `next_action` can continue that operation but never replaces the workspace
-   Route.
-
-Do not infer repo sources, extraction scope, review decisions, or package output
-choices from surrounding files. Do not call source-repo operations such as
-clone, checkout, reset, fetch, install, build, or test without explicit user
-approval.

package/plugins/cursor/commands/context-init.md

@@ -1,40 +0,0 @@
----
-description: "Initialize a Context knowledge workspace."
-argument-hint: "[project-dir] [--name <name>] [--language en|zh-CN] [--debug]"
-allowed-tools: Bash(context:*), Bash(bun:*), Bash(cd *)
----
-
-Initialize a Context knowledge workspace.
-
----
-
-## Workflow
-
-Initialize a Context workspace with the global CLI, complete the returned setup
-step, then hand control to the current workflow route.
-
-Use the user's language for conversation. Keep command and payload tokens
-unchanged.
-
-Run `context init [project-dir] [--name <name>] --language <language>`. Use the
-user's explicit language choice when present; otherwise pass `zh-CN` for a
-Chinese conversation and `en` for an English conversation. This explicit CLI
-value controls generated workspace instructions and starter templates. Never
-substitute `.` when `project-dir` was omitted; the default is `context/`. Use
-`--dev` only for an explicitly requested local-link test.
-Add `--debug` only when the user explicitly asks to trace this workspace. Debug
-mode is otherwise off by default.
-
-If init reports `init-target-nonempty`, explain that existing files would share
-the workspace root. Run the returned `--allow-nonempty` command only after
-explicit confirmation.
-
-Execute the returned setup command, enter the project root, and read its
-generated `AGENTS.md`. Then run `context status --format json`, adding
-`--managed` only for fully managed operation explicitly authorized in this
-conversation. Treat `workflow.current` as authoritative: read its required
-resources, execute only exact commands, honor unresolved human gates, and
-reevaluate status after each action.
-
-Do not add extra project-local agent setup or infer sources from the surrounding
-monorepo.