@c4a/context-cli 0.6.0-beta.6 → 0.6.0-beta.7

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@c4a/context-cli",
-  "version": "0.6.0-beta.6",
+  "version": "0.6.0-beta.7",
   "type": "module",
   "bin": {
     "context": "./cli.js"
   },
   "dependencies": {
-    "@c4a/context": "0.6.0-beta.6",
+    "@c4a/context": "0.6.0-beta.7",
     "commander": "^11.0.0",
     "handlebars": "^4.7.8",
     "ink": "^5.0.0",

package/plugin/skills/skill-continue-workflow/SKILL.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

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

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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.

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

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

package/plugins/VERSION

@@ -1 +1 @@
-0.6.0-beta.6
+0.6.0-beta.7

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

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
-  "version": "0.6.0-beta.6",
+  "version": "0.6.0-beta.7",
   "author": {
     "name": "c4a"
   },

package/plugins/claude/skills/skill-continue-workflow/SKILL.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

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

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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.

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

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

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

@@ -1,6 +1,6 @@
 {
   "name": "context",
-  "version": "0.6.0-beta.6",
+  "version": "0.6.0-beta.7",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "c4a"
@@ -18,7 +18,7 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "C4A Context",
-    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.0-beta.6",
+    "shortDescription": "Initialize and advance a local, source-linked project knowledge workspace.\nv0.6.0-beta.7",
     "longDescription": "Create a Context workspace and use agent-guided next steps to register sources, run extraction, review candidates, build package outputs, and verify health without silently mutating source repositories.",
     "developerName": "c4a",
     "category": "Productivity",

package/plugins/codex/skills/continue/references/internal-procedures/skill-continue-workflow.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

package/plugins/codex/skills/continue/references/internal-procedures/skill-prose-align.md

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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
   `skill-prose-compile.md`.
 - Compile, review, close, verify, and build remain separate gates.

package/plugins/codex/skills/continue/references/internal-procedures/skill-prose-compile.md

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

package/plugins/codex/skills/init/references/internal-procedures/skill-continue-workflow.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

package/plugins/codex/skills/init/references/internal-procedures/skill-prose-align.md

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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
   `skill-prose-compile.md`.
 - Compile, review, close, verify, and build remain separate gates.

package/plugins/codex/skills/init/references/internal-procedures/skill-prose-compile.md

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

package/plugins/cursor/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "context",
   "displayName": "C4A Context",
-  "version": "0.6.0-beta.6",
+  "version": "0.6.0-beta.7",
   "description": "Maintain a project-local knowledge workspace through init and next-step agent guidance.",
   "author": {
     "name": "Context4AI",

package/plugins/cursor/skills/skill-continue-workflow/SKILL.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

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

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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
   `../skill-prose-compile/SKILL.md`.
 - Compile, review, close, verify, and build remain separate gates.

package/plugins/cursor/skills/skill-prose-compile/SKILL.md

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

package/plugins/skills/context-continue/references/internal-procedures/skill-continue-workflow.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

package/plugins/skills/context-continue/references/internal-procedures/skill-prose-align.md

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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
   `skill-prose-compile.md`.
 - Compile, review, close, verify, and build remain separate gates.

package/plugins/skills/context-continue/references/internal-procedures/skill-prose-compile.md

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.

package/plugins/skills/context-init/references/internal-procedures/skill-continue-workflow.md

@@ -24,6 +24,10 @@ Continue an existing Context workspace from its current state.
   workflow; do not treat the host repository root as the workspace.
 - There is no `context continue` CLI command. Start with `context status`.
 - `context status` and CLI diagnostics are the source of truth.
+- Inspect `declarationGraph` and `configurationGaps`. Before structure
+  confirmation they are configuration warnings; after confirmation, a missing
+  compile route is a hard gate. Never substitute a compile phase from another
+  collection.
 - Execute safe mechanical `next:` steps; stop at semantic choices and human
   gates.
 - Delegate source/scope decisions to

package/plugins/skills/context-init/references/internal-procedures/skill-prose-align.md

@@ -24,16 +24,17 @@ Turn captured document evidence into confirmed structure.
 - 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 the current procedure
-  references listed by the CLI as `semantic_reference_files`. These references
-  are the current structure judgment rules, not summaries.
+  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. If
-  the relevant `semantic_reference_files` have not been read in the current
-  turn, stop and read them first.
+- 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
   `skill-prose-compile.md`.
 - Compile, review, close, verify, and build remain separate gates.

package/plugins/skills/context-init/references/internal-procedures/skill-prose-compile.md

@@ -38,12 +38,13 @@ Compile confirmed document structure into reviewable draft knowledge.
   faithful mirrored continuous span, split the section or return to prose align
   for a confirmed structure change.
 - Before choosing section kind, summary, skip/update, weak-evidence handling, or
-  structure repair, read the current procedure references listed by the CLI as
-  `semantic_reference_files`. These are the migrated compile judgment rules, not
-  summaries.
-- Do not produce or validate compile actions from this entry file alone. If the
-  relevant `semantic_reference_files` have not been read in the current turn,
-  stop and read them first.
+  structure repair, read only the procedure references in the CLI
+  `semantic_rules.required` set. The CLI selects core and conditional rules for
+  the current node and explains each selection with `reason`.
+- Do not produce or validate compile actions 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`.
 
 <reference>
 
@@ -162,9 +163,10 @@ context run compile:<type>:<source>:<collection> --view node-context --source <v
 context run compile:<type>:<source>:<collection> --view schema --format json
 ```
 
-Read the compile references listed by `semantic_reference_files` before
+Read only the compile references listed by `semantic_rules.required` before
 classifying section kind, summary, support, skip/update, weak evidence, or
-structure repair.
+structure repair. Do not load the full rule inventory unless the CLI explicitly
+returns it as required.
 
 Do not treat those references as optional background. They are the current
 compile drafting, judgment, and semantic-repair procedures.