@c4a/context-cli 0.6.0-beta.7 → 0.6.1-beta.1

package/plugin/skills/skill-prose-align/SKILL.md

@@ -1,327 +0,0 @@
----
-name: skill-prose-align
-description: >
-  Internal procedure invoked by the public Context continuation entry; not a user slash command.
-  Uses Context document evidence views to propose, validate, and confirm
-  `unapproved/structure.yaml` without reading raw snapshots directly.
-tools:
-  - Bash
----
-
-# skill-prose-align
-
-Turn captured document evidence into confirmed structure.
-
-## TL;DR
-
-- Use this after document capture, or when the user asks to split, merge,
-  reorganize, classify, or relate document evidence.
-- The first product output is a structure draft, not final page body.
-- Read source material only through CLI evidence views: `read-plan`,
-  `source-index`, `span-detail`, `span-text`, `schema`, and
-  `structure-summary`. Additional views are diagnostic surfaces; use the route
-  and view set returned by the CLI.
-- Write and validate `context.structure.v1` into `unapproved/structure.yaml`.
-  Stop for user confirmation before compile.
-- Before classifying nodes, section plans, edges, support strength, duplicates,
-  conflicts, ownership, or unresolved items, read only the procedure references
-  in the CLI `semantic_rules.required` set. Use each returned `reason` to keep
-  unrelated rules out of the current judgment.
-- Plan source evidence as Sections before promoting any heading to a Node/View.
-  Local FAQ, decision, incident, warning, or reference fragments normally stay
-  under the owning View unless source evidence proves independent retrieval
-  identity.
-- Do not produce or validate a structure payload from this entry file alone. A
-  ruleset already present in the active context may be reused only when both its
-  `handle` and `digest` match. If the context was compacted, the digest changed,
-  or the rule content is no longer present, read `semantic_rules.required`.
-- When status reaches `structure-ready` or `needs-prose-compile`, hand off to
-  `${CLAUDE_PLUGIN_ROOT}/skills/skill-prose-compile/SKILL.md`.
-- Compile, review, close, verify, and build remain separate gates.
-
-<reference>
-
-## User-Facing Gates
-
-Use semantic labels, not SDK function names:
-
-| Gate | Say this | Do not say this first |
-|---|---|---|
-| Material investigation | "I will read the evidence index and source spans through Context, then propose a structure draft." | `alignProse`, `source-index`, `context.structure.v1` |
-| Structure confirmation | "Confirming this structure freezes page paths, section ownership, and relationships for this compile round." | `unapproved/structure.yaml` as a raw parameter |
-| Compile handoff | "The structure is confirmed; I will switch to source-bound compile for draft pages." | Continuing to edit structure in compile |
-
-## Runtime Discipline
-
-Use these rules in the current phase-runner flow:
-
-- Follow the top-level state, `routing.command_plan`, CLI `next_action`, and
-  CLI-returned `next_command` values for every write. Treat `allowed_actions[]`
-  as permission for read-only insertions; it is not a menu of alternate write
-  paths.
-- Use `views[].command` / `next_command` for evidence reads, prioritizing the
-  CLI-designated expected view when present.
-- Treat `agent_hints[]` as temporary diagnostics. If an agent hint conflicts
-  with a top-level `next_action` or status route, follow the top-level route.
-- Do not use direct file tools, shell scripts, `jq`, `sed`, `cat`, `head`,
-  `tail`, Python, or Node.js to inspect `sources/`, `unapproved/`,
-  `knowledge/`, `dist/`, or CLI-managed `.tmp` as a substitute for Context
-  views.
-- Write digest/hash flags are stale guards. Use the value returned by the CLI;
-  do not parse stdout fragments or host tool-result files to reconstruct one.
-- Delegated execution is only valid when the user explicitly authorizes it in
-  this conversation. Do not infer it from "continue", "继续", or general trust.
-- Run one write at a time. Do not parallelize align stage, compile stage, review
-  apply, close, or build writes.
-- If a payload is too large for a heredoc, stage it under
-  `.tmp/agent-payloads/<run-id>/...` in the workspace root and redirect stdin
-  from that file. Never reuse fixed `/tmp/c4a-*` names, and never place agent
-  scratch payloads under CLI-managed `.tmp/context-cli/`, `sources/`,
-  `unapproved/`, `knowledge/`, `dist/`, or package output directories.
-- If a validation or view response includes `reason_code`, `path`, `missing[]`,
-  `diagnostics`, `repair_hints`, or `agent_hints`, treat those fields as the
-  repair contract. Do not recover by replaying a stale manual route, editing
-  rendered files, or guessing schema aliases.
-
-## Evidence Views
-
-Recommended read order:
-
-```bash
-context run align:<type>:<source>:<collection> --view read-plan --format json
-context run align:<type>:<source>:<collection> --view source-index --compact --format json
-context run align:<type>:<source>:<collection> --view span-detail --span <source-ref> --format json
-context run align:<type>:<source>:<collection> --view span-text --span <source-ref> --format json
-context run align:<type>:<source>:<collection> --view schema --format json
-context run align:<type>:<source>:<collection> --view structure-summary --input <structure.yaml> --format json
-```
-
-Use CLI-returned `next_command` values for pagination. Do not reconstruct
-documents with ad hoc `cat`, `grep`, or scripts against `sources/` or `.tmp`.
-
-## Structure Contract
-
-The structure draft uses `schema_version: context.structure.v1` and lives at
-`unapproved/structure.yaml` after staging. It contains:
-
-- lifecycle state such as validated/confirmed and frozen snapshot metadata;
-- concept `nodes[]` with stable `node_ref`, `node_type`, title/summary, and
-  ownership;
-- materialized `views[]` with `view_ref`, collection, path, section plans, and
-  evidence refs;
-- typed edges using the closed set defined by the CLI;
-- unresolved items when evidence is weak, conflicting, or the target node is
-  missing.
-
-Confirmed structure is a human gate. Validation passing is not the same as
-confirmation. Do not write `lifecycle.state: confirmed`, `confirmed_by`,
-`confirmed_at`, or `structure_digest` until the user has explicitly confirmed
-the structure proposal in the conversation.
-
-## Procedure References
-
-These are current structure planning rules. They define the source-bound
-semantic gates for Node planning, section ownership, and relationship handling.
-
-| Decision | Reference |
-|---|---|
-| Structure planning, Node ownership, density, candidate resolution | [references/internal-procedures/structure-planning.md](references/internal-procedures/structure-planning.md) |
-| Node type, title, tags, fake entity, action/domain gates, edge gates | [references/internal-procedures/structure-planning/references/gates.md](references/internal-procedures/structure-planning/references/gates.md) |
-| Source density and coarse reading judgment | [references/internal-procedures/structure-planning/references/density-profile.md](references/internal-procedures/structure-planning/references/density-profile.md) |
-| Candidate anomalies, stable ids, paths, duplicates, and conflicts | [references/internal-procedures/structure-planning/references/candidate-resolution.md](references/internal-procedures/structure-planning/references/candidate-resolution.md) |
-
-</reference>
-
-<procedures>
-
-### Step 1 — Open Material Investigation
-
-Run:
-
-```bash
-context run align:<type>:<source>:<collection> --view read-plan --format json
-```
-
-Use the returned views, budgets, snapshot hash, and next actions. If the CLI
-reports a missing or stale snapshot, route back to source capture/refresh. Do
-not read the snapshot file yourself.
-
-### Step 2 — Read Evidence Through The Index
-
-Read a compact index before requesting exact spans:
-
-```bash
-context run align:<type>:<source>:<collection> --view source-index --compact --format json
-```
-
-For exact evidence, copy CLI-returned source refs or next commands:
-
-```bash
-context run align:<type>:<source>:<collection> --view span-detail --span <source-ref> --format json
-context run align:<type>:<source>:<collection> --view span-text --span <source-ref> --format json
-```
-
-Keep a short note of what evidence supports each proposed node, section, and
-edge. If the evidence is weak or conflicting, keep it as unresolved instead of
-turning it into a fact.
-
-Before drafting structure, read:
-
-- [references/internal-procedures/structure-planning.md](references/internal-procedures/structure-planning.md)
-- [references/internal-procedures/structure-planning/references/gates.md](references/internal-procedures/structure-planning/references/gates.md)
-- [references/internal-procedures/structure-planning/references/density-profile.md](references/internal-procedures/structure-planning/references/density-profile.md)
-- [references/internal-procedures/structure-planning/references/candidate-resolution.md](references/internal-procedures/structure-planning/references/candidate-resolution.md)
-
-Do not treat this as optional background. These files contain the current
-semantic gates for source-bound structure planning. A structure payload drafted
-without the applicable references is incomplete, even if the CLI schema accepts
-its shape.
-
-### Step 3 — Draft And Validate Structure
-
-Request the schema:
-
-```bash
-context run align:<type>:<source>:<collection> --view schema --format json
-```
-
-Create a `context.structure.v1` YAML file. The draft may include a one-page-per
-source shape, but that is represented as ordinary nodes and sections; it does
-not bypass structure confirmation.
-
-For small payloads, use stdin/heredoc. For larger payloads, write a scratch file
-under `.tmp/agent-payloads/<run-id>/` and pass it through `--input`. Scratch
-files are disposable agent working files; they are never phase state and
-must not be read back as a substitute for CLI views.
-
-Validate:
-
-```bash
-context run align:<type>:<source>:<collection> --validate --input <structure.yaml> --format json
-```
-
-Validation returns `structure_summary` and writes a temporary HTML report under
-`.tmp/context-runtime/reports/`. A validation report with
-`confirmation_ready=false` is an Agent repair artifact, not a user review gate:
-do not ask the user to approve it. The staged report produced after
-`confirmation_ready=true` is the final review surface; use its
-`structure_report.file_url` as the primary user-facing link and include
-`structure_report.absolute_path` as a copyable fallback.
-If the user needs a focused view, run:
-
-```bash
-context run align:<type>:<source>:<collection> --view structure-summary --input <structure.yaml> --format json
-```
-
-The CLI response may include a large full `structure_summary` for debugging and
-report rendering. For user confirmation, prioritize the first-screen fields:
-`review_notice`, `structure_report`, and `structure_summary_compact`. A valid
-user-facing confirmation prompt must include the report `file_url`, the absolute
-path fallback, and a compact summary of collections/views/unresolved/diagnostics.
-Do not ask the user to confirm from counts alone.
-
-Repair diagnostics by routing them to the right decision:
-
-- source ref or snapshot mismatch -> reread evidence views or refresh capture;
-- unsupported node/section/edge -> remove it or mark unresolved;
-- duplicate/conflict -> ask the user which structure should win;
-- illegal edge type, missing target node, or edge without source refs -> fix the
-  structure or keep the relation unresolved;
-- stale structure -> regenerate from the current snapshot hash.
-
-When validation returns `repair_confirmation_blockers`, follow its exact repair
-route without stopping for human confirmation. `--repair suggested-splits`
-mechanically splits non-contiguous source mirror Sections; write its
-`repaired_payload` to a scratch YAML file and validate again. For oversized
-Views, use the returned child-View and contains-edge suggestions, but classify
-each child Node from evidence instead of mechanically inheriting the parent
-type. Repair other diagnostics from evidence and validate again. Ask the user only when evidence
-supports multiple incompatible semantic choices, and label that question as a
-structure-design choice rather than final review. Do not stage until
-`confirmation_ready=true`.
-
-### Step 4 — Review Structure Before Confirmation
-
-After validation reports `confirmation_ready=true`, stage the draft. The stage
-command opens the final report. Then show the user:
-
-- node list and planned paths;
-- section ownership;
-- typed edges and unresolved relation candidates;
-- expected compile order;
-- downstream impact: these choices freeze paths, section ownership, and
-  relationships for this compile round.
-- the `structure_report.file_url` generated by validate or `--view
-  structure-summary`;
-- the `structure_report.absolute_path` fallback in case the host cannot click
-  file URLs.
-
-If the CLI stage result includes `next_action.human_gate: true`, treat it as a
-hard stop for structure review. Do not ask for a blind "confirm structure"
-reply. Surface the report `file_url`, absolute path, and enough structured
-summary for the user to inspect what will be confirmed.
-
-Do not turn `confirmation_blockers` into a preliminary approval round. A
-validator-required page split, continuous-source split, ref repair, or
-structure-spine connection is work to resolve before staging. If a genuinely
-ambiguous semantic choice needs the user, ask only that choice and then resume
-repair; it does not replace the final report-based confirmation.
-
-Use the host's multi-choice question tool when available. If unavailable, use a
-short Markdown fallback. Good options are:
-
-- Confirm this structure and continue to compile.
-- Revise the structure with additional guidance.
-- Go back to source scope or capture because the evidence set is wrong.
-
-Only after confirmation, run the CLI confirmation command, normally:
-
-```bash
-context run align:<type>:<source>:<collection> --confirm --format json
-```
-
-If confirming a structure file other than `unapproved/structure.yaml`, pass it
-with `--input <structure.yaml>`. A draft stage in `unapproved/structure.yaml` is
-not confirmation. Do not edit `unapproved/structure.yaml` after confirmation to
-change meaning; return to this gate instead.
-
-### Step 5 — Handoff To Compile
-
-After the user confirms the structure and the CLI reports `structure-ready` or
-`needs-prose-compile`, stop this procedure and follow:
-
-```text
-${CLAUDE_PLUGIN_ROOT}/skills/skill-prose-compile/SKILL.md
-```
-
-Do not keep editing structure while compiling. If compile diagnostics show the
-planned structure is wrong, return to this align gate and ask the user to
-confirm the corrected structure.
-
-### Step 6 — Self-verify Checklist
-
-- [ ] Evidence came only from Context evidence views.
-- [ ] `context.structure.v1` was validated before user confirmation.
-- [ ] User confirmed the structure before compile.
-- [ ] Compile was delegated to `skill-prose-compile`; this procedure did not
-  write draft page body.
-- [ ] Relationships are expressed as structure edges or unresolved items.
-- [ ] No direct edits were made to `sources/`, `.tmp`, `unapproved/`,
-  `knowledge/`, review HTML, or `dist/`.
-
-### Final Report
-
-Report in the user's language. Include only:
-
-- evidence views actually read;
-- proposed and confirmed node count, section count, edge count, and unresolved
-  count;
-- user confirmation outcome;
-- validation warnings that still matter for compile;
-- next route reported by status or the align phase.
-
-Do not report payload digests, snapshot hashes, source-ref hashes, absolute
-paths, or scratch file paths unless the CLI explicitly asks the user to repair
-one.
-
-</procedures>

package/plugin/skills/skill-prose-align/references/internal-procedures/structure-planning/references/candidate-resolution.md

@@ -1,91 +0,0 @@
-# Candidate Resolution Rules
-
-Use these rules after reading the current align evidence views and before
-authoring `context.structure.v1`. They define how current anomaly diagnostics
-map to supported structure outcomes.
-
-## Anomaly Signals
-
-Anomaly diagnostics are mechanical warnings. Do not ignore them and do not treat
-them as recommendations.
-
-For each anomaly, choose one current outcome and record the reasoning in the
-structure payload or user-facing explanation:
-
-| Outcome | Use When |
-|---|---|
-| Accept the correction | The anomaly points to a real structure fix. Apply a concrete node, section, edge, or ownership correction supported by source refs. |
-| Dismiss with rationale | The warning is mechanically true but semantically harmless. Keep the structure and state why in the confirmation summary. |
-| Keep unresolved | The warning changes structure but source evidence is insufficient. Add an `unresolved[]` item instead of guessing. |
-
-Known anomaly kinds:
-
-| Kind | Meaning | Required handling |
-|---|---|---|
-| Missing evidence | A proposed node, section, or edge has no source-backed evidence. | Add source refs, remove it, or keep the issue unresolved. |
-| Structure churn | A node was renamed, split, merged, replaced, or rejected during investigation. | Confirm the final id/title/target with the user or keep the ambiguity unresolved. |
-| Duplicate evidence | The same source ref appears more than once for the same semantic role. | Deduplicate it or explain why the repeated ref supports different roles. |
-| Broad review needed | The CLI collapsed many anomalies or reports aggregate risk. | Review the affected structure broadly; do not finalize solely from ordering. |
-
-## Stable References
-
-Use stable `node_ref`, `view_ref`, and `section_ref` values from the current
-`context.structure.v1` payload for in-payload references. A NodeRef should be
-safe, lower-case, and path-shaped, such as `entity/rspack` or
-`domain/build-tooling`. `slug` and `path` are derived fields in the current
-flow; do not invent alternate reference aliases.
-
-When an edge or section points at knowledge:
-
-- use the schema ref that matches the target layer:
-  `node_ref` for a conceptual Node, `view_ref` for a collection view, and
-  `section_ref` for a planned section;
-- ensure the target NodeRef, ViewRef, or SectionRef exists in the current
-  structure or approved knowledge;
-- keep relation hints unresolved when the target does not exist;
-- follow CLI diagnostics if a ref is unknown or stale.
-
-Do not create alternate alias fields or non-schema candidate ledger fields.
-They are not part of the current structure contract.
-
-## Visible Labels And Audit Rationale
-
-Humans need to understand merge, reject, rename, and replacement choices
-without decoding temporary ids. Keep that discipline in the current structure
-flow through current fields:
-
-- use `title` and `summary` to name the final node in user-facing language;
-- explain renamed/split/merged candidates in the confirmation summary, not by
-  adding non-schema label fields;
-- when a relation or rename cannot be settled from evidence, put the visible
-  title/target clue in `unresolved[]`;
-- when asking the user, phrase the choice with business labels ("Rspack build
-  tool page" vs "Webpack page"), not with source refs or internal section ids.
-
-NodeRef is the stable conceptual identity. ViewRef is the collection-specific
-view identity and is the durable approved-page identity. SectionRef is the
-stable planned-section identity under a ViewRef. Package paths are derived from
-the approved ViewRef plus containment/slug; do not treat paths as an alternate
-identity contract. Visible labels help humans review the choice, but they do
-not authorize a different NodeRef, ViewRef, edge, or section ownership without
-source-backed evidence and user confirmation.
-
-## Duplicate And Conflict Handling
-
-- Exact duplicate structure -> keep one node/section/edge and explain the
-  duplicate in the confirmation summary.
-- Same topic but different evidence boundary -> keep separate sections only
-  when each section has a distinct source-backed role.
-- Conflicting facts -> ask the user or keep an `unresolved[]` item. Do not
-  pick a winner from title order or source order.
-- Replacement or rename -> ask the user when it changes NodeRef, ViewRef,
-  containment, slug, or the derived approved path. These are durable user-facing
-  identities, not disposable labels.
-
-## Self-verify
-
-- [ ] Every accepted node, section, and edge has source-backed support.
-- [ ] Every unresolved relation or conflict is explicit in `unresolved[]`.
-- [ ] No non-schema candidate ledger fields or alias fields appear in the payload.
-- [ ] NodeRef, ViewRef, and SectionRef values, not temporary labels or paths,
-  are used for current references.

package/plugin/skills/skill-prose-align/references/internal-procedures/structure-planning/references/density-profile.md

@@ -1,30 +0,0 @@
-# Evidence Density Selection
-
-Use density as a private reading and section-planning strategy. It is not a
-separate payload, not a quality score, and not a workflow stage. Persist only
-current `context.structure.v1` fields such as `nodes[]`, `sections[]`,
-`source_refs[]`, `edges[]`, and `unresolved[]`.
-
-Apply this reference when a captured source is long, dense, fragmented, or hard
-to split into stable planned sections. Use the current CLI evidence views
-(`read-plan`, `source-index`, `span-detail`, `span-text`) to inspect material;
-do not invent a separate coarse-read artifact.
-
-| Profile | Use When | Agent Behavior |
-|---|---|---|
-| `macro` | A long source has many headings, sections, or broad topic shifts. | Create section proposals around major headings and preserve document-level anchors so later passes do not flatten scope. |
-| `meso` | Default for normal product, design, or operational documents with several related sections. | Produce section proposals for meaningful local units and preserve evidence anchors. |
-| `micro` | The source is fragmented, note-like, or dense with short independent claims. | Keep section proposals narrow and avoid bundling unrelated blocks into one candidate. |
-| `single_pass` | The source is short enough that one read can safely discover all relevant structure. | Keep anchors minimal and avoid over-segmentation, but still validate the resulting structure. |
-
-Treat Markdown heading changes as section-planning hints, not hard boundaries.
-Sibling sub-headings under a shared parent can remain in one planned section
-when they form one coherent semantic topic for that parent. Headings with no
-shared parent should usually split unless you intentionally want one section to
-span them. When a dense source has many headings, split by heading first, then
-merge adjacent or sibling groups only when the merged section is still one
-coherent fact group.
-
-Do not let density alone choose `node_type`, `tags`, `section.kind`, or body
-content. Action/domain gates are decided from source evidence and the current
-schema, not from density metadata.