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

package/templates/aspects/code/aspect.yaml

@@ -0,0 +1,21 @@
+schema_version: "1.0"
+name: code
+runner:
+  package: "@c4a/extract"
+  bin: c4a-extract-code
+plugins:
+  - package: "@c4a/extract-ts"
+    export: TypeScriptPlugin
+output:
+  bucket: raw/aspect/code/<source-slug>/<snapshot-id>/
+  files:
+    - source.yaml
+    - manifest.json
+    - digests.jsonl
+    - source-files.jsonl
+    - packages.jsonl
+    - symbols.jsonl
+    - edges.jsonl
+    - _meta.yaml
+evidence:
+  mode: none

package/templates/aspects/code/prompt.md

@@ -1,29 +1,44 @@
 # aspect: code
 
-> Code structure aspect. The `context capture-code` command invokes the
-> `@c4a/extract` / `@c4a/extract-ts` pipeline directly — it does not read
-> this file. The prompt exists as a placeholder so the init flow is
-> uniform and so a future scripted-aspect mechanism can take over without
-> reshuffling directory structure.
+> Code structure aspect. The public entrypoint is `context capture --code`.
 
 ## Target
 
-Extract `Package` / `Symbol` nodes and `imports` / `calls` / `extends` edges
-from the current git worktree.
+Extract package, symbol, edge, digest, and source-file rows from the local
+worktree. The runner reads JSON from stdin and returns NDJSON events; the
+context CLI owns `.context` writes.
 
-## Schema
+## Raw Snapshot
 
-Payloads are written by the CLI as JSONL files under each dated bucket:
+Each capture writes a source-scoped bucket:
 
-- `packages.jsonl` — one `Package` per line
-- `symbols.jsonl` — one `Symbol` per line (recursive `members` flattened)
-- `edges.jsonl` — one relation per line (optional)
-- `_meta.yaml` — bucket metadata (`commit`, `captured_at`, `script_hash`,
-  `content_hash`)
+```text
+raw/aspect/code/<source-slug>/<snapshot-id>/
+```
+
+The bucket contains:
+
+- `source.yaml` — local source identity and publish upsert hints
+- `manifest.json` — snapshot identity, runner hash, counts, and content hash
+- `digests.jsonl` — module digest rows with `hash_id`, `module_path`, and `dir_commit`
+- `source-files.jsonl` — service-compatible source file mapping
+- `packages.jsonl` — flat package/module view
+- `symbols.jsonl` — flat symbol view, with nested members flattened
+- `edges.jsonl` — flat code relation view
+- `_meta.yaml` — compact copy of snapshot metadata for legacy readers
 
 ## Notes
 
-- Currently driven by the CLI, not by a per-aspect script. The scripted
-  `capture.ts` contract for non-code aspects is planned for a later release.
-- source-id is always `aspect:code`.
-- Bucket name is `YYYY-MM-DD-<sha7>` where `<sha7>` is `git rev-parse --short HEAD`.
+- New writes use `aspect:code:<source-slug>` as the source id.
+- Repeated captures of the same commit, script hash, and snapshot content are
+  reported as unchanged and do not create duplicate snapshots.
+- Dirty worktrees are allowed; dirty module rows keep the real `dir_commit`
+  and use a content-sensitive `hash_id`.
+- The code aspect uses `evidence.mode: none`: it does not generate
+  `raw/.evidence` block manifests. Symbols, files, and edges are already
+  represented by the bucket JSONL indexes.
+- Formal code DSL query and logical code `source_ref` support are tracked by a
+  later version; this aspect only prepares the raw snapshot contract.
+- Runner raw extraction results are intentionally not written as a separate
+  bucket file. Future consumers should read `digests.jsonl` and the flat
+  package/symbol/edge projections instead.

package/templates/aspects/design-system/prompt.md

@@ -1,9 +1,8 @@
 # aspect: design-system
 
 > Design-system aspect placeholder. The current CLI does not yet provide
-> a scripted capture driver for this aspect — `context capture-aspect
-> design-system` will report that scripted aspects beyond `code` are not
-> implemented. This file exists so the init flow keeps the aspect slot
+> a scripted capture driver for this aspect. Only code capture is exposed
+> today via `context capture --code`. This file exists so the init flow keeps the aspect slot
 > consistent for a future scripted-capture release.
 
 ## Target

package/templates/aspects/graphql/prompt.md

@@ -1,8 +1,8 @@
 # aspect: graphql
 
 > GraphQL aspect placeholder. The current CLI does not yet provide a
-> scripted capture driver — `context capture-aspect graphql` will report
-> that scripted aspects beyond `code` are not implemented.
+> scripted capture driver for this aspect; only code capture is exposed via
+> `context capture --code`.
 
 ## Target
 

package/templates/aspects/openapi/prompt.md

@@ -1,8 +1,8 @@
 # aspect: openapi
 
 > OpenAPI aspect placeholder. The current CLI does not yet provide a
-> scripted capture driver — `context capture-aspect openapi` will report
-> that scripted aspects beyond `code` are not implemented.
+> scripted capture driver for this aspect; only code capture is exposed via
+> `context capture --code`.
 
 ## Target
 

package/plugin/.claude-plugin/plugin.json

@@ -1,16 +0,0 @@
-{
-  "name": "context",
-  "description": "Context For AI — local knowledge workspace. Capture docs, extract code structure, compile into an interlinked wiki with source-traced facts. CLI does mechanical work; agent drives compile/drop via skill protocols.",
-  "version": "0.5.29-alpha.2",
-  "author": {
-    "name": "c4a"
-  },
-  "license": "MIT",
-  "keywords": [
-    "context",
-    "knowledge-base",
-    "wiki",
-    "claude-plugin",
-    "c4a"
-  ]
-}

package/plugin/.codex-plugin/plugin.json

@@ -1,35 +0,0 @@
-{
-  "name": "context",
-  "version": "0.5.29-alpha.2",
-  "description": "Context For AI — local knowledge workspace. Capture docs, extract code structure, compile into source-traced local knowledge, query with citations, and govern source updates.",
-  "author": {
-    "name": "c4a"
-  },
-  "homepage": "https://github.com/context4ai/c4a",
-  "repository": "https://github.com/context4ai/c4a/tree/main/packages/context-cli",
-  "license": "MIT",
-  "keywords": [
-    "context",
-    "knowledge-base",
-    "codex-plugin",
-    "agent-skills",
-    "c4a"
-  ],
-  "skills": "./skills/",
-  "interface": {
-    "displayName": "C4A Context",
-    "shortDescription": "Local knowledge workspace skills for C4A.",
-    "longDescription": "Use the context CLI and bundled skills to capture project sources, align them to a Node tree, compile source-traced local knowledge, query with citations, and govern source drop or refresh workflows.",
-    "developerName": "c4a",
-    "category": "Productivity",
-    "capabilities": [
-      "Read",
-      "Write"
-    ],
-    "websiteURL": "https://github.com/context4ai/c4a",
-    "defaultPrompt": [
-      "Use C4A Context to answer from local knowledge with citations.",
-      "Use C4A Context to compile newly captured sources into local knowledge."
-    ]
-  }
-}

package/plugin/commands/capture-aspect.md

@@ -1,17 +0,0 @@
----
-description: "Run a named aspect capture pipeline. Stub in the current CLI — every invocation exits non-zero with 'planned for a future release'."
-argument-hint: "<aspect-name>"
-allowed-tools: Bash(context:*)
----
-
-## Your task
-
-`capture-aspect` is a placeholder. Every invocation, including `capture-aspect code`, exits non-zero with a deferred-to-a-future-release message; the pluggable aspect pipeline lands later.
-
-Run `context capture-aspect $ARGUMENTS` and relay the CLI's exit code + stderr verbatim. Do NOT route `code` to `/context:capture-code` — the two commands have different semantics, and the stub intentionally blocks this entry point so future aspect kinds land behind one consistent surface.
-
-Users who actually want to snapshot the repo's code structure today should be told to run `/context:capture-code` directly; mention it as a pointer in your reply. Do not auto-invoke it.
-
-Language policy: your explanatory prose follows the user's conversation language. Relay CLI stderr/stdout verbatim; command names, paths, source-ids, and quoted CLI phrases stay as printed.
-
-Never work around the stub by shelling into extraction directly or writing into workspace `raw/aspect/<name>/` by hand — the CLI is the sole writer of `raw/`.

package/plugin/commands/capture-code.md

@@ -1,25 +0,0 @@
----
-description: "Extract TypeScript code structure (Package / Symbol / Edge) from the current git repository into raw/aspect/code/."
-argument-hint: ""
-allowed-tools: Bash(context:*)
----
-
-## Your task
-
-Run `context capture-code` from anywhere inside the workspace — the CLI always scans the resolved workspace root, not the current subdirectory, so invoking it from a subfolder like `apps/web/src/` still snapshots the full repo. The CLI:
-
-- Requires the workspace to live inside a git checkout (needs `HEAD` sha).
-- Writes a bucket `raw/aspect/code/<YYYY-MM-DD>-<sha7>/` containing `packages.jsonl`, `symbols.jsonl`, `edges.jsonl`, `_meta.yaml`.
-- Updates `raw/aspect/code/latest` symlink and registers the snapshot in `raw/_sources.yaml` under source-id `aspect:code` (snapshots array entry carries `commit` + `script_hash`). Raw-side audit is kept via `_sources.yaml` snapshots + git history — the standalone `log.md` from earlier CLI generations is no longer maintained.
-- Skips with `unchanged, skipped` when the commit + script hash combination has already been captured.
-- Refuses with an actionable error when extraction finds zero scannable packages (rather than writing an empty bucket that Compile would later mistake for the full repo).
-
-Report whether a new bucket was produced or the run was a skipped idempotent re-run. When a fresh bucket lands, suggest the right next step:
-
-- Run `context workspace locate --format json` and use `ctxDir` as `WORKSPACE_DIR`.
-- `WORKSPACE_DIR/output/align.md` does not exist → suggest `/context:align` (code snapshot becomes align / compile material, but compile requires the structural plan from align first).
-- `WORKSPACE_DIR/output/align.md` exists → suggest `/context:compile`.
-
-Language policy: your explanatory prose follows the user's conversation language. CLI output, paths, source-ids, command names, commit hashes, and status tokens such as `unchanged, skipped` stay as printed.
-
-Do NOT write workspace `raw/aspect/code/` directly — only the CLI mutates that tree.

package/plugin/skills/align-finalize/SKILL.md

@@ -1,137 +0,0 @@
----
-name: align-finalize
-description: >
-  Third skill of `/context:align`. Reconciles `WORKSPACE_DIR/output/align.propose.yaml`
-  with the user's `WORKSPACE_DIR/output/align.user-decisions.yaml`, applies every pick
-  (ambiguous / orphan / accept-reject / addition / rename), re-validates
-  the tree against identity / establishment / tag / mount / layout rules,
-  and writes the final AlignRenderInput YAML. The CLI renders
-  `WORKSPACE_DIR/output/align.md` and binds raw mentions to `WORKSPACE_DIR/output/bind.yaml`.
-  Activates after the user has reviewed `align.propose.md` and written
-  their decisions file.
-tools:
-  - Read
-  - Bash
----
-
-# align-finalize — apply user decisions, emit the final plan
-
-Reconcile propose YAML with user-decisions YAML, settle every
-ambiguity, and produce the final `AlignRenderInput`. The CLI does
-all rendering.
-
-`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
-
-- Inputs must both exist: `output/align.propose.yaml` (CLI render) + `output/align.user-decisions.yaml` (user pick), read through `context workspace read`. Missing → stop and say which one.
-- Output: final `AlignRenderInput` passed to `context align --finalize -`; add `--save-input` when the caller wants a durable scratch copy.
-- Respect user decisions literally; a demoted candidate does not appear in `nodes[]` even if you disagreed during propose.
-- `type` values are closed to `domain / entity / action / concept` (see [Node types](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#node-types)); reject anything else rather than silently mapping.
-- Domain hard rule: no Node sits inline under a Domain file; every child of a Domain is a standalone root (see [Layout rules](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#layout-rules)).
-- `planned_sections[]` must satisfy the [Section mount matrix](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#section-mount-matrix) for each Node's type.
-- Slugs reuse across loops for `existing` / `modified`; new slugs only for `new`; user rename decisions carry through verbatim.
-- Every edge endpoint references a slug in `nodes[]`; no dangling edges.
-- No cycles across `contains` + `refines`; user-decision-induced cycles reject with the cycle path.
-- User decisions are business-intent answers; map them back to the closed model yourself instead of asking follow-up questions with model terms.
-- Output language: user-facing prose and `decisions.notes` match the user's language; slug / tag / type / edge values stay English.
-
-<reference>
-
-## User-decisions shape
-
-```yaml
-decisions:
-  ambiguous:
-    - phrase: "..."
-      choice: A                         # A / B / other
-      custom: { ... }                    # optional for "other"
-  orphans:
-    - slug: "..."
-      choice: deprecate                  # deprecate | keep | modify | supersede
-      new_status: deprecated
-      valid_until: <date>
-      supersede_with: <slug>              # when choice=supersede
-  new_candidates:
-    - name: "..."
-      choice: accept                     # accept | reject | reclassify
-      reclassify: { type: ..., tags: [...] }
-      rename: <new-slug>                  # optional
-  additions:
-    - name: "..."
-      suggested_type: ...
-      suggested_tags: [...]
-```
-
-Missing sections = "no change from propose". Read tolerantly.
-
-## Action establishment recheck
-
-User decisions can drop an Action below its establishment bar (e.g.
-rejecting a sub-Action leaves the parent with a single Section
-intent). After applying all decisions, re-verify every `action` Node
-against [Node establishment thresholds](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#node-establishment-thresholds). Below bar → leave the Node in place (the user made the call) but flag the weakness in `decisions.notes`. The caller's next `context doctor` pass (run at the end of `/context:align`) surfaces the note via the output-align diagnostic group, giving the user a chance to reopen the decision on the next loop.
-
-## Alias carry-through
-
-For every `new` Node, carry over the aliases the raw called it by
-(derived from scan mentions) so the close-time glossary build picks
-them up. Without aliases, later retrieval misses language variants.
-
-</reference>
-
-<procedures>
-
-### Step 1 — Load inputs
-
-Read `output/align.propose.yaml` and `output/align.user-decisions.yaml` in full with `context workspace read <path> --format text`. Build a `decisions` lookup keyed by slug / phrase / name. If either file is missing, stop and name it.
-
-### Step 2 — Apply `new_candidates` decisions
-
-For each propose `new` candidate:
-
-- `accept` → keep in the plan.
-- `reject` → drop from the plan; its mentions still show in `bind.yaml` as unbound raw.
-- `reclassify` → swap `type` + `tags`; re-check tags per the [Entity tag groups](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#entity-tag-groups) and concept gate rules.
-- `rename` → change `slug` / `title`; propagate to every edge + parent pointer.
-
-### Step 3 — Apply `ambiguous` decisions
-
-Pick the matching candidate per the user's `choice`; drop the others. `custom` branches go through Step 2's `reclassify` path.
-
-### Step 4 — Apply `orphans` decisions
-
-- `keep` → `status: existing`, no change.
-- `deprecate` → `status: orphan` + copy `new_status` / `valid_until`.
-- `modify` → `status: modified` + record intent in `decisions.notes`.
-- `supersede` → `status: orphan` on the old slug + add a new Node for the supersession target from `supersede_with`.
-
-### Step 5 — Apply `additions`
-
-For every user addition, run it through the same gates as propose ([establishment](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#node-establishment-thresholds), [tag rules](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#entity-tag-groups), [concept gate](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#concept-three-test-gate)). Gate failure → surface to the caller; the user needs to revise. Do not silently drop.
-
-### Step 6 — Fill and verify `planned_sections[]`
-
-Carry propose's hint when set; extend from raw evidence only with kinds that satisfy the [Section mount matrix](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#section-mount-matrix) for the Node's type. Drop mismatches and note them in `decisions.notes`.
-
-### Step 7 — Layout + cycle check
-
-- Confirm no Node carries a `contains_parent` that would require inline nesting under a Domain (see [Layout rules](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#layout-rules)).
-- Run a cycle check over `contains` + `refines`. Any cycle → reject with the offending path in the output; do not auto-break.
-
-### Step 8 — Write the final input
-
-Emit the confirmed `AlignRenderInput` shape (same shape as align-propose's output) for the caller to pass to `context align --finalize -` (or `context align --finalize - --save-input` when a durable scratch copy is needed). Return control to the caller.
-
-### Step 9 — Self-verify
-
-- [ ] Every `type` is one of the four closed values — if not, **Step 2/3/5**.
-- [ ] Every `entity` has ≥1 A/B tag — if not, **Step 2/3/5**.
-- [ ] Every `action` cleared the establishment bar OR carries a `decisions.notes` override — if not, **Step 2**.
-- [ ] Every `planned_sections[]` entry is legal for the Node type — if not, **Step 6**.
-- [ ] No Node sits inline under a Domain — if any, **Step 7**.
-- [ ] No cycles — if any, **Step 7**.
-- [ ] Every edge endpoint appears in `nodes[]` — if not, **Step 8**.
-- [ ] No Read / Glob / Grep / Write was used against `WORKSPACE_DIR` — if any, restart with `context workspace` / `context mdrive` commands.
-
-</procedures>

package/plugin/skills/align-propose/SKILL.md

@@ -1,163 +0,0 @@
----
-name: align-propose
-description: >
-  Second skill of `/context:align`. Reads the align-scan decisions file +
-  the existing `knowledge/` contains tree from `context mdrive query
-  --contains-tree --format json`, assembles a candidate Node tree, validates every candidate
-  against identity / establishment / tag / Edge rules, marks each node
-  new / existing / modified / orphan, and writes an AlignRenderInput
-  YAML. The CLI renders `WORKSPACE_DIR/output/align.propose.md` + `.yaml` for the user
-  to review. Activates when align-scan decisions are on disk and the
-  pipeline needs a reviewable tree before align-finalize.
-tools:
-  - Read
-  - Bash
----
-
-# align-propose — assemble a reviewable Node tree
-
-Promote classified mentions into a contains-rooted tree with explicit
-Edges, applying the identity / establishment / tag rules. Output is
-pure YAML; the CLI does the rendering.
-
-`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
-
-- Input: `output/align.scan-decisions.json` read through `context workspace read` + the current contains tree from `context mdrive query --contains-tree --format json`.
-- Output: an `AlignRenderInput` passed to `context align --propose -`; add `--save-input` when the caller wants a durable scratch copy.
-- Every candidate carries a `status` (see [Status markers](#status-markers)); `new` is never the default.
-- Entity candidates pass [Entity tag groups](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#entity-tag-groups); re-route false Entities per [False-Entity smell](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#false-entity-smell).
-- Action candidates clear [Node establishment thresholds](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#node-establishment-thresholds); below-bar demote to Section suggestions.
-- Concept candidates pass the [Concept three-test gate](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#concept-three-test-gate); failures demote.
-- Edges come from the five logical types only (see [Edge types](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#edge-types)); `refers_to_nodes` is a Section field, not an Edge.
-- No `contains` edge from a Domain to a Node that would nest inline — Domain children are always standalone files (see [Layout rules](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#layout-rules)).
-- No cycles in `contains` + `refines`.
-- Slugs are kebab-case, ≤60 chars, stable across loops.
-- User review questions follow `${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/user-question-contract.md`: ask for business intent, never storage mechanics.
-- Output language: user-facing prose and `decisions.notes` match the user's language; slugs / tag / type / edge values stay English.
-
-<reference>
-
-## Status markers
-
-| marker | When to use |
-|---|---|
-| `existing` | Exact slug / title match in workspace AND raw does not contradict the glossary entry |
-| `new` | No existing Node; raw material justifies creating it |
-| `modified` | Matches an existing Node AND raw adds information (new Sections incoming, or raw flips a decision) |
-| `orphan` | Existing Node whose raw footprint says sunset / deprecated / superseded; user decides deprecate / keep / supersede |
-
-## AlignRenderInput shape
-
-```yaml
-workspace: <workspace-name>
-nodes:
-  - slug: <kebab-case>
-    type: domain | entity | action | concept
-    tags: [...]
-    title: <human title>
-    sources: [<source-id>, ...]
-    aliases: [...]
-    summary: <optional one-liner>
-    status: new | existing | modified | orphan
-    contains_parent: <slug, optional>
-    planned_sections: [description, spec, warning]
-edges:
-  - type: contains | depends_on | realizes | refines | related_to
-    from: <slug>
-    to: <slug>
-    note: <optional>
-decisions:
-  notes: |
-    <brief rationale + demotions + unresolved questions>
-  new_candidates:
-    - slug: <accepted-node-slug>
-      mentions:
-        - file: <raw-file>
-          line: <line-number>
-          quote: <verbatim raw quote>
-  demotions:
-    - heading: <candidate or heading that was not promoted>
-      outcome: kept as Section | merged into <slug> | ignored as navigation
-      mentions:
-        - file: <raw-file>
-          line: <line-number>
-          quote: <verbatim raw quote>
-  ambiguous: [ ... carried from scan + discovered re-routes ... ]
-  orphans:   [ ... carried from scan ... ]
-```
-
-## User-review shape
-
-The CLI renders the proposal to `align.propose.md`. Shape your output
-so the caller can ask a small number of business-intent questions. The
-user should never need to know the internal Node / Section / Edge model.
-
-1. **Same thing or separate topic?** Pre-resolve with the identity tests.
-   Surface only hard cases in `decisions.ambiguous[]`.
-2. **Standalone lookup or parent detail?** Set the internal parent / demotion
-   fields yourself. Ask the user only when future user-visible lookup or
-   organization is unclear.
-3. **Business relationship?** Ask only when raw evidence leaves multiple
-   plausible meanings, such as alternatives vs dependency vs co-location.
-4. **Validity change?** Ask when old and new source documents conflict about
-   what readers should trust now.
-5. **Navigation-only duplication?** Do not ask. Repeated "Related links",
-   "References", and similar blocks are handled as structure unless they carry
-   new business prose.
-
-</reference>
-
-<procedures>
-
-### Step 1 — Load inputs
-
-1. Read `output/align.scan-decisions.json` with `context workspace read output/align.scan-decisions.json --format text`.
-2. Run `context mdrive query --contains-tree --format json` and use the returned `nodes[]` + `edges[]` as the current workspace skeleton. `contains` edges encode both same-file heading children and cross-file `## Contains` links; do not rebuild the tree with Glob + Read.
-
-### Step 2 — Seat `existing_nodes`
-
-Copy every `existing` entry into `nodes[]` with its current parent pointer from the tree. Set `status: existing`, or `modified` if new mentions imply incoming Sections. Do not re-parent without explicit raw evidence.
-
-### Step 3 — Promote new candidates
-
-For each `new_candidates[]` from `output/align.scan-decisions.json`:
-
-1. Check [Node establishment thresholds](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#node-establishment-thresholds). Below bar → skip the Node; record a Section demotion in `decisions.notes`.
-2. For `entity`, verify tags per the data-model reference. Neither-group hits → re-route via [False-Entity smell](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#false-entity-smell) into `decisions.ambiguous[]`.
-3. For `concept`, run the [Concept three-test gate](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#concept-three-test-gate). Any ❌ → demote; do not emit.
-4. Pick `contains_parent` from the scan's `suggested_parent` or a matching existing Domain.
-5. Fill `planned_sections[]` only where raw clearly justifies kinds that fit the target type per the [Section mount matrix](${CLAUDE_PLUGIN_ROOT}/skills/align-scan/references/data-model.md#section-mount-matrix).
-6. For every candidate you promote into `nodes[]`, copy its raw `mentions[]`
-   into `decisions.new_candidates[]` under the final `slug`. For every
-   candidate or heading you do not promote, add `decisions.demotions[]` with
-   the raw mention and the outcome. These are review evidence, not new
-   summaries.
-
-### Step 4 — Enumerate edges
-
-One `edges[]` entry per `contains` edge in the tree. Add `depends_on` / `realizes` / `refines` / `related_to` only where raw explicitly justifies the relationship AND both endpoints appear in `nodes[]`. Never emit `refers_to_nodes`-style edges. Run a cycle check over `contains` + `refines`; reject any cycle.
-
-### Step 5 — Carry ambiguous and orphans
-
-Copy `scan.ambiguous[]` into `decisions.ambiguous[]` plus any discoveries from Step 3 re-routes. Copy `scan.orphans[]` into `decisions.orphans[]`. Do not make deprecation calls yourself; the user decides in the next gate.
-
-### Step 6 — Write the proposal input
-
-Emit the [AlignRenderInput shape](#alignrenderinput-shape) as YAML for the caller to pass to `context align --propose -` (or `context align --propose - --save-input` when a durable scratch copy is needed). Return control to the caller; the caller renders `align.propose.md` + `.yaml`.
-
-### Step 7 — Self-verify
-
-- [ ] Every `entity` has ≥1 A/B tag — if not, **Step 3**.
-- [ ] Every `action` clears the establishment bar OR is demoted — if not, **Step 3**.
-- [ ] Every `concept` passes the three-test gate — if not, **Step 3**.
-- [ ] Every promoted new candidate has `decisions.new_candidates[].mentions[]` copied from scan evidence — if not, **Step 3**.
-- [ ] Every demoted candidate/heading has `decisions.demotions[]` with raw mentions — if not, **Step 3**.
-- [ ] No cycles in `contains` + `refines` — if any, **Step 4**.
-- [ ] No `refers_to_nodes` edges — if any, **Step 4**.
-- [ ] No `new` slug collides with an existing slug — if any, treat as `modified` in **Step 3**.
-- [ ] `decisions.ambiguous[]` + `decisions.orphans[]` carried through — if not, **Step 5**.
-- [ ] No Read / Glob / Grep / Write was used against `WORKSPACE_DIR` — if any, restart with `context workspace` / `context mdrive` commands.
-
-</procedures>