@c4a/context-cli 0.6.7 → 0.6.9

package/providers/context/graphs/workspace.yaml

@@ -2,7 +2,7 @@ schema: agent-graph.graph.v1
 id: workspace
 description: Fact-grounded lifecycle for a Context knowledge workspace.
 entrypoints:
-  continue: repair-project-entry
+  context: repair-project-entry
 nodes:
   - id: repair-project-entry
     kind: action
@@ -92,6 +92,12 @@ nodes:
     kind: gate
     reasonCode: route.structure.confirmation-required
     inspectionAction: actions/inspect-structure.yaml
+    resolutionAction: actions/apply-structure-confirmation.yaml
+    delegated:
+      inspection: skip
+      resources:
+        required: []
+        recommended: []
     gate:
       id: structure-confirmation
       prompt: Confirm the proposed knowledge structure before candidates are compiled.
@@ -166,6 +172,12 @@ nodes:
     kind: gate
     reasonCode: route.review.decision-required
     inspectionAction: actions/inspect-review.yaml
+    delegated:
+      inspection: skip
+      resolutionAction: actions/apply-managed-review.yaml
+      resources:
+        required: []
+        recommended: []
     gate:
       id: knowledge-review
       prompt: Review the complete current document candidate batch before it enters approved knowledge.
@@ -210,6 +222,7 @@ nodes:
         - resources/procedures/source-boundary.md
         - resources/dialogue/human-gates.md
         - resources/dialogue/source-boundary.md
+        - resources/dialogue/workflow-mode-after-creation.md
         - resources/views/source-current.yaml
       recommended:
         - resources/procedures/source-capture-detailed.md
@@ -290,6 +303,14 @@ nodes:
     kind: gate
     reasonCode: route.extract.scope-required
     inspectionAction: actions/inspect-code-extraction.yaml
+    delegated:
+      resources:
+        required:
+          - resources/procedures/code-extraction.md
+          - resources/dialogue/code-extraction.md
+          - resources/views/source-current.yaml
+        recommended:
+          - resources/procedures/source-capture-detailed.md
     gate:
       id: extraction-scope
       prompt: Confirm which registered code modules and symbol boundaries should enter code knowledge.
@@ -303,6 +324,7 @@ nodes:
         - resources/procedures/code-extraction.md
         - resources/dialogue/human-gates.md
         - resources/dialogue/code-extraction.md
+        - resources/dialogue/workflow-mode-after-capture.md
         - resources/views/source-current.yaml
       recommended:
         - resources/procedures/source-capture-detailed.md
@@ -337,6 +359,12 @@ nodes:
     kind: gate
     reasonCode: route.document.classification-required
     inspectionAction: actions/inspect-document-classification.yaml
+    delegated:
+      resources:
+        required:
+          - resources/procedures/document-classification.md
+          - resources/dialogue/document-classification.md
+          - resources/views/source-current.yaml
     gate:
       id: document-classification
       prompt: Confirm the evidence-backed knowledge collection for the next captured document.
@@ -350,6 +378,7 @@ nodes:
         - resources/procedures/document-classification.md
         - resources/dialogue/human-gates.md
         - resources/dialogue/document-classification.md
+        - resources/dialogue/workflow-mode-after-capture.md
         - resources/views/source-current.yaml
 
   - id: configure-prose-lifecycle
@@ -387,6 +416,12 @@ nodes:
     kind: gate
     reasonCode: route.review.decision-required
     inspectionAction: actions/inspect-review.yaml
+    delegated:
+      inspection: skip
+      resolutionAction: actions/apply-managed-review.yaml
+      resources:
+        required: []
+        recommended: []
     gate:
       id: knowledge-review
       prompt: Review the complete current candidate batch before it enters approved knowledge.
@@ -484,6 +519,10 @@ nodes:
     kind: gate
     reasonCode: route.package.template-review-required
     resolutionAction: actions/accept-package-templates.yaml
+    delegated:
+      resources:
+        required: []
+        recommended: []
     gate:
       id: package-template-review
       prompt: Replace or edit the declared package templates, or explicitly accept the unchanged generic defaults.
@@ -499,6 +538,17 @@ nodes:
         - resources/views/package-current.yaml
         - resources/manuals/reference/package-templates.md
 
+  - id: flush-logs-after-build
+    kind: action
+    reasonCode: route.logs.delivery-pending
+    action: actions/flush-runtime-events.yaml
+    satisfiedBy:
+      - path: logs.final_pending
+        exists: false
+    resources:
+      required:
+        - resources/procedures/runtime-event-delivery.md
+
   - id: current-scope-complete
     kind: terminal
     terminalOutcome: completed
@@ -534,4 +584,5 @@ edges:
   - { from: choose-package-output, to: configure-package-output, kind: gatedBy }
   - { from: configure-package-output, to: review-package-template }
   - { from: review-package-template, to: build-next, kind: gatedBy }
-  - { from: build-next, to: current-scope-complete }
+  - { from: build-next, to: flush-logs-after-build }
+  - { from: flush-logs-after-build, to: current-scope-complete }

package/providers/context/manifest.json

@@ -2,14 +2,14 @@
   "schema": "agent-graph.bundle.v1",
   "provider": {
     "id": "c4a/context",
-    "version": "0.6.7"
+    "version": "0.6.9"
   },
   "providerManifest": "provider.yaml",
   "graphs": [
     {
       "id": "workspace",
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:83c1b8feb410398a34051810cbefffe8fc86dd44211d32e049d3007ecea24d7e"
+      "digest": "sha256:cfc421a1bb645eac298883f59137e363d36d3c053a6e658324533eafaafea6c7"
     }
   ],
   "actions": [
@@ -78,6 +78,11 @@
       "path": "actions/extract-next.yaml",
       "digest": "sha256:3d5e26cbdd912c9be666ce423b19456b31ab67da53c4e01a1a1c7a3dc1e6420a"
     },
+    {
+      "id": "flush-runtime-events",
+      "path": "actions/flush-runtime-events.yaml",
+      "digest": "sha256:a5f29f652fc9f5f3775fdf9aad0af837f8c72879a22c11074321923bda49b45a"
+    },
     {
       "id": "inspect-code-extraction",
       "path": "actions/inspect-code-extraction.yaml",
@@ -163,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:c42ea22df144db608ab5dc3718704b2e42c0e7a4fe51ca322dfbe705f0619549"
+      "digest": "sha256:e4052794b74c240c0de85d3ba89ba44144fd282426f478359b2defa4d0c6217b"
     },
     {
       "id": "context.sdk.project-api",
@@ -295,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",
@@ -333,7 +348,7 @@
     {
       "id": "procedure.package-output",
       "path": "resources/procedures/package-output.md",
-      "digest": "sha256:5d93de483e668fe77c5eaabb3ae52d4d9c36f73b61e264fd40d53f7f4d008bf8"
+      "digest": "sha256:d75ccce1f1eccff40c1d0d66319286d6a940ca0b83c185a1cee1bebd65b3af8e"
     },
     {
       "id": "procedure.project-configuration",
@@ -355,6 +370,11 @@
       "path": "resources/procedures/repository-source-recovery.md",
       "digest": "sha256:af42c0f67d48518e76f4feac1969476fe16e35f591d2dd4432ae57fb31b6f794"
     },
+    {
+      "id": "procedure.runtime-event-delivery",
+      "path": "resources/procedures/runtime-event-delivery.md",
+      "digest": "sha256:bb7e695270d9d8780fa7b7cdd4cde883cc05a5f63e97fb18088838623f4ce381"
+    },
     {
       "id": "procedure.source-boundary",
       "path": "resources/procedures/source-boundary.md",
@@ -446,6 +466,10 @@
       "path": "actions/extract-next.yaml",
       "digest": "sha256:3d5e26cbdd912c9be666ce423b19456b31ab67da53c4e01a1a1c7a3dc1e6420a"
     },
+    {
+      "path": "actions/flush-runtime-events.yaml",
+      "digest": "sha256:a5f29f652fc9f5f3775fdf9aad0af837f8c72879a22c11074321923bda49b45a"
+    },
     {
       "path": "actions/inspect-code-extraction.yaml",
       "digest": "sha256:214cf9b0f9645ec7164a779ab5779ccf5b3e3132b10f8f9f666213d048f582b1"
@@ -500,15 +524,15 @@
     },
     {
       "path": "codes.yaml",
-      "digest": "sha256:583f6b7e4d489d42328ea0f7ad73b95c6a28c03cc44bd4b703443f00cdb66a6d"
+      "digest": "sha256:407f6e1db47a4248f082cb347058a76547c0c6888511de5e49182afcd7a78eb6"
     },
     {
       "path": "graphs/workspace.yaml",
-      "digest": "sha256:83c1b8feb410398a34051810cbefffe8fc86dd44211d32e049d3007ecea24d7e"
+      "digest": "sha256:cfc421a1bb645eac298883f59137e363d36d3c053a6e658324533eafaafea6c7"
     },
     {
       "path": "provider.yaml",
-      "digest": "sha256:ba20dd22b84639677e224787555f427e66042a72101454824e136bca222034da"
+      "digest": "sha256:ef4af3314dc2d10892d97f0236d68b8a3b7549cfbcb5c55c45efc3de08b2a50e"
     },
     {
       "path": "resources/diagnostics/projection-stale.md",
@@ -562,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",
@@ -576,7 +608,7 @@
     },
     {
       "path": "resources/manuals/reference/package-templates.md",
-      "digest": "sha256:c42ea22df144db608ab5dc3718704b2e42c0e7a4fe51ca322dfbe705f0619549"
+      "digest": "sha256:e4052794b74c240c0de85d3ba89ba44144fd282426f478359b2defa4d0c6217b"
     },
     {
       "path": "resources/manuals/reference/project-api.md",
@@ -612,7 +644,7 @@
     },
     {
       "path": "resources/procedures/package-output.md",
-      "digest": "sha256:5d93de483e668fe77c5eaabb3ae52d4d9c36f73b61e264fd40d53f7f4d008bf8"
+      "digest": "sha256:d75ccce1f1eccff40c1d0d66319286d6a940ca0b83c185a1cee1bebd65b3af8e"
     },
     {
       "path": "resources/procedures/project-configuration.md",
@@ -630,6 +662,10 @@
       "path": "resources/procedures/repository-source-recovery.md",
       "digest": "sha256:af42c0f67d48518e76f4feac1969476fe16e35f591d2dd4432ae57fb31b6f794"
     },
+    {
+      "path": "resources/procedures/runtime-event-delivery.md",
+      "digest": "sha256:bb7e695270d9d8780fa7b7cdd4cde883cc05a5f63e97fb18088838623f4ce381"
+    },
     {
       "path": "resources/procedures/source-boundary.md",
       "digest": "sha256:99097947961d7fa5b17f9e6b9c9471aac38cec1943bd7feb414b21d6a1e26a49"
@@ -714,5 +750,5 @@
   "graphDependencies": {
     "workspace": []
   },
-  "digest": "sha256:9e3ccfd59436360fd799f8f399c848caa7b52a51e50c61562d1aa3c06f905dae"
+  "digest": "sha256:3550fa7734792eb9bcc2abacf04f7fff9c0ac14344bbecea3a2b961f1354c8b3"
 }

package/providers/context/provider.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.provider.v1
 id: c4a/context
-version: 0.6.7
+version: 0.6.9
 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

@@ -73,6 +73,18 @@ inside Git, because Context must resolve the current commit. A workspace outside
 Git must use a literal, already-published prefix without `{commit}`. Context
 appends the project-relative `knowledge/assets/...` path.
 
+For a non-GitHub service that exposes raw files through the GitHub-compatible
+same-host layout
+`https://<host>/<namespace>/<repository>/raw/<ref>/<path>`, derive and configure
+the explicit prefix before choosing bundled delivery. For example, use
+`https://git.example.com/team/knowledge/raw/{commit}` for a workspace at the
+repository root. If the workspace is nested, append its repository-relative
+directory to the prefix because Context appends only the project-relative
+`knowledge/assets/...` path. This derivation is appropriate only when the
+service's raw convention and repository identity are confirmed; otherwise ask
+for the prefix or use bundled delivery. The fact that Context does not
+automatically recognize a host is not, by itself, a reason to bundle.
+
 The resolved commit and raw URL participate in package freshness, so changing
 Git HEAD or the selected remote makes an existing package stale. Context does
 not check whether resources are committed, pushed, or remotely readable;
@@ -315,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/providers/context/resources/procedures/package-output.md

@@ -43,8 +43,22 @@ commit-pinned URL or that explicit prefix. Context does not check whether those
 files are committed, pushed, or remotely readable; that remains the package
 author's responsibility. If neither Git nor an explicit prefix is available,
 offer bundled resources or explicit omission; omission keeps unresolved links
-and must be described as such. Do not infer repository identity or invent a raw
-host URL.
+and must be described as such.
+
+Before falling back to bundled delivery for a non-GitHub remote, inspect the
+confirmed repository web URL or a known raw-file URL. When the Git service uses
+the GitHub-compatible same-host shape
+`https://<host>/<namespace>/<repository>/raw/<ref>/<path>`, prefer an explicit
+`urlPrefix` such as
+`https://git.example.com/team/knowledge/raw/{commit}`. Include the
+repository-relative workspace directory in that prefix when the Context
+workspace is nested below the repository root; Context appends the
+project-relative `knowledge/assets/...` path. Lack of built-in automatic
+derivation alone is not a reason to bundle. Prefer `{commit}` for immutable
+links; use a literal published ref only when the author intentionally wants it.
+If the service's raw convention or repository identity cannot be established,
+do not guess or probe an invented endpoint: ask the author for `urlPrefix`, or
+offer bundled delivery.
 
 Large image optimization applies only to bundled delivery. Without an `assets`
 declaration, existing workspaces continue to copy selected resources

package/providers/context/resources/procedures/runtime-event-delivery.md

@@ -0,0 +1,86 @@
+---
+id: procedure.runtime-event-delivery
+kind: procedure
+mediaType: text/markdown
+---
+
+# Runtime event delivery
+
+This route exists only when the installed Context package configured a runtime
+event sink and the build-completion batch remains in the workspace outbox.
+Initialization, workspace activity, and close events are delivered silently on
+a best-effort basis; their failures stay queued and never select this route by
+themselves. Build appends its completion event and attempts the accumulated
+outbox as one batch. Only a failed build-boundary delivery selects this route.
+Those earlier event failures must never request host escalation by themselves.
+
+An explicit fully managed request in the current conversation authorizes
+delivery through that package-owned sink. This is explicit user authorization
+for the allowlisted runtime metrics; do not ask the user for endpoint-specific
+consent again or pause only because the sink is external telemetry. It does not
+remove the Agent host's network approval boundary. Satisfy that boundary by
+requesting host network escalation in the tool invocation that executes the
+flush, not by turning it into another conversational approval gate.
+
+Before requesting network access, run:
+
+```bash
+context logs plan --format json
+```
+
+The plan is the audit contract. It reports the canonical workspace outbox,
+normally `.tmp/context-runtime/logs/outbox.jsonl`, the event count and kinds,
+the allowlisted property names, the sink command, and the resolved HTTP
+destination when the sink supports description. Quote the exact outbox path,
+event count and kinds, destination, method, and data policy in the host approval
+request. If the plan reports a proxy destination and an upstream target, quote
+both. Event count, event-kind mix, and property-key mix are audit details, not
+new conversational consent boundaries. The accumulated build batch may include
+queued initialization, activity, and close events. When the destination, input
+schema, and data policy are unchanged, do not ask again merely because those
+allowlisted payload details differ from an earlier attempt. Immediately run
+only the `flush_command` returned by the plan as a
+top-level Agent-host action with the host network escalation or approval
+mechanism. Do not stop to write a blocker before attempting that host action. A
+host approval prompt is an execution boundary, not a new user decision. Stop
+only if the host denies the request or the command still fails with host network
+access.
+
+Apply these approval rules exactly:
+
+1. A fully managed request is the user authorization for the package-owned,
+   allowlisted runtime-event sink in the current conversation. Do not add an
+   endpoint-specific conversational confirmation on top of it.
+2. Initialization, workspace-activity, and close commands use silent
+   best-effort delivery. A failure from any of them remains in the outbox and
+   must not request host escalation, select a delivery route, create a blocker,
+   or interrupt the knowledge workflow.
+3. Build appends its completion event and attempts the complete accumulated
+   outbox as one batch. Only failure of that build-boundary batch may select
+   this route and request host network escalation.
+4. A later batch may have a different event count, event order, event-kind mix,
+   or property-key mix because earlier silent events accumulated. If the fixed
+   destination, HTTP method, input schema, and data policy are unchanged and the
+   package-owned sink accepts the batch, that payload variation is already
+   authorized. Do not ask the user to enumerate or approve the current fields.
+5. A changed destination, proxy or upstream target, HTTP method, input schema,
+   or data policy is a new audit boundary. Stop and surface the changed plan
+   before requesting network access. An unresolved destination is also a
+   blocker; never replace it with a guessed endpoint.
+6. Request host network escalation by invoking the exact returned
+   `flush_command` as the top-level Agent-host action. Do not first ask a chat
+   question, write an issue, suggest a manual command, or retry inside the same
+   restricted sandbox.
+7. After host approval, continue the workflow immediately when the sink
+   acknowledges the batch. Stop only when the host denies execution, the
+   escalated command still fails, or the plan violates the audit requirements
+   above.
+
+Flush converts pending records to `context.runtime-event-batch.v1` and passes
+that batch on stdin to the package-owned command. It never uploads the outbox
+file as a file and exposes no arbitrary payload or destination option. Do not
+read, edit, copy, or substitute the outbox, and do not add a payload-file flag.
+After a successful sink acknowledgement, Context removes the acknowledged
+records. If the plan cannot resolve a network destination, stop and report that
+the installed sink lacks an auditable description instead of requesting broad
+network access.

package/plugins/claude/commands/continue.md

@@ -1,85 +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
-```
-
-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.