@c4a/context-cli 0.7.9 → 0.7.10-alpha.2

package/plugins/skills/context-sessions-indexer/references/indexer.md

@@ -37,7 +37,7 @@ that limitation behind a change URL.
 
 ## Diagrams
 
-Use the materialized [diagram guidance](diagrams.md) when a diagram clarifies the reader task. This also applies to older templates, source diagrams and Composer summaries. Preserve source strength, version and external boundaries; diagram presence is not a completion requirement.
+Use the materialized [diagram guidance](diagrams.md) when a diagram clarifies the reader task. This also applies to source diagrams and combined articles. Preserve source strength, version and external boundaries; diagram presence is not a completion requirement.
 
 ## Existing source images and tables
 
@@ -45,4 +45,8 @@ For authorized visual material, follow [source visual processing](visual-source-
 
 ## Reading selected article material
 
-Use the current task's combined writing brief: it includes selected article guidance, examples when supplied, and section/variable slots. Profile bindings can share one article Markdown source; do not open every binding or regenerate every listed article. Keep short collaboration notes and examples beside the relevant guidance instead of requesting separate files. Read extra source or full technical contracts only when this task needs them. The CLI applies executable contracts and evidence bindings; the Agent decides applicability, substance and useful diagrams. Reuse an already-read unchanged shared resource while it remains in context.
+Read the current task's brief and source navigation; choose relevant examples
+and source passages rather than enumerating profile bindings. For a revision,
+use the supplied base article and references. Reuse unchanged shared material
+already in context. The CLI checks source authorization, regional references
+and safe writes; the Agent decides the topic, meaning and useful diagrams.

package/plugins/skills/context-sessions-indexer/references/updates-and-composition.md

@@ -1,37 +1,31 @@
 # Updates and composition
 
-First inspect the authorized existing knowledge and requested outcome. Saving
-input alone does not authorize a new indexing target. If a paragraph corrects
-an existing explanation, revise that approved page. Retain its useful steps,
-examples, images, limitations and confirmed contributions. If the material
-supports a new reader task, propose that topic through normal structure review
-before Author; never write directly to approved knowledge. If it adds nothing
-new, retain the source without producing a duplicate page.
+Start with existing article titles, descriptions and references. Read relevant
+article bodies or source passages when that navigation is insufficient. A
+correction belongs in the affected article; do not create a page merely to
+announce an improvement. A new reader question may justify a new target.
+Several authorized sources and skills may contribute to the same article.
+There is no primary-skill ownership or extension-profile binding to retain.
 
-Use one primary Provider per target. For an independent note/session topic this
-Provider may be primary with one of its declared document profiles. For an
-existing Code or Markdown page, retain that page's primary Provider. When this
-Provider's specialized interpretation is needed, select it as an extension
-layer and bind its prefixed extension profile to the active base profile, e.g.
-`sessions/component-library` extends `component-library`. `profile.additional`
-uses `kind: extension`, not `supporting`: supporting profiles belong to the
-same primary layer. Read actual manifests; do not invent a profile name for a
-business Provider.
+Use the current stage's plan submission to propose targets or append revision
+tasks. Preserve accepted articles; do not overwrite a successful task by
+resubmitting different content. Once a revision is issued, use its supplied
+base Markdown and reference table to edit only the necessary sections through
+the current submission schema. Keep useful unaffected examples and limitations.
 
-This is an instruction-only extension. Its selected references guide source
-interpretation in the primary task; it has no separate inspector/program and
-does not claim to emit machine fact fragments. It supplies source-backed
-distinctions, relevant reasons, conflicts and limits to the same writing task. It does not become a second author,
-replace the primary API table, or create a standalone session page merely
-because a source exists. Extend only the target's explicit evidence/read scope;
-a commit or URL in metadata does not authorize fetching it. If no extension is
-selected, the main Provider can still read authorized supporting material under
-its own guidance; do not silently enable an unavailable skill.
+Write drafts and submission files in the designated Agent temporary directory.
+Submit their paths through the current CLI action, not long shell arguments.
+The coordinator may submit a finished subset. Child Agents work only when the
+current host supports them and the issued directory permits that scheduling;
+they do not concurrently mutate shared production state.
 
-An incorrect source summary needs explicit correction by the host import flow,
-with current base_digest and task adjustment for pinned inputs. An accurate
-source but misleading page needs only approved-page revision. This Provider
-must not rewrite the original source to make a new page seem supported.
-A rejected revision leaves source material and approved content available for
-repair. Knowledge approval never changes upstream code, approves an MR, or
-turns a proposal into an adopted decision.
+An accurate source with a misleading article needs an article revision. An
+incorrect source needs the authorized source-import correction flow, not an
+Indexer quietly rewriting evidence. A source change invalidates affected task
+inputs; follow the CLI refresh action and preserve unrelated work.
+
+CLI acceptance saves a candidate for this run; it is not publication. Review
+rejection requires repair, not deletion of the article's responsibility.
+Temporary plans, candidates and receipts need not survive clearing temporary
+storage or changing machines. A new run starts from formal sources, confirmed
+long-term requirements and formal articles.

package/plugins/skills/context-sessions-indexer/references/writing.md

@@ -6,7 +6,7 @@ smallest source span supporting each claim; link the stored summary when that
 is all you read. Never pretend its original conversation or linked document was
 available. Missing originals limit confidence, not permission to invent detail.
 
-Select the declared profile template for the actual reader task. Its headings
+Choose an outline for the actual reader task; a supplied template is optional guidance. Its headings
 are prompts, not required empty sections. A FAQ answers a coherent reader question
 or related set of questions; a guide teaches a task; a decision explains a choice and its
 limits. Do not make one page per source heading or one page per input file.
@@ -56,8 +56,8 @@ only when writing choices cannot solve the missing capability. Explain an actual
 tooling gap and the available recovery in the user's language, outside the
 knowledge page; do not turn an unfamiliar topic into a request for a new Provider.
 
-Before returning the current Route payload, read the page as a reader: can they
+Before submitting the draft files, read the page as a reader: can they
 answer the selected question without reconstructing the conversation? Check
-that each meaningful source topic is included, supporting, deferred or excluded
-with a concrete reason. A generic overview that drops the actual decision,
+that the article answers its planned reader question. Keep remaining investigation
+and real gaps visible in the stage; do not submit a per-passage disposition ledger. A generic overview that drops the actual decision,
 exception or resolution is incomplete even if its headings look correct.

package/plugins/skills/context-sessions-indexer/tests/fixtures/profiles.json

@@ -20,14 +20,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-purpose"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-domain-reference-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-domain-reference-source"
     ]
   },
   {
@@ -51,14 +45,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-purpose"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-product-requirements-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-product-requirements-source"
     ]
   },
   {
@@ -82,14 +70,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-structure"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-technical-guide-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-technical-guide-source"
     ]
   },
   {
@@ -113,14 +95,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-operation"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-user-and-developer-guide-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-user-and-developer-guide-source"
     ]
   },
   {
@@ -144,14 +120,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-operation"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-runbook-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-runbook-source"
     ]
   },
   {
@@ -175,14 +145,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-purpose"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-faq-support-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-faq-support-source"
     ]
   },
   {
@@ -206,14 +170,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-purpose"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-decision-record-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-decision-record-source"
     ]
   },
   {
@@ -237,14 +195,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-operation"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-incident-review-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-incident-review-source"
     ]
   },
   {
@@ -268,14 +220,8 @@
         "purpose": "required",
         "reader_question_refs": [
           "question:reader-operation"
-        ],
-        "evidence_refs": [
-          "evidence:anonymous-test-validation-source"
         ]
       }
-    ],
-    "evidence_refs": [
-      "evidence:anonymous-test-validation-source"
     ]
   }
 ]

package/providers/context/actions/approve-production-report.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: approve-production-report
+runner: agent
+effect: write
+skill: skills/work-production-stage/SKILL.md

package/providers/context/actions/configure-production-requirements.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: configure-production-requirements
+runner: agent
+effect: write
+skill: skills/work-production-stage/SKILL.md

package/providers/context/actions/prepare-production-stage.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: prepare-production-stage
+runner: command
+effect: write
+command: context action prepare-current --format json

package/providers/context/actions/register-source-batch.yaml

@@ -1,6 +1,6 @@
 schema: agent-graph.action.v1
 id: register-source-batch
-description: Register the source batch after the complete work-start report was presented and the boundary was explicitly confirmed.
+description: Register the explicitly confirmed source boundary for capture and lightweight investigation.
 runner: command
 effect: write
 command: context source add batch --input .tmp/agent-payloads/source-batch.json --format json

package/providers/context/actions/run-indexer-lifecycle.yaml

@@ -1,6 +1,9 @@
 schema: agent-graph.action.v1
 id: run-indexer-lifecycle
-description: Continue the unique registry-and-Provider Indexer lifecycle until current Candidates exist.
+files:
+  - resources/manuals/guides/code-indexer-skill-authoring.md
+  - resources/manuals/guides/markdown-indexer-skill-authoring.md
+description: Continue the current directory-based investigation and article production Route.
 runner: agent
 effect: write
 skill: skills/run-indexer-lifecycle/SKILL.md

package/providers/context/actions/work-production-stage.yaml

@@ -0,0 +1,5 @@
+schema: agent-graph.action.v1
+id: work-production-stage
+runner: agent
+effect: write
+skill: skills/work-production-stage/SKILL.md

package/providers/context/codes.yaml

@@ -1,5 +1,15 @@
 schema: agent-graph.code-catalog.v1
 codes:
+  - { code: route.production.investigation-required, kind: route-reason, summary: Continue the remaining authorized investigation and append its article tasks. }
+  - { code: route.production.repair-required, kind: route-reason, summary: Add revision tasks for rejected planned articles before closing production. }
+  - { code: route.production.requirements-required, kind: route-reason, summary: Record confirmed reader purposes and authorized production sources. }
+  - { code: route.production.requirements-migration, kind: route-reason, summary: Preserve long-term requirements while removing legacy Provider configuration. }
+  - { code: route.production.planning-prepare, kind: route-reason, summary: Prepare lightweight navigation for confirmed requirements. }
+  - { code: route.production.planning-required, kind: route-reason, summary: Investigate source skeletons and submit article goals and batches. }
+  - { code: route.production.report-required, kind: route-reason, summary: Present the planned work-start report and wait for user feedback. }
+  - { code: route.production.prepare-required, kind: route-reason, summary: Prepare the next eligible production directories. }
+  - { code: route.production.writing-required, kind: route-reason, summary: Complete the issued production tasks using stage-local files. }
+  - { code: route.production.scope-incomplete, kind: route-reason, summary: Resolve remaining investigation and material gaps without discarding accepted articles. }
   - { code: route.version.content-changed, kind: route-reason, summary: Record an increasing workspace version and changelog for formal content changes. }
   - { code: route.workspace.recovery, kind: route-reason, summary: Inspect a stuck task independently of normal workflow evaluation., document: resources/procedures/task-recovery.md }
   - { code: route.indexer.maintenance, kind: route-reason, summary: Advance registered knowledge maintenance at a safe boundary., document: resources/procedures/knowledge-maintenance.md }
@@ -14,8 +24,6 @@ codes:
   - { code: route.workspace.project-entry-invalid, kind: route-reason, summary: Repair the Context project entry before continuing., document: resources/procedures/project-configuration.md }
   - { code: route.workspace.state-invalid, kind: route-reason, summary: Inspect and repair the invalid workspace facts., document: resources/diagnostics/workspace-state.md }
   - { code: route.verify.failed, kind: route-reason, summary: Resolve blocking verification findings before other lifecycle writes., document: resources/procedures/verify-and-repair.md }
-  - { code: route.evidence.decision-required, kind: route-reason, summary: A source-evidence change needs an explicit maintenance decision., document: resources/procedures/evidence-maintenance.md }
-  - { code: route.evidence.maintenance-required, kind: route-reason, summary: Apply the selected evidence-maintenance action., document: resources/procedures/evidence-maintenance.md }
   - { code: route.source.boundary-required, kind: route-reason, summary: No knowledge source boundary has been registered., document: resources/procedures/source-boundary.md }
   - { code: route.source.repository-not-ready, kind: route-reason, summary: A registered repository checkout or local source link must be restored., document: resources/procedures/repository-source-recovery.md }
   - { code: route.capture.configuration-required, kind: route-reason, summary: Registered document sources are missing capture declarations., document: resources/procedures/project-configuration.md }
@@ -73,11 +81,7 @@ codes:
   - { code: route.indexer.catalog-fallback, kind: route-reason, summary: Mechanically accept one deterministic catalog parent after semantic strategies are exhausted. }
   - { code: route.indexer.main-run-acceptance, kind: route-reason, summary: "Atomically accept one fully validated main Result, receipts, and ledger transition." }
   - { code: route.indexer.main-run-failure, kind: route-reason, summary: Persist one exact main run failure and its dependency digests. }
-  - { code: route.indexer.subject-catalog, kind: route-reason, summary: Merge approved Nodes and all validated primary partition group SubjectKeys. }
-  - { code: route.indexer.target-resolution, kind: route-reason, summary: Resolve enrich-or-independent groups by exact SubjectKey before authoring. }
   - { code: route.indexer.projected-artifact-fan-out, kind: route-reason, summary: Recompute projected Artifact ownership and Bundle eligibility before Candidate materialization. }
-  - { code: route.indexer.subject-key-validation, kind: route-reason, summary: Recompute SubjectKey schema authority and approved-Node identity compatibility. }
-  - { code: route.indexer.subject-reidentification, kind: route-reason, summary: Require a non-delegable confirmation for one exact collision-free breaking SubjectKey mapping. }
   - { code: route.indexer.author-worksets, kind: route-reason, summary: Build one immutable author workset for each validated partition group. }
   - { code: route.indexer.effective-composers, kind: route-reason, summary: "Resolve the exact selected, declared, and profile-applicable composer set." }
   - { code: route.indexer.post-author-worksets, kind: route-reason, summary: Materialize bounded composer worksets or publish an explicit not-required state. }
@@ -89,7 +93,6 @@ codes:
   - { code: route.indexer.post-author-composition, kind: route-reason, summary: Compose the current result envelope after every selected composer is accepted. }
   - { code: route.indexer.result-reconciliation, kind: route-reason, summary: Recompute per-domain completion and emit exact capability or material gaps before reporting success. }
   - { code: route.indexer.candidate-compile, kind: route-reason, summary: Compile Candidate Artifacts from the exact accepted author IndexerResult set and authorized layout. }
-  - { code: route.indexer.incremental-impact, kind: route-reason, summary: "Report exact logical-unit, Artifact, and Section impact from complete current Merkle dependency views." }
   - { code: route.indexer.candidate-review, kind: route-reason, summary: Review the exact current candidate set only after current mechanical validation passes. }
   - { code: route.indexer.approved-knowledge-close, kind: route-reason, summary: Atomically close approved Indexer structure after required material gaps are resolved. }
   - { code: route.indexer.source-update, kind: route-reason, summary: Inspect fixed source changes against current approved pages. }