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

package/indexers/bundles/context-code-indexer/references/indexer.md

@@ -61,6 +61,20 @@ returned action; accepted content needs a revision task.
 
 ## Writing follows actual behavior
 
+For a large module, divide work by reader question or capability family, not
+by an exhaustive symbol list. Put useful directory and entrypoint hints in the
+task brief. Investigate one bounded slice first and keep remaining scope in the
+existing plan; do not wait for a module-wide catalog before writing. Reuse shared
+findings in temporary files across related tasks, checking source evidence for
+new claims. If a task proves too broad, amend unfinished tasks rather than
+expanding every dependency recursively. A complete component manual still needs
+coverage of its agreed components, spread across manageable tasks.
+
+Use explicit file selections for optional deep analysis. Package export tracing
+can still follow other files to establish public identity, so selected output
+does not guarantee a cheap scan. Prefer direct reading when that traversal is
+unnecessary; stop or narrow a helper that exceeds the useful time/output budget.
+
 Explain what the module is responsible for, when and how to enter it through
 stable interfaces, what it hands off, and the relevant state and failure
 boundaries. A directory summary or symbol list is not an explanation.

package/indexers/bundles/context-code-indexer/templates/adapter-integration.md

@@ -11,7 +11,7 @@ compatibility layers, gateways, and translators whose stable responsibility is
 to connect two boundaries. An ordinary internal helper that converts one object
 is not automatically an adapter module.
 
-Use the exact profile and Artifact policy variant supplied by the workset. For
+Follow the current task.md, sources.md and submission schema. For
 an inbound operation surface, combine this template with the selected gateway
 or protocol evidence without creating a second operation registry.
 

package/indexers/bundles/context-code-indexer/templates/api-service.md

@@ -11,7 +11,7 @@ surface as `api-service`. A module that only calls a remote API is a protocol
 consumer, not automatically an API service. Gateways that translate to another
 protocol normally also selects `adapter-integration`.
 
-Use the exact profile and Artifact policy variant supplied by the workset. If
+Follow the current task.md, sources.md and submission schema. If
 the reader goal is primarily the transformation between inbound and outbound
 boundaries, use the selected adapter-integration profile and retain one
 canonical operation registry.

package/indexers/bundles/context-code-indexer/templates/background-runtime.md

@@ -10,7 +10,7 @@ Use for `background-runtime`: queue or stream consumers, scheduled jobs,
 pipelines, functions, controllers, watchers, and long-running agents activated
 by a trigger instead of an interactive request.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 

package/indexers/bundles/context-code-indexer/templates/cli-tool.md

@@ -11,7 +11,7 @@ executables, generators, and command-driven plugin hosts. A build script used
 only internally does not need a CLI knowledge unit unless it is a supported
 operator or contributor surface.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 

package/indexers/bundles/context-code-indexer/templates/component-library.md

@@ -12,7 +12,7 @@ imports and component contracts. A web application that happens to contain
 shared components remains a `web-application` unless the component surface is
 published as an independent consumer boundary.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 
@@ -30,10 +30,10 @@ Treat stories and examples as usage evidence, not as authority for unsupported
 props or behavior. When generated declarations disagree with source, identify
 the authoritative source and record the gap.
 
-When the Authorized Workset View supplies a public declaration together with
+When the task's authorized sources supply a public declaration together with
 structured props, events, defaults, variants, maintained examples, or source
-roles, the corresponding reader section must consume those facts or record an
-explicit supported omission/material-gap disposition. Do not replace available
+roles, use the relevant facts in the reader section and explain essential
+missing material. Do not replace available
 contract facts with a generic statement about the component directory. A component group
 without a reader-authorizing public declaration remains catalog-only and does
 not produce an empty component page. Library and system subjects may instead be

package/indexers/bundles/context-code-indexer/templates/contract-source.md

@@ -11,7 +11,7 @@ IDL, OpenAPI document, schema registry, message contract, or equivalent
 machine-readable interface definition. It defines contracts consumed by other
 modules but does not need to execute or dispatch them itself.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 Generated projections must point back to this authority and remain supporting
 evidence rather than a second contract authority.
 

package/indexers/bundles/context-code-indexer/templates/data-sync-reconciliation.md

@@ -52,16 +52,14 @@ Examples include application-to-client-to-endpoint, endpoint-to-service-to-
 repository, producer-to-event-to-consumer, command-to-remote-operation, and
 plugin-host-to-provider.
 
-## Partition and ownership rule
+## Article scope and source reuse
 
-A flow normally cites sources already owned by module units. Give the flow one
-stable article identity and keep module inventory ownership unchanged; its author
-workset may reference the exact cross-source evidence views but must not claim
-the same inventory members as a second primary owner.
+A flow may reuse sources cited by module articles. Give the flow one stable
+article identity and use the current task's authorized sources. No primary
+owner or inventory membership is required; avoid duplicating existing prose.
 
-The aggregate candidate may cite evidence from every participating source. It
-must cover all Route-reported structural probes selected by the flow profile;
-one page may cover several probes when it carries each exact evidence locator.
+The article may cite every authorized participating source. Cover the reader
+question and relevant handoffs defined in the task brief.
 Explain operations and handoffs in reader prose, links or diagrams, citing the
 actual source regions for each fragment (at most three locations per fragment).
 Do not emit graph edges, classify nodes or create a relationship ledger.

package/indexers/bundles/context-code-indexer/templates/domain-service.md

@@ -11,7 +11,7 @@ reusable service contract and its first-level orchestration. Do not classify a
 directory as a service merely because it contains classes or functions named
 `Service`.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 

package/indexers/bundles/context-code-indexer/templates/monorepo-container.md

@@ -11,7 +11,7 @@ registration, ownership, dependency, build, or release topology of multiple
 child modules. Do not treat the physical repository as one application merely
 because it has one Git remote.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 

package/indexers/bundles/context-code-indexer/templates/sdk-library.md

@@ -11,8 +11,7 @@ SDKs, public framework extensions, or shared runtimes consumed through a
 deliberately supported interface. A package being imported elsewhere is not
 enough; confirm its supported entry and consumer contract.
 
-Use the exact sdk-library or component-library profile and Artifact policy
-variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass
 

package/indexers/bundles/context-code-indexer/templates/web-application.md

@@ -15,7 +15,7 @@ only browser code. It does
 not automatically cover every package containing UI components; a reusable
 component package is usually `sdk-library`.
 
-Use the exact profile and Artifact policy variant supplied by the workset.
+Follow the current task.md, sources.md and submission schema.
 
 ## Evidence pass