@c4a/context-cli 0.6.1-beta.1 → 0.6.1-beta.2

package/plugins/claude/skills/skill-prose-align/SKILL.md

@@ -1,322 +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.
-- When status is `captured-ready-to-classify`, run every returned capture-phase
-  evidence command before editing `src/index.ts`. Use the collection-neutral
-  title tree, span index, and exact text to propose a mainline collection; wait
-  for user confirmation, then declare matching align/compile/review phases.
-- 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 semantic judgment, use the CLI `semantic-rules` View to page through
-  only `semantic_rules.required`. Use each selection `reason` to keep unrelated
-  rules out of the current judgment.
-- Plan source evidence as Sections before promoting any heading to a Node/View.
-  Promotion depends on source-backed standalone retrieval identity, not on a
-  hard-coded section kind or collection name.
-- 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, resume the CLI rule-page sequence.
-- 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 |
-|---|---|---|
-| Collection classification | "I have inspected the captured evidence. Based on these source characteristics, I recommend this knowledge category; please confirm before I configure compilation." | Guessing from a filename, URL, or SDK collection enum before investigation |
-| 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
-
-`skill-continue-workflow` owns global state routing; this Skill owns only the
-align phase selected by that route. Use CLI evidence/rule/diagnostic Views,
-follow their exact continuation commands, and treat hints as subordinate to
-`next_action`. Evidence reads may be parallel; stage, confirm, Review apply,
-close, and build writes remain serial. Never reconstruct digest values or
-inspect CLI-managed state files as a substitute for a View.
-- 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.
-
-When the current conversation explicitly authorizes fully managed operation,
-use the CLI-returned `--stage --managed` command after successful validation.
-The CLI records `confirmed_by: managed-session`; validation errors and unresolved
-evidence still block confirmation. Never persist managed mode in `defineProject`
-or reuse it in another 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 a compact 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 explicit `structure-summary` View returns the full summary for focused
-debugging. For user confirmation, prioritize the default 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/plugins/claude/skills/skill-prose-align/references/internal-procedures/structure-planning/references/gates.md

@@ -1,263 +0,0 @@
-# Node Classification Gates
-
-Use these gates before every structure draft and before authoring the align
-payload described by the current schema view.
-Align owns Node type, tag, graph, planned Section, and ownership classification. It does **not** write Section prose.
-
-Current schema mapping:
-
-- Treat the action checklist, domain checklist, and inference tables as private
-  working notes unless the current schema view explicitly exposes matching
-  fields.
-- In `context.structure.v1`, persist the outcome through `node_type`, `tags`,
-  `summary`, `ownership`, `sections[].source_refs`, `edges[]`, and
-  `unresolved[]`.
-- Do not add unknown gate fields to the payload just because this procedure uses
-  them for reasoning.
-
-## Node Type Order
-
-Answer in this order and stop at the first match:
-
-1. **Action?** A large executable event / process with both:
-   - scale: can support `planned_sections` with at least two distinct Section kinds, or contains at least one child Action;
-   - process evidence: explicit steps, phases, trigger -> handling -> result, role collaboration, or repeatable plan. Parallel lists such as "three API modes" are not process evidence.
-   Single-section user-story / scenario / incident records may be meaningful to
-   a human reader, but the CLI does not infer that exception from source prose.
-   If the structure cannot express at least two distinct Section kinds or a
-   child Action, keep the material as a Section under the owning Node.
-2. **Entity?** A concrete independent subject with retrieval value: deployable code, product/application/system, library/module/CLI/symbol, or an atomic term/pattern.
-3. **Domain?** A container/scope that groups at least one child Node.
-4. Otherwise do not create a Node; leave the material for compile as a Section under the owning Node.
-
-Good examples:
-
-| Type | Examples |
-|---|---|
-| `domain` | "X business domain", "Y technical area", "Z research topic" |
-| `entity` concrete | `@acme/api-server`, `@acme/ui-kit` `Button`, "X sub-application" |
-| `entity` term | "X identifier", "Y business metric", idempotency |
-| `action` | "user submits X request end-to-end flow", "operator executes Y change flow", "team Z release flow" |
-
-## Title and Source Heading Rules
-
-Classify the Node by the evidence referent, not by the source file title, heading, or local section title. A source title is ordinary evidence just like body prose. It has no automatic right to become `node.title`, `aliases[]`, or `slug`.
-
-After choosing `node_type`, choose the title to fit that type:
-
-| Final type | Title shape |
-|---|---|
-| `entity` concrete | The concrete product, service, library, module, CLI, symbol, application, or system name. |
-| `entity` term | The atomic concept or pattern name, without extra scope/process suffixes. |
-| `domain` | The grouping scope that owns child Nodes. |
-| `action` | The executable process / runbook / flow name that passed the Action Gate. |
-
-Scope/process words in a source title are warning signals when proposed as an Entity title, not hard classification rules. Re-check the type/title when a proposed Entity title contains words such as "方案", "架构", "体系", "演练", "流程", "策略", "能力", "机制", "framework", "architecture", "system", "strategy", "process", or "drill". Keep the wording only when evidence shows it is the formal name of a concrete object or an atomic term.
-
-Do not promote broad architecture/system/方案 content to `domain` just because it sounds like a scope. When the source has writable Sections but no resolvable current/existing child Nodes, use an Entity such as `[system]` or `[application]` and put the architecture facts in Sections. Use `domain` only when it groups child Nodes through supported `edges[]`.
-
-Relation-only sources should not force title copying or dangling graph edges. Decide placeholder handling in this order:
-
-1. If resolved current/existing child Nodes make the page a real grouping scope, keep the relation evidence as supported `edges[]` only when the Domain also has at least one source-backed planned Section.
-2. If an explicit user-facing retrieval need or graph need makes the source/page identity valuable, and the title names an atomic concept or concrete object, keep that identity in `unresolved[]` until it has source-backed section evidence, a valid generated `parent_index` view with source-backed `contains` edges to child views, or a compile-time `skip` decision. Do not submit root-level `planned_sections: []` or ordinary source-bound `sections: []`.
-3. Otherwise, skip navigation-only / placeholder-only material; keep a short
-   `unresolved[]` note only when the deferred relation remains useful.
-
-Do not create a hidden domain-gate object. A kept placeholder needs support:
-source refs, approved graph support, or explicit user-confirmed retrieval value.
-For Domain placeholders, write only resolved current/existing children as typed
-`edges[]`; if all children are unresolved/deferred relation clues, keep those
-target hints in `unresolved[]`. If the source names only an atomic concept and
-that term is useful on its own, prefer a concise term Entity title without
-scope/process suffixes.
-
-For no-write placeholder summaries, describe only the preserved page identity and unresolved navigation clues. Do not say the Node "provides navigation/links/relations to X" unless those targets are resolved graph children or rendered links; say the source contains deferred navigation clues instead.
-
-## Section Promotion Gate
-
-Classify local evidence as a Section before creating a child Node/View. A
-heading, table row, FAQ label, or short sub-topic does not by itself establish a
-standalone page.
-
-Promote a Section to a child View only when at least one condition is supported
-by source evidence:
-
-1. The title is a concrete product/code object/system/module/library, not just a
-   local heading.
-2. The item is an atomic term or pattern that answers standalone lookup
-   questions outside the parent page.
-3. The item clears the Action Gate or Domain Gate.
-4. The source gives it independent article identity: owner/date, lifecycle,
-   timeline, tracking record, or cross-cutting support scope.
-
-Use one content-neutral test for every proposed child View: does cited evidence
-support an independent subject identity, enough context to stand alone, and a
-separate retrieval need? A heading, section kind, collection name, or contains
-edge is not sufficient by itself. The CLI warns when many same-source,
-single-section child Entities look mechanically fragmented, but it does not
-reject a page merely because of its content type.
-
-## Entity Tag Rules
-
-Use `tags` to state what the Entity is. Legal combinations:
-
-| Case | Tags |
-|---|---|
-| Runtime/code object | one A tag: `app`, `service`, `lib`, `cli`, `module`, or `symbol` |
-| Product-analysis object | one B tag: `application` or `system` |
-| Code + product object | one A tag plus one B tag |
-| Pure term / pattern | only `term` |
-
-`term` is mutually exclusive with A/B tags. React is `[lib]`, not `[lib, term]`; if a separate term entry is useful, create another Entity tagged `[term]` and let the structure plan express the relation as a typed edge or unresolved relation with `source_refs[]`.
-
-Do not inherit scope tags mechanically. If a parent Entity is tagged `system` or
-`application`, a child Entity should repeat that tag only when it is itself an
-independent system/application. Local aspects under that parent should either
-use their own shape tag or remain Sections.
-
-## Action Gate
-
-Use `node_type: action` only after the Node Type Order says action. Fill the
-action reasoning checklist in your working notes; persist only fields accepted by
-the current structure schema.
-
-The action probe uses five booleans as a reasoning checklist, but the semantic
-bar is:
-
-| Field | Meaning | Evidence rule |
-|---|---|---|
-| `has_steps_or_phases` | Process evidence exists: steps, phases, trigger -> handling -> result, role collaboration, or repeatable plan. | Hard requirement; support it from span evidence. |
-| `has_actor_or_role` | A user, system, operator, service, or role performs the work. | May be inferred; record the source. |
-| `has_outcome_or_goal` | The process has a target result, acceptance condition, or operational goal. | May be inferred; record the source. |
-| `is_repeatable_or_planned` | The work is repeatable, scheduled, policy-like, or intentionally planned. | May be inferred; record the source. |
-| `queries_answerable_with_refs` | The Node can answer how/when/who/what-to-do questions from cited spans. | May be inferred; record the source. |
-
-Do not emit an Action for a single sentence, a one-off conclusion, a short operation, or a parallel enumeration. Those become Sections under the owning Entity or Domain. The CLI does not infer single-Section Action exceptions from source prose; represent the material with enough structure or keep it as a Section.
-
-Action anti-examples:
-
-| Candidate | Correct routing |
-|---|---|
-| "migrate to X tool" as one conclusion | `decision` Section under the owning Entity |
-| "component X usage" as one sentence | `description` + maybe `example` under X |
-| "submit -> validate -> generate" as one unexpanded sentence | `spec` Section under X/Y |
-| "three API call modes" | `comparison`, `spec`, or `description` Section; not Action |
-
-## Fake Entity Gate
-
-A relationship-style title is only suspicious by itself. Downgrade or change type when at least **two** signals are true:
-
-1. Title contains relationship language such as "X impact on Y", "Y under X", "Y side of X", "X migration", or "X collection".
-2. No legal Entity tag fits.
-3. The Node does not stand alone away from its upstream Node.
-
-Repairs:
-
-| Pattern | Repair |
-|---|---|
-| "X impact on Y" | Section under X plus a typed edge or unresolved relation to Y when the evidence supports it |
-| "Y under X condition" | Section under Y; X is a condition in the Section body |
-| "X subsystem migration" | Action only if it clears the Action Gate; otherwise `decision` Section under X |
-| "X error collection" / "X FAQ collection" | `faq` / `incident` Sections under X |
-
-## Domain Gate
-
-Use `node_type: domain` only for a scope that groups child Nodes. Keep this
-domain reasoning checklist in working notes and persist supported relations through current
-`edges[]` or `unresolved[]`:
-
-| Field | Meaning |
-|---|---|
-| `scope_refs[]` | Source refs that describe the scope boundary or grouping. |
-| `child_refs[]` | Working-note candidate ids, local refs, or final slugs for children in the scope; persist valid ones as `edges[]`. |
-| `grouping_reason` | Why these children belong together under this domain. |
-
-If a domain has no resolvable child refs, no clear grouping reason, or only one same-file child without a broader scope, do not emit a Domain. For navigation-only / placeholder-only sources with only deferred children, skip the Node after ruling out standalone retrieval or graph value for an atomic-term or concrete Entity; keep only useful unresolved relation notes. Emit an Entity only when evidence names an atomic term or concrete object and choose its Entity tag yourself. The CLI rejects invalid Domain gates; it does not auto-downgrade a Domain or choose fallback tags.
-
-Scope-name titles such as "X 业务域", "Y 领域", "business domain", or "technical area" are a warning sign when proposed as Entity. Keep them as Entity only when the subject is an atomic term or concrete object; otherwise use Domain with supported child edges or unresolved relation hints.
-
-## Edge Gate
-
-Use a typed edge only when all four checks pass:
-
-1. Both `from` and `to` nodes exist in the current structure or approved
-   knowledge.
-2. The relation type is in the current closed set (`is_a`, `contains`,
-   `depends_on`, `corresponds_to`, `causes`, `triggers`, `prerequisite`,
-   `applies_to`, `verified_by`, `supersedes`).
-3. `source_refs[]` cite evidence for the relation itself, not just for one
-   endpoint.
-4. The relation is stronger than a vague "related" hint.
-
-If any check fails, write an `unresolved[]` item instead of an edge.
-
-If the source sentence states the relation with uncertainty, keep the edge only
-when the uncertainty is source-authored and preserved through
-`confidence: possible` or `confidence: hypothesis`. Do not use `confidence` for
-Agent uncertainty. If you are uncertain whether the evidence supports the
-relation, write `unresolved[]` instead.
-
-## Inference Sources
-
-Inference sources are working notes for the action reasoning checklist; do not
-persist this object unless the current schema explicitly exposes it:
-
-```yaml
-inference_sources:
-  actor:
-    source_type: explicit-span
-    source_refs: ["file:docs/runbook.md#span:steps L10-18@<span-hash>"]
-    rationale: "The span names the operator role."
-  outcome_or_goal:
-    source_type: inferred-from-span
-    source_refs: ["file:docs/runbook.md#span:steps L10-18@<span-hash>"]
-    rationale: "The span describes recovery as the expected result."
-  repeatability_or_plan:
-    source_type: heading-and-span
-    source_refs: ["file:docs/runbook.md#span:steps L10-18@<span-hash>"]
-    rationale: "The runbook heading and ordered list indicate planned reuse."
-  answerability:
-    source_type: explicit-span
-    source_refs: ["file:docs/runbook.md#span:steps L10-18@<span-hash>"]
-    rationale: "The steps answer how the operation is performed."
-```
-
-Allowed `source_type` values:
-
-| Value | Use when |
-|---|---|
-| `explicit-span` | The evidence span directly states the signal. |
-| `heading-and-span` | The heading plus span text together support the signal. |
-| `ref-node` | An existing or same-decision Node reference supplies the signal. Include `ref_nodes`. |
-| `inferred-from-span` | The signal is inferred from span content. Keep the rationale short and concrete. |
-
-Each source must include `rationale` when inferred and at least one of `source_refs[]` or `ref_nodes[]`.
-
-## Final Reflection
-
-- Entity cannot pick a legal tag, or depends on its upstream title to make sense -> write it as a Section under the upstream Node or change type before submit.
-- Action only supports one Section -> write it as a Section instead of an Action, or add source-backed structure that reaches at least two distinct Section kinds / one child Action. The CLI does not use source prose keywords to grant an exception.
-- Action "steps" are parallel options/configs -> route to Entity `comparison` / `spec` / `description`.
-- Domain has no children -> delete it or merge it into a larger Domain.
-
-## Current CLI Quality Diagnostics
-
-Current `context.structure.v1` validation preserves the old Node quality
-checks as deterministic diagnostics:
-
-| Diagnostic | Meaning | Required response |
-|---|---|---|
-| `schema.section_kind_invalid` | A planned Section uses a kind outside the current prose kind set. | Replace it with a kind from the schema view; do not invent local kind names. |
-| `schema.section_kind_mount_invalid` | A planned Section kind cannot be mounted on the chosen `node_type`. | Choose a kind allowed by the mount matrix, or reclassify the Node before confirming structure. |
-| `tags.term_conflict` | An Entity uses `term` together with concrete runtime/product tags such as `lib`, `service`, `application`, or `system`. | Split the term from the concrete object, or remove the conflicting tag before staging. |
-| `node.description_dominates` | A non-Action Node has at least half of its planned Sections as `description`. | Re-run kind precision. Keep it only when source evidence is genuinely narrative; otherwise split into `example`, `spec`, `comparison`, `faq`, `incident`, `decision`, `warning`, or `principle`. |
-| `node.thin_concrete_entity` | A concrete Entity has one Section and no child Nodes. | Keep it only when it has stable standalone retrieval value; otherwise merge it into the owning Node. |
-| `node.children_should_be_sections` | One parent contains many same-source, single-section child Entities with no stable shape tag. | Merge those children into parent Sections unless the user confirms each child has standalone lookup value. |
-| `node.term_expanded_beyond_definition` | A `term` Entity has grown past a compact definition or owns children. | Move rules, procedures, designs, and examples to the owning Node; keep the term entry narrow. |
-| `node.action_too_thin` | An Action has fewer than two distinct planned Section kinds and no child Action. | Downgrade it to a Section under the owning Node, add a distinct Section kind, or add a child Action; the CLI does not infer a single-section exception from source text. |
-| `node.domain_without_children` | A Domain has no source-backed `contains` child edge. | Add supported children, keep an explicitly confirmed no-write placeholder, or reclassify the Node. |
-| `tags.child_inherits_system` | A child Entity repeats its parent `system` / `application` scope tag. | Retag by the child’s own shape/scope, or keep the child as a Section if it is only a local aspect. |
-| `edge.confidence_invalid` | An edge declares a confidence value outside the current schema. | Use only `possible` or `hypothesis`, or omit the field for source-certain relations. |
-
-Warnings are not automatic blockers, but they are not suggestions to ignore.
-Resolve them or include the user-confirmed rationale when confirming structure.