npm - @c4a/context-cli - Versions diffs - 0.7.8 → 0.7.10-alpha.1 - Mend

@c4a/context-cli 0.7.8 → 0.7.10-alpha.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1386) hide show

package/indexers/bundles/context-markdown-indexer/context-indexer.yaml CHANGED Viewed

@@ -1,6 +1,6 @@
 protocol: context.indexer.provider/v1
 id: context-markdown-indexer
-version: 1.1.3
+version: 1.1.4-alpha.1
 domains:
   - markdown
 activation:
@@ -67,7 +67,7 @@ provides:
     - decision-record
   logical_units:
     - id: reader-subject
-      identity: canonical-subject-key
+      identity: stable-article
       artifacts:
         recommended:
           - content
@@ -545,441 +545,441 @@ provider:
       delivery: selected
     - id: domain-reference-c01-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-c01-page.md
+      path: templates/articles/c01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/c01.md
     - id: technical-guide-c01-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-c01-page.md
+      path: templates/articles/c01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/c01.md
     - id: documentation-site-c01-page
       profile: documentation-site
-      path: templates/article-programs/documentation-site-c01-page.md
+      path: templates/articles/c01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/c01.md
     - id: domain-reference-c02-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-c02-page.md
+      path: templates/articles/c02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/c02.md
     - id: product-requirements-c02-page
       profile: product-requirements
-      path: templates/article-programs/product-requirements-c02-page.md
+      path: templates/articles/c02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/c02.md
     - id: user-and-developer-guide-c02-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-c02-page.md
+      path: templates/articles/c02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/c02.md
     - id: domain-reference-c03-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-c03-page.md
+      path: templates/articles/c03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/c03.md
     - id: product-requirements-c03-page
       profile: product-requirements
-      path: templates/article-programs/product-requirements-c03-page.md
+      path: templates/articles/c03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/c03.md
     - id: technical-guide-c04-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-c04-page.md
+      path: templates/articles/c04.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/c04.md
     - id: faq-support-c05-page
       profile: faq-support
-      path: templates/article-programs/faq-support-c05-page.md
+      path: templates/articles/c05.md
       kind: page-program
       delivery: selected
       reader_goal: resolve-reader-question
       guidance_path: templates/articles/c05.md
     - id: runbook-c05-page
       profile: runbook
-      path: templates/article-programs/runbook-c05-page.md
+      path: templates/articles/c05.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system
       guidance_path: templates/articles/c05.md
     - id: incident-review-c05-page
       profile: incident-review
-      path: templates/article-programs/incident-review-c05-page.md
+      path: templates/articles/c05.md
       kind: page-program
       delivery: selected
       reader_goal: learn-from-incident
       guidance_path: templates/articles/c05.md
     - id: decision-record-c06-page
       profile: decision-record
-      path: templates/article-programs/decision-record-c06-page.md
+      path: templates/articles/c06.md
       kind: page-program
       delivery: selected
       reader_goal: understand-decision-and-tradeoffs
       guidance_path: templates/articles/c06.md
     - id: incident-review-c06-page
       profile: incident-review
-      path: templates/article-programs/incident-review-c06-page.md
+      path: templates/articles/c06.md
       kind: page-program
       delivery: selected
       reader_goal: learn-from-incident
       guidance_path: templates/articles/c06.md
     - id: release-migration-guide-c06-page
       profile: release-migration-guide
-      path: templates/article-programs/release-migration-guide-c06-page.md
+      path: templates/articles/c06.md
       kind: page-program
       delivery: selected
       reader_goal: understand-release-change
       guidance_path: templates/articles/c06.md
     - id: technical-guide-c07-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-c07-page.md
+      path: templates/articles/c07.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/c07.md
     - id: domain-reference-d01-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-d01-page.md
+      path: templates/articles/d01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/d01.md
     - id: technical-guide-d01-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-d01-page.md
+      path: templates/articles/d01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/d01.md
     - id: domain-reference-d02-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-d02-page.md
+      path: templates/articles/d02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/d02.md
     - id: technical-guide-d02-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-d02-page.md
+      path: templates/articles/d02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/d02.md
     - id: domain-reference-d03-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-d03-page.md
+      path: templates/articles/d03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/d03.md
     - id: standard-policy-d03-page
       profile: standard-policy
-      path: templates/article-programs/standard-policy-d03-page.md
+      path: templates/articles/d03.md
       kind: page-program
       delivery: selected
       reader_goal: follow-standard-or-policy
       guidance_path: templates/articles/d03.md
     - id: runbook-d04-page
       profile: runbook
-      path: templates/article-programs/runbook-d04-page.md
+      path: templates/articles/d04.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system
       guidance_path: templates/articles/d04.md
     - id: technical-guide-d04-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-d04-page.md
+      path: templates/articles/d04.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/d04.md
     - id: standard-policy-d04-page
       profile: standard-policy
-      path: templates/article-programs/standard-policy-d04-page.md
+      path: templates/articles/d04.md
       kind: page-program
       delivery: selected
       reader_goal: follow-standard-or-policy
       guidance_path: templates/articles/d04.md
     - id: technical-guide-f01-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-f01-page.md
+      path: templates/articles/f01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/f01.md
     - id: public-api-reference-f05-page
       profile: public-api-reference
-      path: templates/article-programs/public-api-reference-f05-page.md
+      path: templates/articles/f05.md
       kind: page-program
       delivery: selected
       reader_goal: look-up-public-contract
       guidance_path: templates/articles/f05.md
     - id: technical-guide-f06-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-f06-page.md
+      path: templates/articles/f06.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/f06.md
     - id: technical-guide-f08-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-f08-page.md
+      path: templates/articles/f08.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/f08.md
     - id: standard-policy-f08-page
       profile: standard-policy
-      path: templates/article-programs/standard-policy-f08-page.md
+      path: templates/articles/f08.md
       kind: page-program
       delivery: selected
       reader_goal: follow-standard-or-policy
       guidance_path: templates/articles/f08.md
     - id: runbook-f09-page
       profile: runbook
-      path: templates/article-programs/runbook-f09-page.md
+      path: templates/articles/f09.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system
       guidance_path: templates/articles/f09.md
     - id: user-and-developer-guide-f09-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-f09-page.md
+      path: templates/articles/f09.md
       kind: page-program
       delivery: selected
       reader_goal: complete-reader-task
       guidance_path: templates/articles/f09.md
     - id: release-migration-guide-f09-page
       profile: release-migration-guide
-      path: templates/article-programs/release-migration-guide-f09-page.md
+      path: templates/articles/f09.md
       kind: page-program
       delivery: selected
       reader_goal: understand-release-change
       guidance_path: templates/articles/f09.md
     - id: user-and-developer-guide-l01-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-l01-page.md
+      path: templates/articles/l01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/l01.md
     - id: release-migration-guide-l01-page
       profile: release-migration-guide
-      path: templates/article-programs/release-migration-guide-l01-page.md
+      path: templates/articles/l01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-release-change
       guidance_path: templates/articles/l01.md
     - id: public-api-reference-l02-page
       profile: public-api-reference
-      path: templates/article-programs/public-api-reference-l02-page.md
+      path: templates/articles/l02.md
       kind: page-program
       delivery: selected
       reader_goal: look-up-public-contract
       guidance_path: templates/articles/l02.md
     - id: user-and-developer-guide-l02-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-l02-page.md
+      path: templates/articles/l02.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/l02.md
     - id: standard-policy-l03-page
       profile: standard-policy
-      path: templates/article-programs/standard-policy-l03-page.md
+      path: templates/articles/l03.md
       kind: page-program
       delivery: selected
       reader_goal: follow-standard-or-policy
       guidance_path: templates/articles/l03.md
     - id: technical-guide-l03-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-l03-page.md
+      path: templates/articles/l03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/l03.md
     - id: user-and-developer-guide-l03-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-l03-page.md
+      path: templates/articles/l03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/l03.md
     - id: release-migration-guide-l03-page
       profile: release-migration-guide
-      path: templates/article-programs/release-migration-guide-l03-page.md
+      path: templates/articles/l03.md
       kind: page-program
       delivery: selected
       reader_goal: understand-release-change
       guidance_path: templates/articles/l03.md
     - id: technical-guide-l04-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-l04-page.md
+      path: templates/articles/l04.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/l04.md
     - id: user-and-developer-guide-l05-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-l05-page.md
+      path: templates/articles/l05.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/l05.md
     - id: documentation-site-l05-page
       profile: documentation-site
-      path: templates/article-programs/documentation-site-l05-page.md
+      path: templates/articles/l05.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/l05.md
     - id: release-migration-guide-l05-page
       profile: release-migration-guide
-      path: templates/article-programs/release-migration-guide-l05-page.md
+      path: templates/articles/l05.md
       kind: page-program
       delivery: selected
       reader_goal: understand-release-change
       guidance_path: templates/articles/l05.md
     - id: test-validation-q01-page
       profile: test-validation
-      path: templates/article-programs/test-validation-q01-page.md
+      path: templates/articles/q01.md
       kind: page-program
       delivery: selected
       reader_goal: verify-behavior-or-acceptance
       guidance_path: templates/articles/q01.md
     - id: domain-reference-q01-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-q01-page.md
+      path: templates/articles/q01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/q01.md
     - id: test-validation-q02-page
       profile: test-validation
-      path: templates/article-programs/test-validation-q02-page.md
+      path: templates/articles/q02.md
       kind: page-program
       delivery: selected
       reader_goal: verify-behavior-or-acceptance
       guidance_path: templates/articles/q02.md
     - id: test-validation-q03-page
       profile: test-validation
-      path: templates/article-programs/test-validation-q03-page.md
+      path: templates/articles/q03.md
       kind: page-program
       delivery: selected
       reader_goal: verify-behavior-or-acceptance
       guidance_path: templates/articles/q03.md
     - id: test-validation-q04-page
       profile: test-validation
-      path: templates/article-programs/test-validation-q04-page.md
+      path: templates/articles/q04.md
       kind: page-program
       delivery: selected
       reader_goal: verify-behavior-or-acceptance
       guidance_path: templates/articles/q04.md
     - id: test-validation-q05-page
       profile: test-validation
-      path: templates/article-programs/test-validation-q05-page.md
+      path: templates/articles/q05.md
       kind: page-program
       delivery: selected
       reader_goal: verify-behavior-or-acceptance
       guidance_path: templates/articles/q05.md
     - id: runbook-q05-page
       profile: runbook
-      path: templates/article-programs/runbook-q05-page.md
+      path: templates/articles/q05.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system
       guidance_path: templates/articles/q05.md
     - id: runbook-q06-page
       profile: runbook
-      path: templates/article-programs/runbook-q06-page.md
+      path: templates/articles/q06.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system
       guidance_path: templates/articles/q06.md
     - id: user-and-developer-guide-q06-page
       profile: user-and-developer-guide
-      path: templates/article-programs/user-and-developer-guide-q06-page.md
+      path: templates/articles/q06.md
       kind: page-program
       delivery: selected
       reader_goal: understand-product-intent
       guidance_path: templates/articles/q06.md
     - id: incident-review-q07-page
       profile: incident-review
-      path: templates/article-programs/incident-review-q07-page.md
+      path: templates/articles/q07.md
       kind: page-program
       delivery: selected
       reader_goal: learn-from-incident
       guidance_path: templates/articles/q07.md
     - id: faq-support-q07-page
       profile: faq-support
-      path: templates/article-programs/faq-support-q07-page.md
+      path: templates/articles/q07.md
       kind: page-program
       delivery: selected
       reader_goal: resolve-reader-question
       guidance_path: templates/articles/q07.md
     - id: technical-guide-s01-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-s01-page.md
+      path: templates/articles/s01.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/s01.md
     - id: public-api-reference-s02-page
       profile: public-api-reference
-      path: templates/article-programs/public-api-reference-s02-page.md
+      path: templates/articles/s02.md
       kind: page-program
       delivery: selected
       reader_goal: look-up-public-contract
       guidance_path: templates/articles/s02.md
     - id: public-api-reference-s03-page
       profile: public-api-reference
-      path: templates/article-programs/public-api-reference-s03-page.md
+      path: templates/articles/s03.md
       kind: page-program
       delivery: selected
       reader_goal: look-up-public-contract
       guidance_path: templates/articles/s03.md
     - id: domain-reference-s04-page
       profile: domain-reference
-      path: templates/article-programs/domain-reference-s04-page.md
+      path: templates/articles/s04.md
       kind: page-program
       delivery: selected
       reader_goal: understand-domain
       guidance_path: templates/articles/s04.md
     - id: technical-guide-s05-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-s05-page.md
+      path: templates/articles/s05.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/s05.md
     - id: technical-guide-s06-page
       profile: technical-guide
-      path: templates/article-programs/technical-guide-s06-page.md
+      path: templates/articles/s06.md
       kind: page-program
       delivery: selected
       reader_goal: understand-technical-design
       guidance_path: templates/articles/s06.md
     - id: runbook-s07-page
       profile: runbook
-      path: templates/article-programs/runbook-s07-page.md
+      path: templates/articles/s07.md
       kind: page-program
       delivery: selected
       reader_goal: operate-or-recover-system

package/indexers/bundles/context-markdown-indexer/references/classification.md CHANGED Viewed

@@ -1,63 +1,28 @@
-# Section classification and projection intent
-Classify evidence at Section granularity. A profile describes the source family;
-it does not force one whole document into one reader purpose. For every emitted
-Section, choose the semantic `document_kind`, `reader_goal`, and
-`artifact_kind` before grouping Sections into Artifacts.
-Use body evidence, source authority, audience, and the reader task. File names,
-URLs, headings, navigation labels, and the selected profile are hints, not proof
-that every Section has the same intent. Do not infer authority from polished
-language or an official-looking path.
-## Canonical projection vocabulary
-The current community Markdown profiles use the following semantic intents.
-The CLI profile contract owns their stable storage projection; this table does
-not authorize a collection or output path.
-| Profile or Section family | Use when the evidence primarily… | `document_kind` | `reader_goal` | `artifact_kind` |
-| --- | --- | --- | --- | --- |
-| `domain-reference` | defines a durable domain, vocabulary, boundary, or business concept | `domain-reference` | `understand-domain` | `content` |
-| `product-requirements` | states product intent, behavior, scope, actors, or acceptance needs | `product-requirements` | `understand-product-intent` | `content` |
-| `technical-guide` | explains architecture, runtime behavior, interfaces, or design constraints | `technical-guide` | `understand-technical-design` | `content` |
-| user/developer product guidance | explains a user-visible capability or product behavior | `product-requirements` | `understand-product-intent` | `content` |
-| user/developer technical guidance | explains implementation-facing design or integration context | `technical-guide` | `understand-technical-design` | `content` |
-| user/developer task guidance | gives a repeatable task, setup, operation, or troubleshooting sequence | `task-guide` | `complete-reader-task` | `content` |
-| public API contract | supports lookup of public operations, fields, compatibility, or examples | `public-api-reference` | `look-up-public-contract` | `content` |
-| public contract policy | states normative compatibility or usage constraints around a public contract | `public-contract-policy` | `follow-public-contract-policy` | `content` |
-| `runbook` | directs operation, diagnosis, mitigation, recovery, or rollback | `runbook` | `operate-or-recover-system` | `content` |
-| `faq-support` | answers a durable reader question with reusable evidence | `faq-support` | `resolve-reader-question` | `content` |
-| `standard-policy` | defines a stable rule, standard, policy, or compliance boundary | `standard-policy` | `follow-standard-or-policy` | `content` |
-| `decision-record` | records alternatives, a choice, rationale, and consequences | `decision-record` | `understand-decision-and-tradeoffs` | `content` |
-| `incident-review` | records impact, timeline, cause, response, and follow-up learning | `incident-review` | `learn-from-incident` | `content` |
-| `test-validation` | defines or reports verification, acceptance, or observed results | `test-validation` | `verify-behavior-or-acceptance` | `content` |
-| release explanation | explains what changed, compatibility, or release impact | `release-guide` | `understand-release-change` | `content` |
-| migration procedure | tells a reader how to migrate, verify, and recover | `migration-guide` | `complete-migration` | `content` |
-`documentation-site` is an umbrella router. Apply the matching row above to
-each source-backed Section; do not invent a site-wide projection intent and do
-not collapse a multi-document site to one classification.
-## Classification order
-1. Establish the Section's current source authority and audience from the
-   authorized evidence view.
-2. State the concrete question the Section enables a reader to answer or task
-   it enables them to complete.
-3. Choose the narrowest matching `document_kind` and `reader_goal` pair from
-   the current profile contract.
-4. Use `artifact_kind: content` for the current community Markdown Bundle. Do
-   not invent a specialized Artifact kind unless the supplied profile contract
-   explicitly registers it.
-5. Return the intent on every actual or template-projected Section. Do not put
-   a collection, directory, filename, or package root in the Result.
-When a Section mixes multiple reader tasks, split it along continuous evidence
-boundaries. Keep one Section only when the material forms one coherent answer
-for one reader goal. A heading change alone does not require a split, and a
-shared heading does not justify combining unrelated tasks.
-If no registered intent fits, return a material/capability disposition instead
-of selecting the nearest label. Unsupported or authority-ambiguous material
-must not become a reader Artifact.
+# Choose a useful reader outcome
+Use the content, audience and reader question, not a required classification
+tuple for every section. The current plan schema supplies supported output
+paths; article title and description belong in its Markdown.
+| Reader need | Useful form |
+| --- | --- |
+| Understand a term, boundary or business rule | Domain explanation with scope and examples |
+| Understand intended product behavior | Requirements and acceptance conditions, distinct from implementation |
+| Understand architecture or integration | Technical explanation, contracts and relevant limitations |
+| Complete a repeatable task | Guide with prerequisites, actions and checks |
+| Look up a public interface | Contract reference with actual parameters and examples |
+| Diagnose or recover | Runbook with symptoms, safe actions and verification |
+| Understand a choice | Decision, alternatives, rationale and consequences |
+| Learn from an incident | Impact, observations, causes and response, separating hypotheses |
+| Interpret a test | Method, scope and what the observed result establishes |
+| Follow a rule or migrate | Normative boundaries or migration steps, compatibility and recovery |
+These forms guide writing; they are not profile registrations or fixed
+templates. One useful article can contain related explanations, procedures and
+examples. Split only when distinct reader tasks require it, not because two
+sections would previously have had different projection labels.
+Do not turn a document site into one generic summary or every note into a FAQ.
+An unfamiliar topic or imperfect stock outline is not a missing capability.
+Ask for essential missing material; otherwise preserve bounded uncertainty
+and write what the authorized source actually establishes.

package/indexers/bundles/context-markdown-indexer/references/editorial-policy.md CHANGED Viewed

@@ -92,5 +92,5 @@ Protected-value and reference checks remain mechanical safeguards.
 - Struck-through text that is the only surviving historical record may be kept
   when it has continuing reader value; no signal-specific receipt is required.
-Before returning a decision, confirm every Section has one outcome and no
-revision accidentally changes authority, evidence, identity, or protected values.
+Before submitting, check that the revision preserves authority, evidence,
+identity and protected values. Do not submit an outcome ledger for every section.