@c4a/context-cli 0.6.0-beta.8 → 0.6.1

package/plugin/skills/skill-source-scope/references/capture-source.md

@@ -1,201 +0,0 @@
----
-name: capture-source
-description: >
-  Capture local Markdown or Lark/Feishu document sources through registered
-  Context sources and declared capture phases. Use the local `context` CLI for
-  workspace writes.
-tools:
-  - Bash
----
-
-# Capture
-
-Current capture discipline for document sources. The executable path is source
-registration plus the declared capture phase flow:
-
-- local Markdown/MDX file source: `context source add file [YYYYMMDD] --module <module> --local <path>`
-  followed by `context run capture:file:YYYYMMDD/<module> --format json`;
-- Lark/Feishu source: `context source add lark [YYYYMMDD] --module <module> ...`
-  followed by `context run capture:lark:YYYYMMDD/<module> --format json`;
-- refresh: rerun the same declared capture phase after status or the user asks
-  for recapture.
-
-Use only commands surfaced by the current status output or capture phase.
-For a user-confirmed multi-document batch, `context status --format json`
-returns every uncaptured module in `routing.command_plan`. Run the complete
-list in order; a successful module is omitted from the next status result.
-When the user explicitly asks to capture, ingest, fetch, read, or include exact
-file/Lark paths or URLs, that request is the read permission for those sources;
-do not repeat the question after registration. A mere mention, possible-source
-discussion, or register-only request is not permission, and an explicit refusal
-always wins.
-Register several file/Lark/repo sources with `context source add batch [date]
---input <yaml|json|->`; do not launch multiple `source add` processes in
-parallel. Repo batch items require `module`; file/Lark items may omit it and use
-the module returned by the CLI. A write-lock error means another Context mutation is active: wait for
-it to finish and retry rather than editing registry files.
-
----
-
-## Workflow
-
-Capture is entirely CLI-driven — your role is to register the right source,
-declare the matching capture phase, run the current `context run capture:*`
-command, and relay its output. Never hand-write captured source snapshots: the
-CLI owns normalisation (NFC, BOM strip, line endings) and the `content_hash`
-contract, so any manual edit breaks idempotency.
-
-### Code capture diagnostics
-
-Do not run hand-written dependency preflight commands before code extraction or
-document capture. The CLI owns configured runner/plugin resolution and returns
-structured `agent_hints[]` when a runner or remote-document helper is missing or
-misconfigured.
-
-If code extraction capture fails with install or runner hints, surface the CLI's `agent_hints[]` command exactly as printed. Ask the user once whether to run that command on their behalf when it touches shared state. If approved, run the exact command from `agent_hints[0].command`, then retry the same capture command. If declined, leave the command visible so the user can run it manually. Do not inline extraction packages, do not hand-write code snapshots, and do not continue with partial capture.
-
-Invocation note: document capture and code extraction do not run through `npx`.
-Use the installed `context` CLI and the declared phase command returned by
-`context status` or the phase view. When external helpers are missing, surface
-the CLI's structured install hints instead of substituting your own package
-manager or version.
-
-### Route by source boundary
-
-Before choosing a local Markdown capture route, honor the surrounding task context. Driver documents such as run instructions, handbooks, READMEs, plans, feedback issues, corpus/index/manifests, and batch lists are not Context sources unless the user explicitly asks to ingest them. Capture only ingest targets that are already explicit in the user request; if they are missing, ask one clarification instead of capturing the driver document.
-
-- One or more local `.md` / `.mdx` files or a local documentation folder to ingest →
-  register one file source with the user-confirmed boundary:
-  `context source add file [YYYYMMDD] --module <module> --local <file-or-folder>`.
-  The CLI returns the `YYYYMMDD/module` identity to use in project phases. More
-  than one file module may share the date. For an explicit
-  batch inside a broader folder, preserve the user's include list on source
-  registration. Default file capture handles `.md`. If the CLI reports
-  document-site files such as `.mdx`, `_meta.json`, sidebars, or docs config,
-  stop and confirm whether the selected boundary is a documentation site before
-  changing capture configuration. For MDX documentation sites that use
-  `_meta.json`, declare `mdxJsonDocs()` on `captureFile` in `src/index.ts`;
-  keep `_meta.json` only when it is route metadata for the selected document
-  folder. The CLI captures it as metadata and generates
-  `__context_route_metadata.md` as mechanical route evidence; it also extracts
-  static MDX component props/children into `__context_mdx_component_text.md`
-  when components carry user-facing text. Declare
-  `captureFile({ source: source("<date>", "<module>", { type: "file" }), processor: mdxJsonDocs() })`, then
-  run `context run capture:file:<date>/<module> --format json`. If the selected MDX page
-  is empty or only mounts runtime-rendered content, tell the user that capture
-  found a document-site shell and ask for the rendered-site or data-source
-  boundary instead of inventing body text.
-- A Lark/Feishu URL, doc token, or wiki token → register one Lark source:
-  `context source add lark [YYYYMMDD] --module <module> --url <url>` or the
-  matching token flag. Register every requested document under the same date;
-  do not ask for `YYYYMMDD-2`. Declare
-  `captureLark({ source: source("<date>", "<module>", { type: "lark" }) })`,
-  then run `context run capture:lark:<date>/<module> --format json`.
-- Mixed local document and Lark document batches are separate sources unless
-  the current CLI explicitly offers a combined source contract. Do not write an
-  Agent-side URL/file loop.
-- Refresh or recapture request for an already registered file/Lark source →
-  rerun the same declared capture phase. The CLI appends a new snapshot only
-  when content changes and never overwrites prior snapshots.
-- Code package extraction is not document capture. Route code source selection
-  through `skill-source-scope` extraction preview and the declared extract
-  phase. Do not invent a document capture path for code.
-- Conversation notes, decisions, and revision intents are not document capture
-  sources in the current workflow unless the CLI status or project-specific
-  phase exposes an explicit note source contract. If absent, record the user
-  guidance in the conversation and use it as pre-align hints, not as a snapshot
-  write.
-
-Do not discover files with `find` / `ls` when the user already supplied paths.
-If the include set is large, summarize it and ask for confirmation before
-registration; do not read file bodies before capture permission is clear.
-
-### Output Handling
-
-Report the CLI output verbatim. If the CLI reports `N sources changed`, suggest the right next step:
-
-- Run `context status --format json` and use its `state`, `routing`, and
-  `command_plan`; if status returns `needs-capture-phase`, first perform the
-  exact `routing.configuration` edit and rerun status.
-- While status remains `needs-capture`, execute every returned capture command
-  for the already confirmed batch before asking another naming, collection, or
-  read-permission question.
-- If status reports `captured-ready-to-investigate`, suggest the returned
-  `context run align:<type>:<source>:<collection> --view read-plan --format json`
-  command and hand off to `skill-prose-align`.
-- If status reports `needs-structure` or `structure-ready`, follow the returned
-  align/compile command instead of naming a generic slash command.
-- If status reports `compile-ready-for-review`, route to the review gate.
-- If the source was code-only and status reports pending code projection,
-  follow the CLI-owned extract/compile route returned by status.
-
-Never suggest prose compile or hand-built document knowledge for a code-only
-source. Code sources become active knowledge only through the declared
-extraction/review route returned by `context status`.
-
-If capture is rejected because another phase or write gate is active, do not
-discard it automatically. Explain the active state from `context status`, follow
-that phase when it is the intended task, and ask the user before discarding
-in-progress work when a current project command exists. If the user expected a
-different repository/workspace, change to the confirmed workspace root before
-retrying capture.
-
-## Final Report
-
-Report in the user's conversation language. Translate section headings into the user's language instead of copying the English labels below verbatim. Optimize for human readability: use document titles instead of source ids, package names instead of internal source id strings, and human-readable kind labels ("local markdown", "Feishu doc", "code package") instead of internal tokens. Do not surface content hashes, snapshot digests, internal payload identifiers, or absolute file paths.
-
-Stable structure:
-
-1. Completion headline. Single line with the action verb plus core counts: how
-   many sources were captured this round, broken down by `new` / `updated` /
-   `unchanged`. Capture data from the current `context run capture:* --format
-   json` result summary, or per-source statuses when no aggregate is returned.
-2. Per-source list grouped by status. Show each captured source under one of three groups (`new` / `updated` / `unchanged`); within each group list the document title (`source.title`), kind label, and a short delta indicator for updated sources (for example added/removed line counts when the CLI returns them; otherwise "content changed"). Cache-hit code packages belong in `unchanged`. Omit groups that are empty.
-3. Pending phase signals. When `context status --format json` reports follow-up
-   work tied to this capture (sources pending align, sources pending compile,
-   refreshed sources pending recompile, code sources pending projection),
-   summarize each as a single line naming the work and which sources are
-   affected. Omit the section entirely when there is no pending follow-up.
-4. Next step. Single command suggestion driven by status: the returned
-   `context run align:<type>:<source>:<collection> ...` command when structure work is
-   pending, the returned `context run compile:<type>:<source>:<collection> ...`
-   command when prose compile work is pending, or the CLI-owned code projection
-   command when code projection is pending. If nothing is pending, say so
-   explicitly.
-
-Do not include raw CLI diagnostics, agent_hints content, schema names, or phase
-payload identifiers in the report. Those belong in earlier troubleshooting
-output, not in the completion summary.
-
-## Reference
-
-### Missing Dependency Recovery
-
-If the CLI returns `agent_hints[]` for a missing code runner or plugin package, stop and surface the hint. Ask the user once for permission to run `agent_hints[0].command` (the CLI has already picked the correct package manager — `npm install -g` or `bun install -g` — based on how `context` itself was installed). If approved, run that exact command via `Bash` and then retry the same capture; if declined, leave the command visible for manual install. Never substitute a different package manager or version.
-
-If the CLI prints a missing-dependency error like `lark-cli not installed`, walk the user through installation:
-
-1. Ask once up-front whether to proceed with install. If no → stop and tell the user to install manually from the tool's official README, then re-run.
-2. `WebFetch` the tool's official README (for `lark-cli` that's `https://github.com/larksuite/cli/blob/main/README.md#quick-start-ai-agent`).
-3. For each command the README prescribes for the user's platform, show the command then call `Bash`. The host's per-tool permission prompt is the user's confirmation surface; don't add extra y/n questions between commands.
-4. Stop on any failure; surface stderr verbatim.
-5. After success, tell the user to rerun the current Context command that
-   failed.
-
-### Language Policy
-
-Your prose to the user follows the user's conversation language. CLI commands, flag names, URLs, env-var names, binary names, source-ids stay English.
-
-### Invariants
-
-- Captured source snapshots are immutable post-write — the CLI only ever appends new snapshots.
-- The source registry is authoritative; derived index files are not Agent phase
-  inputs.
-- Local `.md` / `.mdx` source identity follows the captured file's stable origin path, not its H1/title. If the user edits the title but captures the same path again, the CLI appends a new snapshot to the same `local:*` source.
-- In `--format json`, code capture runner cache state is authoritative in `result.runner.cacheMode`: `prepared` means a workspace runner was prepared, `cached` means workspace cache hit, and `bypass` means `--no-runner-cache` used a temporary runner directory instead of the workspace runner cache.
-- Code extraction runner evidence is derived by the CLI from emitted source files. Do not ask users to configure `evidence.mode`; rerun capture after fixing the runner emit output.
-- Code extraction snapshots ship with `evidence.mode: none`; symbols/files/edges are indexed inside the code bucket. Do not ask users to inspect or repair a code `.evidence` manifest.
-- Code extraction/projection is separate from document capture. Materialize code
-  knowledge through the declared extract/code projection flow before prose align
-  attaches documentation to code Nodes.
-- On duplicate capture of the same URL: identical `content_hash` → CLI skips with `unchanged`; different hash → CLI appends a new snapshot.

package/plugins/assets/icon.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 758 296" fill="none">
-  <path fill-rule="evenodd" clip-rule="evenodd" d="M647.569 0.78043C613.4 3.48518 581.318 15.3269 533.021 43.0605C527.45 46.2597 498.781 61.8832 490.42 67.9156C464.4 83.1281 440.36 99.9754 407.462 125.999C399.965 131.93 392.626 137.658 391.153 138.729C389.68 139.8 382.798 145.128 375.858 150.569C368.919 156.01 358.504 163.98 352.714 168.281L343.516 175.006L348.516 179.006C351.553 181.229 358.164 187.09 362.516 190.006L370.516 196.006L379.016 190.006C384.498 185.597 392.279 178.726 395.782 175.811C399.285 172.896 411.776 162.857 414.201 160.847C416.626 158.838 420.318 155.949 427.144 150.29C445.631 134.963 481.502 112.007 494.26 102.533C581.313 47.1925 633.705 27.2029 682.312 46.6436C688.772 50.1275 692.158 52.8781 699.014 60.2106C706.594 68.3166 708.17 70.6632 712.305 79.9992C717.792 92.3865 720.263 102.609 721.288 117.182C723.104 142.96 716.794 171.243 703.236 198.108C693.06 218.269 684.3 229.708 671.088 242.211C628.153 272.315 597.665 274.481 543.801 261.017C510.873 246.43 487.481 230.006 448.016 193.506C444.204 190.241 440.144 186.014 439.516 186.006C438.281 185.991 399.991 214.634 399.516 216.006C399.235 216.815 404.057 219.412 409.016 222.506C410.702 223.559 412.975 225.335 416.516 227.006C433.391 238.059 468.991 255.632 482.516 262.006C485.929 263.614 490.402 264.707 492.545 265.749C509.884 274.195 533.276 282.099 555.644 287.07C564.55 289.049 601.674 289.814 609.103 288.171C612.031 287.523 616.387 286.554 618.782 286.017C633.747 282.66 656.745 272.897 670.289 264.153C708.746 239.325 740.493 194.104 753.016 146.317C764.533 102.359 755.681 60.2459 728.902 31.5909C712.119 13.6333 693.371 4.36271 667.389 1.17066C661.613 0.461953 656.637 -0.0628543 656.33 0.00607299C656.023 0.0750003 652.081 0.42386 647.569 0.78043ZM122.268 6.91848C100.692 8.62683 75.6783 17.7423 58.0176 30.3336C30.2119 50.158 12.2534 76.5887 3.92103 109.95C0.744084 122.668 -0.943192 149.281 0.550004 163.097C6.34545 216.709 38.9366 261.239 87.8925 282.436C108.528 291.37 128.098 295.45 152.658 295.937C173.489 296.35 191.779 294.037 213.531 288.238C254.082 277.427 282.658 266.098 328.68 231.976C341.818 222.235 344.259 221.314 342.05 219.506C337.696 215.941 316.951 199.525 316.016 199.506C315.451 199.495 312.641 202.192 307.128 205.872C245.084 247.275 198.239 258.453 151.476 252.979C138.261 251.432 123.184 247.836 114.645 244.194C82.5503 230.506 61.7452 207.016 52.8018 174.371C50.4952 165.952 50.3622 164.208 50.7059 146.886C51.0496 129.561 51.2517 127.827 53.8915 119.499C58.217 105.86 62.5516 96.3835 68.4271 87.7254C96.678 46.0924 144.857 34.898 199.322 57.3119C205.245 59.7489 221.144 67.3217 224.619 69.361C245.505 81.6138 248.559 83.5927 268.609 97.8683C286.178 110.375 299.632 125.4 316.016 139.031C330.379 150.982 332.229 144.373 335.6 144.44C337.306 142.561 337.353 141.225 335.571 139.031C334.554 137.779 334.892 138.21 331.041 133.458C307.893 104.899 285.92 82.0366 264.533 63.4627C232.185 35.3673 200.085 17.5822 168.343 10.1701C158.514 7.87465 132.964 6.07147 122.268 6.91848Z" fill="#ef6f2e"/>
-</svg>

package/plugins/cursor/assets/icon.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 758 296" fill="none">
-  <path fill-rule="evenodd" clip-rule="evenodd" d="M647.569 0.78043C613.4 3.48518 581.318 15.3269 533.021 43.0605C527.45 46.2597 498.781 61.8832 490.42 67.9156C464.4 83.1281 440.36 99.9754 407.462 125.999C399.965 131.93 392.626 137.658 391.153 138.729C389.68 139.8 382.798 145.128 375.858 150.569C368.919 156.01 358.504 163.98 352.714 168.281L343.516 175.006L348.516 179.006C351.553 181.229 358.164 187.09 362.516 190.006L370.516 196.006L379.016 190.006C384.498 185.597 392.279 178.726 395.782 175.811C399.285 172.896 411.776 162.857 414.201 160.847C416.626 158.838 420.318 155.949 427.144 150.29C445.631 134.963 481.502 112.007 494.26 102.533C581.313 47.1925 633.705 27.2029 682.312 46.6436C688.772 50.1275 692.158 52.8781 699.014 60.2106C706.594 68.3166 708.17 70.6632 712.305 79.9992C717.792 92.3865 720.263 102.609 721.288 117.182C723.104 142.96 716.794 171.243 703.236 198.108C693.06 218.269 684.3 229.708 671.088 242.211C628.153 272.315 597.665 274.481 543.801 261.017C510.873 246.43 487.481 230.006 448.016 193.506C444.204 190.241 440.144 186.014 439.516 186.006C438.281 185.991 399.991 214.634 399.516 216.006C399.235 216.815 404.057 219.412 409.016 222.506C410.702 223.559 412.975 225.335 416.516 227.006C433.391 238.059 468.991 255.632 482.516 262.006C485.929 263.614 490.402 264.707 492.545 265.749C509.884 274.195 533.276 282.099 555.644 287.07C564.55 289.049 601.674 289.814 609.103 288.171C612.031 287.523 616.387 286.554 618.782 286.017C633.747 282.66 656.745 272.897 670.289 264.153C708.746 239.325 740.493 194.104 753.016 146.317C764.533 102.359 755.681 60.2459 728.902 31.5909C712.119 13.6333 693.371 4.36271 667.389 1.17066C661.613 0.461953 656.637 -0.0628543 656.33 0.00607299C656.023 0.0750003 652.081 0.42386 647.569 0.78043ZM122.268 6.91848C100.692 8.62683 75.6783 17.7423 58.0176 30.3336C30.2119 50.158 12.2534 76.5887 3.92103 109.95C0.744084 122.668 -0.943192 149.281 0.550004 163.097C6.34545 216.709 38.9366 261.239 87.8925 282.436C108.528 291.37 128.098 295.45 152.658 295.937C173.489 296.35 191.779 294.037 213.531 288.238C254.082 277.427 282.658 266.098 328.68 231.976C341.818 222.235 344.259 221.314 342.05 219.506C337.696 215.941 316.951 199.525 316.016 199.506C315.451 199.495 312.641 202.192 307.128 205.872C245.084 247.275 198.239 258.453 151.476 252.979C138.261 251.432 123.184 247.836 114.645 244.194C82.5503 230.506 61.7452 207.016 52.8018 174.371C50.4952 165.952 50.3622 164.208 50.7059 146.886C51.0496 129.561 51.2517 127.827 53.8915 119.499C58.217 105.86 62.5516 96.3835 68.4271 87.7254C96.678 46.0924 144.857 34.898 199.322 57.3119C205.245 59.7489 221.144 67.3217 224.619 69.361C245.505 81.6138 248.559 83.5927 268.609 97.8683C286.178 110.375 299.632 125.4 316.016 139.031C330.379 150.982 332.229 144.373 335.6 144.44C337.306 142.561 337.353 141.225 335.571 139.031C334.554 137.779 334.892 138.21 331.041 133.458C307.893 104.899 285.92 82.0366 264.533 63.4627C232.185 35.3673 200.085 17.5822 168.343 10.1701C158.514 7.87465 132.964 6.07147 122.268 6.91848Z" fill="#ef6f2e"/>
-</svg>