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

package/indexers/bundles/context-note-indexer/context-indexer.yaml

@@ -1,6 +1,6 @@
 protocol: context.indexer.provider/v1
 id: context-note-indexer
-version: 1.0.0
+version: 1.0.1-alpha.1
 domains:
   - markdown
 activation:
@@ -85,7 +85,7 @@ provides:
     - decision-record
   logical_units:
     - id: reader-subject
-      identity: canonical-subject-key
+      identity: stable-article
       artifacts:
         recommended:
           - content
@@ -95,431 +95,62 @@ composition:
   extensions:
     - profile: note/monorepo-container
       extends: monorepo-container
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: project
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/web-application
       extends: web-application
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: application
-            local_key:
-              operator: canonical-module-identity
-          - id: capability
-            local_key:
-              operator: canonical-export-family
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/component-library
       extends: component-library
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: component
-            local_key:
-              operator: canonical-export-family
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/sdk-library
       extends: sdk-library
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: capability
-            local_key:
-              operator: canonical-export-family
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/cli-tool
       extends: cli-tool
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: command-family
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/plugin-extension
       extends: plugin-extension
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: extension
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/api-service
       extends: api-service
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: service
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/gateway-facade
       extends: gateway-facade
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: gateway
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/domain-service
       extends: domain-service
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: domain-capability
-            local_key:
-              operator: canonical-module-identity
-          - id: operation-entrypoint
-            local_key:
-              operator: canonical-export-family
-          - id: operation-flow
-            local_key:
-              operator: canonical-export-family
-          - id: runtime-context-family
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/background-runtime
       extends: background-runtime
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: runtime
-            local_key:
-              operator: canonical-module-identity
-          - id: scheduled-operation
-            local_key:
-              operator: canonical-export-family
-          - id: dispatch-contract
-            local_key:
-              operator: canonical-module-identity
-          - id: dependency-boundary
-            local_key:
-              operator: canonical-export-family
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/event-consumer
       extends: event-consumer
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: consumer
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/data-sync-reconciliation
       extends: data-sync-reconciliation
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: sync-pipeline
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/storage-repository
       extends: storage-repository
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: store
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/adapter-integration
       extends: adapter-integration
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: adapter
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/contract-source
       extends: contract-source
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-service-namespace
-        kinds:
-          - id: contract-family
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/derived-generated-source
       extends: derived-generated-source
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: generated-surface
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/domain-reference
       extends: domain-reference
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/product-requirements
       extends: product-requirements
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/technical-guide
       extends: technical-guide
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/user-and-developer-guide
       extends: user-and-developer-guide
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/public-api-reference
       extends: public-api-reference
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/runbook
       extends: runbook
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/faq-support
       extends: faq-support
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/standard-policy
       extends: standard-policy
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/decision-record
       extends: decision-record
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/incident-review
       extends: incident-review
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/test-validation
       extends: test-validation
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/release-migration-guide
       extends: release-migration-guide
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-section
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
     - profile: note/documentation-site
       extends: documentation-site
-      subject_key_schema:
-        version: 1
-        namespace:
-          operator: canonical-source-module-namespace
-        kinds:
-          - id: document-set
-            local_key:
-              operator: canonical-module-identity
-        normalization:
-          - trim
-          - unicode-nfc
-          - preserve-case
 provider:
   instructions:
     - path: references/indexer.md

package/indexers/bundles/context-note-indexer/references/classification.md

@@ -1,55 +1,28 @@
 # Choose the reader outcome
 
-Classify useful passages, not the entire file. Source type, reader-facing form
-and operation are independent choices. One source can correct an existing FAQ,
-add a decision explanation and contain irrelevant conversation at the same time.
-Explain classifications in the user's language in the work-start report; the
-profile IDs below are protocol identifiers, not headings for the reader.
+Read the saved material and compare its reader questions with the current
+article navigation, including topics originally discovered from code. A note
+or session may correct an existing answer, explain a decision, or justify a new
+article. Its filename and source type do not determine the article form.
 
-| Material and reader need | Suitable profile | Action |
-| --- | --- | --- |
-| A concrete question with a supported answer | faq-support | Update the matching answer; create only if the question is distinct |
-| A repeatable task with prerequisites and checks | technical-guide / user-and-developer-guide | Integrate steps into the existing guide or propose a missing task |
-| Operational diagnosis and recovery | runbook | Preserve symptoms, checks, safe actions and verification |
-| Confirmed choice with rationale and limits | decision-record | Explain the choice, applicability and meaningful alternatives |
-| Agreed intended behavior and acceptance conditions | product-requirements | Keep intended behavior distinct from current implementation |
-| A reusable term, relationship or domain rule | domain-reference | Define it with scope and useful examples |
-| An incident account supported by observations | incident-review | Separate observations, causes and unverified hypotheses |
-| A test method or reported validation result | test-validation | Retain method, scope and what the result actually demonstrates |
-| Repetition, superseded claims, unresolved speculation without reader value | No new target | Support, defer or exclude with a concrete reason |
-| A required reader outcome needs a capability this Provider does not supply | `unsupported` for the affected material | Name the actual missing capability using the current Route; report its scope and recovery |
+A question and supported answer can become a FAQ; repeatable steps belong in a
+guide or runbook; a confirmed choice needs rationale and limits; observations
+about an incident or test retain their actual scope. These are writing choices,
+not required profile registrations or fixed article counts.
 
-“FAQ”, “knowledge improvement” and “knowledge accumulation” are not three source
-storage types. FAQ is a reader form; improvement usually revises approved prose;
-accumulation may add a topic or enrich an existing one. Decide from the actual
-reader question and existing coverage. Never route every note/session into FAQ.
+Reuse the stable article identity when revising the same reader task. Similar
+titles alone do not establish that two articles should merge. Separate different
+versions or audiences when combining them would mislead readers. Several
+authorized sources may contribute to one article, regardless of which skills
+helped investigate them.
 
-Choose the closest applicable declared profile by reader task, then adapt its
-outline to the useful content. Headings, grouping and examples are writing
-choices, not new capabilities. An existing project template override takes
-precedence; use supported customization when a reusable local template is
-needed, not as a prerequisite for ordinary writing. Do not invent profile IDs
-or claim unsupported tools, source access or output contracts.
+Use the current plan submission for article targets and writing batches. A
+simple source can directly suggest its target; do not manufacture a separate
+per-passage classification ledger. Keep genuinely unfinished investigation in
+the stage's remaining scope. No independent article value may mean supporting
+an existing article, not excluding the source from all production.
 
-Reserve `unsupported` for a real capability gap that prevents the requested
-outcome within the authorized scope, not a mismatch with a stock outline. Name
-the missing capability in the current Route payload and explain which work is
-affected; follow its recovery instead of imposing an extra approval or stopping
-unrelated work yourself. Missing metadata or an unresolved claim can usually be
-bounded in useful prose. Request material only when the missing evidence is
-necessary to answer the reader's question; exclude material with no reader value.
-
-Reach for it rarely. The forms above are broad, and an awkward fit is not an
-absent one — a benchmark result is test-validation, a complaint with a supported
-answer is faq-support, an onboarding checklist is a guide. What decides is the
-reader question, not how the record happens to be laid out. A messy record, an
-unstated applicability boundary and an unfamiliar topic are none of them
-capability gaps; the first two are ordinary authoring work and the third is
-usually one of these forms under a name you have not seen before.
-
-Keep one subject identity for the same reader topic across updates. Two topics
-with the same title are not necessarily the same page; compare audience, scope
-and task. Do not merge different versions or platforms just to reduce page count.
-Conversely, do not split a coherent answer into thin pages because the source
-has many headings. Close the actual current inventory using the Route schema,
-including explicit dispositions for excluded material.
+Do not invent a tool capability or source authorization. Missing essential
+evidence is a scoped gap; an unfamiliar topic or imperfect stock outline is
+ordinary investigation and writing. Long-term exclusions need the applicable
+user authorization, not just a desire to finish sooner.

package/indexers/bundles/context-note-indexer/references/customization.md

@@ -1,36 +1,23 @@
-# Business replacement and customization
+# Choosing and adapting skills
 
-Enable the chosen skill through the host's ordinary skill switch. Install it
-through your organization's own channel; Context has no additional business
-skill installation or enabled registry. The Agent discovers currently visible
-`context-…-indexer…` skills, then reads their real SKILL.md and sibling
-context-indexer.yaml. A matching name is a discovery hint, not compatibility.
+Use relevant skills actually available in the current host. In planning,
+declare their names, usable entries when needed, and the scopes and purposes
+for which they help. The current stage returns that temporary guidance during
+planning and writing. A name is a discovery hint, not proof of semantic fitness.
 
-To replace a default, declare the business Provider as the primary for the
-selected requirement, using its observed version, supported profiles and actual
-distribution coordinates. Do not select the default too. Use the current
-Provider selection Route's host_visible_skills observation and indexers payload;
-let the host resolution action supply the actual bundle when requested. No host
-cache crawling or guessed version/integrity is needed.
+Adapt reader questions, grouping and outlines without registering a profile,
+verifying skill versions or hashes, or attaching a skill identity to formal
+articles. Multiple skills may complement one module or article. Use another
+available skill when it supplies useful interpretation; do not invent a
+missing capability or silently expand source permissions.
 
-For a reusable wording/template change, these defaults support instructions-append
-and template-override, not config or program-extend. Ordinary heading and grouping
-choices do not require customization. Follow the selected Provider's actual
-capabilities if it is a replacement. For independent
-source interpretation a standalone business Provider is appropriate. To enrich
-another primary, declare extension profiles and compatible fragments in its
-manifest and bind them with kind extension. The existing protocol validates
-these declarations; CLI never decides which business interpretation is best.
+A reusable specialist skill should describe its source interpretation,
+lightweight skeleton investigation, optional bounded helpers and writing
+guidance. Ordinary note/session work needs no parser program: read the supplied
+material and propose a target. Detailed source analysis belongs only where the
+current reader task needs it.
 
-An override is named by the declared template ID, not its bundle filename:
-`src/indexer/<indexer-id>/templates/note-faq-support.md` overrides
-`note-faq-support`, whose default file is `templates/faq-support.md`.
-Keep the required origin comment pointing to the selected skill, observed
-version and profile. The same local override and `instructions.md` apply to
-initial writing and approved-page revision; no separate revision template is needed.
-
-The default template is a writing aid, not a mandatory business taxonomy.
-Customize reader questions and examples without changing source identity,
-revision authority, provenance or the single-primary rule. Check an unrelated
-session, an excerpt with unavailable original, a rejected proposal, an existing
-page correction and a mixed-code target before distributing a replacement.
+When adapting guidance, check a source with an unavailable original, an
+unconfirmed proposal, a correction to an existing article and a mixed-code
+target. Preserve source strength, real citations and the current stage's file
+submission contract. Do not create persistent tool-selection or producer logs.

package/indexers/bundles/context-note-indexer/references/extension-placement.md

@@ -1,54 +1,28 @@
-# Where note material belongs in a base profile's page
+# Place supporting note material
 
-A `note/…` profile is an extension. It does not own a page and does not open a
-parallel one. The module stays on its base profile and selected page plan,
-including an applicable project template override. Contribute to the relevant
-sections; the attachment examples below are guidance, not a heading whitelist.
+Use the current article's reader question and supplied revision base, not a
+profile binding. Integrate relevant explanations into the appropriate sections
+without opening a parallel page or collecting everything under a generic
+"Notes" heading. The article can use several skills.
 
-Do not restate a base section the note has nothing to add to, and do not
-introduce a "notes" section to hold everything a note said.
-
-## What a note can establish that the base sources cannot
-
-Read the base profile's Chapter blueprint and notice which sections its own
-evidence can settle. Structure settles from code and contracts: entry points,
-signatures, registrations, schemas, dependency edges. Several sections in every
-base blueprint ask for something else — why a limit was chosen, what a timeout
-means for a caller, which combination is unsupported, what breaks on upgrade,
-which behavior is deliberate. Those are the sections a saved note is for.
-
-This is the useful division. If a note repeats a signature the code already
-establishes, it adds nothing and risks contradicting the authoritative source. If
-it carries a constraint, a known pitfall or an applicability boundary, it belongs
-in the section that asks for exactly that.
-
-## Attachment points by family
-
-| Family | Base profiles | Sections a note usually reaches |
-| --- | --- | --- |
-| Applications and containers | `monorepo-container`, `web-application` | `Dependency and layering constraints`, `Shared configuration and tooling`, `Configuration and environment selection`, `Known exclusions and source-of-truth links` |
-| Reusable capabilities | `component-library`, `sdk-library`, `cli-tool`, `plugin-extension` | `Compatibility and release constraints`, `Behavior, lifecycle, and errors`, `Recovery and rollback boundaries`, `Configuration, permissions, and isolation`, `Compatibility, failure, diagnostics, and recovery` |
-| Services and gateways | `api-service`, `gateway-facade`, `domain-service` | `Error, timeout, and compatibility behavior`, `Timeout, retry, compatibility, and failure translation`, `State, transaction, and idempotency behavior`, `Failure and recovery behavior`, `Configuration, observability, and release` |
-| Runtimes and data flow | `background-runtime`, `event-consumer`, `data-sync-reconciliation`, `storage-repository` | `Concurrency, ordering, retry, and idempotency`, `Idempotency, retry, checkpoint, and failure destination`, `Authentication, failure, retry, and fallback`, `Transaction, consistency, cache, and locking behavior`, `Failure recovery and observability` |
-| Boundaries and contracts | `adapter-integration`, `contract-source`, `derived-generated-source` | `Error, retry, fallback, and compatibility behavior`, `Versioning, compatibility, and deprecation`, `Generated versus maintained behavior`, `Compatibility and regeneration` |
-| Document profiles | `domain-reference`, `product-requirements`, `technical-guide`, `user-and-developer-guide`, `public-api-reference`, `runbook`, `faq-support`, `standard-policy`, `decision-record`, `incident-review`, `test-validation`, `release-migration-guide`, `documentation-site` | The base document blueprint keeps its shape; a note adds applicability, an exception, a correction or a missing definition |
-
-Read the section names from the actual base template the Route delivered. The
-table lists the sections these families most often need and is not the complete
-set; a base profile may declare a better-fitting section than the one named here.
+Code may establish entry points, signatures, registrations and current
+branches. Saved material can explain why a limit was chosen, an intentionally
+unsupported case, an operational exception or a known pitfall. Put those
+contributions where the reader needs them; do not repeat signatures or replace
+authoritative behavior with recollection.
 
 ## How the material reads once placed
 
-Attribute it. A base page's other sections are backed by code or contracts, so a
+Attribute it. An existing article's other sections are backed by code or contracts, so a
 sentence sourced from a note has to carry its own strength or a reader will
 assume the whole page is equally authoritative. "Recorded in an operations note:
 the retry limit was set to three to stay under the downstream quota" is placeable.
 "The retry limit is three" is not, unless the code establishes it — and if the
-code establishes it, the base section already owns that line.
+code establishes it, the existing section already owns that line.
 
 A note may report one occurrence or document an explicitly confirmed rule.
 Retain that distinction and its attribution. Qualify missing dates or versions
-where they affect the base section's meaning; do not generalize a single case
+where they affect the existing section's meaning; do not generalize a single case
 or demote a confirmed rule merely because either was saved as a note.
 
 When a note contradicts what the code establishes, do not silently pick one. The