@c4a/context-cli 0.5.29-alpha.2 → 0.5.29-beta.17

package/plugin/skills/drop/SKILL.md

@@ -1,170 +0,0 @@
----
-name: drop
-description: >
-  Source retraction through CLI-owned planning and application. The agent
-  calls `context drop --plan` for a structured impact plan, presents the
-  user-facing summary for confirmation, runs semantic reconciliation, then
-  calls `context drop --apply-plan --decisions` so the CLI archives raw and
-  removed knowledge, cleans active knowledge, applies source alias reindexing,
-  source stamp, changelog append, semantic ledger write, and verify.
-  Activates when `/context:drop` is invoked with a source-id, raw snapshot
-  path, or URL.
-tools:
-  - Bash
----
-
-# drop — retract a source without losing the audit trail
-
-Ask the CLI for a structured cleanup plan, confirm the user-visible impact,
-run semantic reconciliation on affected knowledge items, then ask the CLI to
-apply the plan with the confirmed decision document. Do not inspect or mutate
-workspace files directly.
-
-`WORKSPACE_DIR` is provided by the caller from `context workspace locate --format json` (`ctxDir`). It is `.context/` in embedded layout and the repository root in root layout.
-
-## TL;DR — Non-negotiables
-
-- Plan + semantic prepare/review + apply are CLI-owned. The agent only presents the plan, asks semantic questions when required, and waits for confirmation.
-- Drop removes affected raw / unsupported knowledge from the active workspace and stores them under `archive/` for restore/audit.
-- Do not Read / Glob / Grep / Write anything under `WORKSPACE_DIR`; all impact analysis and mutation must go through `context drop --plan`, `context reconcile prepare --mode drop`, `context reconcile review`, and `context drop --apply-plan --decisions`.
-- `context drop --plan <source-id|raw-path|url> --format json` resolves source-id, computes affected topics / knowledge items, and reports alias reindex impact.
-- `context drop --apply-plan <plan-file> --decisions <decisions-file> --reason "<text>" --yes` archives affected active content, consumes semantic decisions, removes unsupported Sections / empty Nodes from active knowledge, applies source alias reindexing, writes the semantic ledger, source stamp, changelog append, and verify.
-- User confirmation required unless `--yes` was passed; abort on any non-`y` answer without writing. `--yes` does not skip semantic `ask_user` questions.
-- Confirmation prose follows `${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/user-question-contract.md`: describe affected topics and claims, not source-ref mechanics.
-- Source evidence, section, and verify rule meanings stay anchored to `${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md`.
-- Output language: impact plan + report match the user's language; CLI commands, flag names, source-ids, comment attributes stay English.
-
-<reference>
-
-## Plan fields
-
-The JSON plan has:
-
-| Field | Meaning |
-|---|---|
-| `source_id` | Canonical source id resolved from user input |
-| `resolved_from.kind` | `source-id`, `snapshot-path`, or `url` |
-| `affected_nodes[]` | Topics whose source list contains the dropped source |
-| `affected_nodes[].sections[]` | Knowledge items that require semantic reconciliation before the source is dropped |
-| `affected_nodes[].reindex_sections[]` | Knowledge items whose internal source alias will be renumbered after the source is removed |
-| `affected_nodes[].will_be_sourceless` | Topic has no remaining source ids after cleanup |
-| `affected_nodes[].will_be_empty` | Topic has no remaining Section/body/children/contains after cleanup and may be archived even if another source id remains |
-| `affected_graph_edges[]` | Explicit graph edges that will be removed if one endpoint is archived by apply |
-| `unaffected_references[]` | Topic relationships that mention affected topics but are not source evidence |
-| `summary` | Counts for confirmation and changelog |
-
-If a non-domain Node would keep an active source id but lose all of its own Sections while still carrying child Nodes, contains links, or body text, do not rely on verify to catch it after mutation. Produce a semantic reanchor/split decision that preserves a supported Section, or expect `drop --apply-plan` to reject before writing.
-
-## User-facing impact summary shape
-
-```
-Affected: N topics · M knowledge items
-
-  <topic title>
-    "short claim preview" → remove from active knowledge and archive
-    "short claim preview" → keep, supported by another source document
-  <topic title>
-    "short claim preview" → remove from active knowledge and archive
-
-Proceed? [y/N]
-```
-
-Keep the internal node slug, Section id, and source-ref patch data in your
-working notes for Step 4; show them only if the user asks for implementation
-details.
-
-## CLI shapes
-
-```
-context drop --plan <source-id|raw-path|url> --format json
-context reconcile prepare --mode drop --drop-plan <plan-file> --format json
-context reconcile review --context <context-file> --decisions <decisions-file> --format json
-context drop --apply-plan <plan-file> --decisions <decisions-file> --reason "<text>" --yes
-```
-
-The apply command writes a source-specific archive under `archive/sources/`,
-moves affected raw out of active `raw/`, consumes semantic decisions for
-reanchor / remove_unsupported / split_then_reanchor, removes unsupported
-Sections / empty Nodes from active `knowledge/`, flips the source registry entry to
-`status: dropped`, stamps `drop_reason` + `dropped_at` + `archive_path`,
-appends a `[drop]` line to `knowledge/changelog.md`, records
-`decisions/semantic.yaml`, and runs verify. It exits
-non-zero if the source-id is unknown, already dropped, plan shape is invalid,
-the plan is stale, semantic decisions are unresolved/invalid, or verify reports errors.
-In drop mode, `remove_unsupported` means physical removal from active knowledge
-after the archive captures the before snapshot; compile/refresh apply uses the
-same action name for Section deprecation.
-
-</reference>
-
-<procedures>
-
-### Step 1 — Parse arguments
-
-From `$ARGUMENTS`: `<source-id|raw-path|url>` (required), `--reason <text>` (optional), `--yes` (optional). If the target is missing, stop and ask for the source id or raw snapshot path. If the reason is missing but the user's wording gives a clear reason, infer a concise reason such as `用户主动撤回`; otherwise collect it before Step 4.
-
-### Step 2 — Ask CLI for a plan
-
-Run `context drop --plan <source-id|raw-path|url> --format json`. Do not inspect
-workspace files yourself. If the CLI reports source-not-found or
-source-already-dropped, relay the error and stop.
-
-### Step 3 — Present the impact plan
-
-Render the [User-facing impact summary shape](#user-facing-impact-summary-shape)
-from the plan JSON in the user's language. Make clear that dropping a source
-removes listed content from active knowledge but keeps it restorable under
-`archive/` until `context purge`. Mention conditional graph edge cleanup when
-`affected_graph_edges[]` is non-empty; these edges are removed only if the
-endpoint leaves active knowledge after reconciliation. Include the reason that will be stamped; if
-it is still unknown, ask for the reason before continuing. If `--yes`, log
-"auto-confirmed per --yes" and continue. Otherwise wait for `y`; abort on
-anything else without writing.
-
-### Step 4 — Reconcile affected knowledge
-
-Write the exact plan JSON to a temporary file outside `WORKSPACE_DIR`, then run:
-
-```
-context reconcile prepare --mode drop --drop-plan <plan-file> --format json
-```
-
-Invoke `${CLAUDE_PLUGIN_ROOT}/skills/semantic-reconcile/SKILL.md` with that
-prepare payload. Save its decision document outside `WORKSPACE_DIR`, then run
-`context reconcile review --context <context-file> --decisions <decisions-file> --format json`.
-If review returns any `questions[]`, ask the user and convert those decisions
-from `ask_user` into one of `reanchor`, `remove_unsupported`, or
-`split_then_reanchor` before continuing. Do not let `--yes` bypass this step.
-
-### Step 5 — Apply the plan
-
-Write the exact plan JSON and confirmed semantic decision document to temporary
-files outside `WORKSPACE_DIR`, then call:
-
-```
-context drop --apply-plan <plan-file> --decisions <decisions-file> --reason "<text>" --yes
-```
-
-Do not call `context mdrive section ...` or `context mdrive node ...` for the
-standard drop flow; `drop --apply-plan --decisions` owns cleanup, ledger write,
-and verify.
-
-### Step 6 — Report
-
-The apply command already verifies. Run `context source get <source-id>` and
-report in the user's language: topics affected, knowledge items marked
-archived/removed from active knowledge, source alias reindex count, archive
-path, changelog timestamp.
-
-### Step 7 — Self-verify
-
-- [ ] No Read / Glob / Grep / Write was used against `WORKSPACE_DIR` — if any was used, restart from **Step 2** with CLI-only flow.
-- [ ] `context drop --plan` succeeded before asking the user — if not, **Step 2**.
-- [ ] `context reconcile prepare --mode drop` was run from the exact drop plan — if not, **Step 2**.
-- [ ] `context reconcile review` returned zero `questions[]` before apply; if any question remains, ask the user and regenerate the decisions document.
-- [ ] User confirmed unless `--yes` was passed — if not, abort without writing.
-- [ ] `context drop --apply-plan` exited 0 — if not, surface the CLI error and stop.
-- [ ] `context source get <source-id>` shows the source as dropped — if not, surface the mismatch.
-- [ ] The reported source entry includes `archive_path` — if missing, surface the mismatch.
-
-</procedures>

package/plugin/skills/semantic-reconcile/SKILL.md

@@ -1,129 +0,0 @@
----
-name: semantic-reconcile
-description: >
-  Internal skill for `/context:compile` and `/context:drop`. Consumes only
-  `context reconcile prepare` output, judges semantic relation/action for each
-  item, and emits a schema_version 1.0 semantic decision document for
-  `context reconcile review` / `context reconcile apply`.
-tools:
-  - Bash
----
-
-# semantic-reconcile — decide Section reconciliation
-
-Judge duplicate, merge, conflict, reanchor, and unsupported cases from the
-CLI-prepared context. Emit decisions only; the CLI performs every write.
-
-## TL;DR — Non-negotiables
-
-- Input is only the `context reconcile prepare` payload. Do not Read, Glob, Grep, or Write workspace `raw/`, `knowledge/`, `archive/`, or `decisions/`.
-- Output exactly one YAML or JSON document with `schema_version: "1.0"` and `decisions[]`.
-- Use canonical relations: `exact_duplicate`, `strong_equivalent`, `near_duplicate`, `complement`, `supersedes`, `conflicts`, `reanchor`, `unsupported`, `keep_separate`, `ask_user`.
-- Use canonical actions: `duplicate_skip`, `merge_update`, `supersede`, `reanchor`, `remove_unsupported`, `keep_separate`, `split_then_reanchor`, `ask_user`.
-- `no-op` is not a decision action. For unchanged refresh items, emit no decision or `duplicate_skip`.
-- Never expose `src-N`, Section ids, or source refs as the user-facing choice. They may appear only in the structured payload.
-- `merge_update` is legal only when the final Section content is supported by one valid `source_ref`; otherwise use `keep_separate`, `split_then_reanchor`, or `ask_user`.
-- Unresolved conflicts and low-confidence support questions must be `action: ask_user`.
-
-<reference>
-
-## Decision Shape
-
-```yaml
-schema_version: "1.0"
-decisions:
-  - item_id: claim-001
-    relation: near_duplicate
-    action: merge_update
-    target:
-      node: payment-runtime
-      section_id: section-3
-    proposed:
-      content: "Runtime isolation uses sandboxing to avoid state pollution."
-      confidence: confirmed
-      source_ref: "src-2#runtime L12-14"
-      source_ref_text: "sandboxing to avoid state pollution"
-    rationale: "The new evidence refines the same claim."
-```
-
-## Action Rules
-
-| action | Required fields | Validation |
-|---|---|---|
-| `duplicate_skip` | `target` | Exact duplicate or already-applied no-op only. |
-| `merge_update` | `target`, `proposed.content`, `proposed.source_ref`, `proposed.source_ref_text` when present in prepare | Final content must be supported by one raw line range; `proposed.kind`, when present, must match target kind. |
-| `supersede` | `target`, `proposed.kind`, `proposed.content`, `proposed.source_ref`, `proposed.source_ref_text` when present in prepare | New Section claim must be supported by one raw line range. |
-| `reanchor` | `target`, `proposed.source_ref`, `proposed.confidence` | Use only when target content is still supported by the new source. |
-| `remove_unsupported` | `target` | Use when no active source supports the target claim in this mode. |
-| `keep_separate` | `target`, `proposed.kind`, `proposed.content`, `proposed.source_ref`, `proposed.source_ref_text` when present in prepare | New orthogonal claim must be supported by one raw line range. |
-| `split_then_reanchor` | `target`, `proposed.sections[]` with each Section carrying `kind`, `content`, `source_ref`, and `source_ref_text` when present in prepare | Each split Section must be independently supported by its cited raw line range. |
-| `ask_user` | `user_confirmation.required: true` | Use only when business meaning or support cannot be decided from prepared evidence. |
-
-For `merge_update`, `supersede`, `keep_separate`, and
-`split_then_reanchor`, the final Section content must be lexically supported by
-the cited raw line range in `proposed.source_ref`. Preserve
-`proposed.source_ref_text` from the prepared context when it is present; it is
-the human-readable evidence text the CLI used to derive the canonical
-`source_ref`. Content should retain the raw evidence's key domain terms,
-numbers, code literals, and named entities. Do not turn sparse raw evidence
-into a broad summary, and do not cite a title, `Relations`, `Parent`,
-`Children`, or `Related` navigation line as the only support for a substantive
-claim.
-
-The support gate exists to prevent orphan claims and false evidence links, not
-to optimize retrieval. Prefer preserving a precise raw-backed claim over
-rewriting content into a smoother summary. If a useful reader summary would
-combine multiple evidence ranges, choose `split_then_reanchor` or `ask_user`
-instead of forcing it into one `source_ref`.
-
-Final executable decisions must not carry `user_confirmation.required: true`.
-Use that flag only on `action: ask_user` items that still require user input.
-
-`remove_unsupported` has mode-specific write behavior. In compile/refresh
-apply it deprecates the target Section so the unsupported claim remains visible
-as inactive history. In drop apply it physically removes the Section from active
-knowledge after `archive/sources/.../knowledge/before/` captures the pre-drop
-file. Use the same action only when this mode-specific outcome is intended.
-
-</reference>
-
-<procedures>
-
-### Step 1 — Read Prepared Context
-
-Use the caller-provided `context reconcile prepare` output. For each item,
-compare `proposed`, `candidates`, `previous_decisions`, and `evidence`.
-
-### Step 2 — Reuse Stable Priors
-
-If `previous_decisions[]` shows the same boundary and the prepared item still
-matches, emit the same final action. If the target changed, treat the previous
-decision as a prior only and continue judging.
-
-### Step 3 — Decide Relation And Action
-
-Classify each item:
-
-- Exact same claim already active -> `exact_duplicate` + `duplicate_skip`.
-- Same claim with a raw-supported correction or refinement from one supporting source -> `strong_equivalent` or `near_duplicate` + `merge_update`.
-- Additional but separate boundary -> `complement` + `keep_separate`.
-- New material replaces old rule -> `supersedes` + `supersede`.
-- Direct contradiction -> `conflicts` + `ask_user`.
-- Drop item still fully supported elsewhere -> `reanchor` + `reanchor`.
-- Drop item partly supported -> `reanchor` + `split_then_reanchor`.
-- No surviving support -> `unsupported` + `remove_unsupported`.
-- Evidence is close but not enough -> `ask_user`.
-
-### Step 4 — Emit Decisions
-
-Emit only executable final decisions plus unresolved `ask_user` questions.
-Do not include prose outside the document.
-
-### Step 5 — Self-verify
-
-- [ ] Every decision uses canonical relation/action values. If not, **Step 3**.
-- [ ] No `no-op` action appears. If not, **Step 3**.
-- [ ] Every write action has the required fields from [Action Rules](#action-rules). If not, **Step 4**.
-- [ ] No workspace files were read or written directly. If violated, restart from **Step 1**.
-
-</procedures>