@c4a/context-cli 0.7.10 → 0.7.11

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

@@ -7,6 +7,9 @@ and file navigation is a starting point, not a semantic grouping or a complete
 feature inventory. Inspect relevant manifests, public entry files, registrations,
 maintained documentation or a few representative declarations to understand
 which kinds of reader topics the module can support.
+For broad work, identify the main capability families across the authorized
+range before treating investigation as finished. A representative implementation
+can establish how to investigate a family, not that every family is covered.
 
 Technology-specific investigation may be direct Agent reading or a bounded
 helper from an available skill. A helper should expose feature names, counts
@@ -51,6 +54,9 @@ supply better business names and rationale; code paths are structural hints,
 not immutable topic names. Preserve stable article identity when the reader
 task is unchanged. Different platforms or deprecated entrypoints may need
 separate treatment even when names match.
+Before consolidating existing articles, read their relevant content. Preserve
+checked interfaces, relationships and examples; a shorter map must not replace
+them with instructions to rediscover the same knowledge.
 
 Submit article targets, reader questions, sources and batches with the current
 plan schema. Keep pending scope explicit when only part is investigated.
@@ -79,7 +85,11 @@ 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.
 An integration guide focuses on consumption; a maintenance guide may need
-internal transformations and recovery. Follow the actual reader purpose.
+internal transformations and recovery. For an entry-first task, provide a checked
+file or symbol, why it is relevant and a concrete next hop; a package name or
+generic instruction to search pages/handlers is not a problem-level entry.
+For an explanation, read the conditions, callers and implementation needed to
+answer it instead of substituting that investigation route for the answer.
 
 Read the source that establishes the claim. An outbound client is not an
 inbound service; host and remote declarations do not prove loading behavior.

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

@@ -9,7 +9,10 @@ contracts, conditions, examples, compatibility limits, images and uncertainty.
 An inventory of headings, a generic summary or a link back to the source does
 not replace an article that answers the reader. Preserve exact commands,
 identifiers, numbers and destinations where they matter; do not reproduce
-secrets or incidental conversion metadata.
+secrets or incidental conversion metadata. For an entry-first request, identify
+the relevant source section and concrete next step; for an operational guide,
+retain what lets the reader execute it. Do not replace available instructions
+with a generic suggestion to consult the original document.
 
 Use [editorial guidance](editorial-policy.md) for a concrete presentation
 problem. It is advice for the Agent and user, not a signal-clearing protocol or
@@ -47,7 +50,9 @@ the same article; no primary/extension ownership is required.
 
 Correct misleading knowledge through a revision. Correct an inaccurate source
 through its authorized import flow, not by editing evidence from this skill.
-Keep useful prior contributions and real gaps visible during updates.
+When merging or shortening existing articles, retain still-valid steps, examples
+and constraints in the article or a linked topic, not just their source links.
+Keep real gaps visible; material not yet obtained is not a permanent exclusion.
 
 ## Visual material
 

package/indexers/bundles/context-markdown-indexer/references/semantic-planning.md

@@ -14,15 +14,18 @@ Document business definitions may correct a mechanical code-topic name; explain
 the proposed change in the plan instead of forcing the document into a path
 mirror. This does not authorize renaming formal files outside the current task.
 
-A coherent document can directly suggest one target. A long document may need
-several articles; several documents may jointly answer one question. Neither
-file count nor heading count determines article count. Choose batches based
-on reader tasks, dependencies and useful shared reading, not source or skill
-identity. Do not create per-member dispositions or a separate semantic graph.
+A coherent document can directly suggest one target. Split distinct reader tasks
+or lifecycles; combine sources when they answer the same task. A shared broad
+label such as development or operations does not make all its procedures one
+summary. Neither file nor heading count determines article count. Choose batches
+by dependencies and useful shared reading, not source or skill identity. Do not
+create per-member dispositions or a separate semantic graph.
 
 Submit article targets, questions, authorized sources and batches through the
 current planning schema. Keep remaining investigation in pending_scopes when
-only part is ready. An unread source is unfinished, not implicitly excluded.
+only part is ready. Referencing one section does not settle a source's other
+useful tasks; describe those in the existing plan. An unread source is unfinished,
+not implicitly excluded.
 Missing essential evidence remains a scoped gap. Long-term exclusions need
 the applicable user authorization.