@c4a/context-cli 0.7.0 → 0.7.1

package/providers/context/resources/semantic/code-index/templates/sdk-library.md

@@ -1,132 +0,0 @@
----
-id: semantic.code-index.template.sdk-library
-kind: procedure
-media-type: text/markdown
----
-
-# SDK and shared library template
-
-Use for `sdk-library`: reusable code packages, component libraries, client
-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.
-
-Recommended `outputProfile`: `public-api-reference`.
-
-## Evidence pass
-
-Locate:
-
-- package manifest, exports map, public barrels, binary/native entry, or
-  documented import paths;
-- initialization, providers, factories, configuration, and required runtime;
-- public capability families, components, hooks, types, commands, or clients;
-- supported extension/plugin points and lifecycle;
-- compatibility, platform, peer dependency, and version constraints;
-- maintained examples, tests, API comments, and migration/release notes;
-- external protocol schemas and generated declarations or clients;
-- internal implementation, fixtures, demos, and re-export chains that should
-  not become independent reader pages.
-
-Use public exports plus maintained documentation together. An exported symbol
-can still be incidental; a documented stable import path can remain public even
-when it re-exports another implementation.
-
-## Questions the knowledge must answer
-
-1. Who should use this package and what capabilities does it promise?
-2. What are the supported import/initialization paths?
-3. How are public APIs grouped into concepts a consumer can navigate?
-4. What configuration, lifecycle, compatibility, and failure rules apply?
-5. Which examples demonstrate supported use rather than test-only behavior?
-6. Which declarations are generated, and where is their authority?
-7. How is the package built, versioned, and released when that is in scope?
-
-## Suggested knowledge units
-
-- **Library/module map**: purpose, supported entrypoints, capability families,
-  runtime/peer requirements, extension points, and navigation.
-- **Getting started or lifecycle**: installation assumptions, initialization,
-  configuration, teardown, and minimal supported examples evidenced by source.
-- **Capability-family reference**: a coherent group of APIs/components with
-  usage, contracts, constraints, and related types.
-- **Granular API/component reference**: one symbol or component per page only
-  when the package intentionally exposes a granular public contract and the
-  measured preview remains appropriate.
-- **Compatibility and migration**: supported platforms/versions and evidenced
-  breaking or transitional behavior.
-- **Build/release entry**: only module-owned packaging and release behavior.
-
-## Chapter blueprints
-
-```markdown
-# <Library> module map
-## Purpose and intended consumers
-## Supported entrypoints and initialization
-## Capability families
-## Runtime, peer, and platform requirements
-## Configuration and lifecycle
-## Extension points and external protocols
-## Compatibility, build, and release
-## Examples, evidence, and exclusions
-```
-
-For a capability family:
-
-```markdown
-# <Capability family>
-## When to use it
-## Supported imports or components
-## Initialization and configuration
-## API/component contracts
-## Lifecycle, errors, and constraints
-## Minimal source-backed examples
-## Related capabilities and authoritative references
-```
-
-For a granular reference page:
-
-```markdown
-# <Public API or component>
-## Purpose
-## Import and signature/props
-## Required context and configuration
-## Behavior, lifecycle, and errors
-## Supported example
-## Compatibility and source evidence
-```
-
-## Granularity and relationships
-
-Prefer capability families over one page per export. A symbol page is justified
-when consumers search for that exact public identity and its contract contains
-meaningful behavior beyond a signature. Do not copy complete function bodies,
-private members, generated declarations, fixtures, or every re-export.
-
-The 300-page limit remains per index unit. When a granular public surface would
-cross it, keep the public identities navigable but aggregate them into
-capability-family pages through `extractCustom()`; the limit is not raised for
-large libraries, and splitting one `extractTs()` source into overlapping units
-is not a valid workaround.
-
-Relate public entries to capability families, configuration, examples, and
-external protocols. Internal call graphs are secondary unless the knowledge
-goal explicitly concerns extension or lifecycle behavior.
-
-## Template composition examples
-
-- A component library may use granular component pages plus family indexes,
-  while its demo site is a separate `web-application` unit.
-- A generated client reads `derived-source.md` and
-  `protocol-boundary.md`; document the supported client surface while naming
-  the upstream schema authority.
-- A library with a plugin host also reads `adapter.md` and
-  `plugin-extension.md`.
-
-## Revise or stop when
-
-- the public boundary cannot be distinguished from internal exports;
-- examples are invented instead of derived from maintained usage or tests;
-- generated declarations have no identifiable authority;
-- every export or component is selected without a consumer-navigation reason;
-- compatibility or lifecycle claims are unavailable but required by the goal.

package/providers/context/resources/semantic/code-index/templates/web-application.md

@@ -1,145 +0,0 @@
----
-id: semantic.code-index.template.web-application
-kind: procedure
-media-type: text/markdown
----
-
-# Web and interactive application template
-
-Use only after evidence classifies a module as `web-application`. This covers
-browser applications, server-rendered sites, embedded WebViews, desktop Web
-shells, native mobile/desktop applications, cross-platform UI runtimes, and
-similar interactive modules. The `web-application` identifier is retained for
-the current contract but represents an interactive application boundary, not
-only browser code. It does
-not automatically cover every package containing UI components; a reusable
-component package is usually `sdk-library`.
-
-Recommended `outputProfile`: `application-map`.
-
-## Evidence pass
-
-Locate the concrete application bootstrap and trace outward just far enough to
-find:
-
-- application mounting, server rendering, shell, or host-container entry;
-- route/page/screen registries and navigation guards;
-- page-to-state, loader, query, client, bridge, or controller boundaries;
-- runtime configuration, environment selection, feature registration, and
-  authentication/session initialization;
-- build, local development, test, bundle, and release entrypoints;
-- generated clients, assets, styles, fixtures, and legacy routes that should
-  remain evidence rather than reader-facing pages.
-
-If the route registry is generated, locate both its generator or source of
-truth and the runtime consumer. Do not infer page identity from a directory
-tree when an explicit registry exists.
-
-## Questions the knowledge must answer
-
-A useful application index should let a reader determine:
-
-1. How does the application start, and which runtime or host does it expect?
-2. What are the stable pages/routes/screens and their entry components?
-3. How does a page obtain data or call an external capability?
-4. Which state, session, bridge, or configuration boundaries affect behavior?
-5. How is the module run, debugged, built, and released?
-6. Which implementation details are intentionally outside the knowledge scope?
-
-## Suggested knowledge units
-
-Select only units supported by the confirmed goal and evidence:
-
-- **Application map**: responsibility, runtime, bootstrap, major subsystems,
-  stable dependencies, and navigation to deeper pages.
-- **Route or page registry**: concrete route/page identity, entry component,
-  loader/guard, main data boundary, and source locator. Aggregate related
-  routes when a page-per-route layout would be repetitive.
-- **Data and protocol boundaries**: add application-specific page, state, and
-  session context to the canonical operation record in `protocol-boundary.md`;
-  do not create a second operation registry.
-- **State and host integration**: only stable stores, bridges, extension points,
-  or host contracts that affect multiple pages or public behavior.
-- **Runtime and delivery guide**: module-owned development commands,
-  configuration, build output, deployment/release entry, and evidenced recovery
-  paths.
-- **Cross-layer flow**: a source-backed page-to-client-to-provider chain when
-  both sides are registered sources.
-
-These are possible page families, not a required number of Markdown files.
-
-## Chapter blueprints
-
-An application-map page may use:
-
-```markdown
-# <Application> module map
-## Responsibility and supported runtime
-## Bootstrap sequence
-## Route/page organization
-## State, data, and protocol boundaries
-## Host integrations and extension points
-## Configuration and environment selection
-## Development, build, and release entrypoints
-## Known exclusions and source-of-truth links
-```
-
-A route/page registry may use a compact record rather than prose repetition:
-
-```markdown
-## <Route or page family>
-- Identity and registration:
-- Entry component or controller:
-- Loader, guard, or initialization:
-- Main client/state dependencies:
-- User-visible outcome:
-- Source evidence:
-```
-
-A cross-layer page may use:
-
-```markdown
-# <User interaction> execution path
-## Trigger and route entry
-## UI/state orchestration
-## Protocol request and authoritative contract
-## Provider boundary and response handling
-## Failure, fallback, and observability
-## Source-backed relationship chain
-```
-
-Do not fill a heading with generic text. Omit or mark a section as a material
-gap when the source cannot support it.
-
-## Granularity and relationships
-
-Prefer stable application concepts over one page per component, hook, state
-field, style, generated type, or internal helper. A page registry must contain
-real identities and source locators, not just folder names. A protocol page
-must name concrete operations or contract locations, not merely state that the
-application “uses HTTP”.
-
-Create structured relationships only when registration, call sites, imports
-with unambiguous ownership, or parser evidence support them. Keep inferred
-product intent out of the index.
-
-## Template composition examples
-
-- A server-rendered application with local API routes also reads
-  `api-service.md` and `protocol-boundary.md`.
-- An embedded application with a host bridge also reads `adapter.md` and the
-  applicable `plugin-extension.md` or `protocol-boundary.md` template.
-- A design-system package rendered in a demo application may need separate
-  index units: `sdk-library` for the supported package and `web-application`
-  for the demo host.
-
-## Revise or stop when
-
-- no executable bootstrap or route registry can be located;
-- the proposed output is only a directory summary;
-- protocol semantics depend on unavailable material;
-- generated routes or clients are being mistaken for authoritative behavior;
-- one-symbol-per-page selection expands components or API types without a
-  deliberate public-reference goal.
-
-Resolve these issues before the measured batch preview.

package/providers/context/resources/semantic/compile/index.md

@@ -1,31 +0,0 @@
----
-context_resource: semantic/compile/index
-id: context.semantic.compile.index
-kind: procedure
-media-type: text/markdown
-applies-to:
-  - diagnostic-routing
-  - evidence-repair
-name: compile-reference-index
-description: "Optional index for non-mechanical structure and evidence diagnostics; normal compile does not require it."
----
-
-# Compile semantic reference index
-
-Normal source-bound compile is deterministic and does not require these
-references. Read this index only when a structure or evidence diagnostic asks
-for a non-mechanical decision, then open only the matching procedure:
-
-- [Compile action contract](compile-actions.md)
-- [Action and domain gates](action-domain-gates.md)
-- [Notes and caveats](notes.md)
-- [Refresh and update](refresh-and-update.md)
-- [Structural challenges](structural-challenges.md)
-- [Compile judgment](compile-judgment.md)
-- [Semantic judgment](semantic-judgment.md)
-- [Disposition semantics](disposition-semantics.md)
-- [Temporal evidence](temporal-and-evidence.md)
-- [Leakage and ownership](leakage-and-ownership.md)
-- [Scope review and omission](scope-review-and-omit.md)
-- [User confirmation](user-confirmation.md)
-- [Close gate](close-gate.md)

package/providers/context/resources/views/code-index-audit.yaml

@@ -1,6 +0,0 @@
-schema: agent-graph.resource.v1
-id: context.code-index-audit
-kind: context-view
-mediaType: text/markdown
-description: Current code-index content-depth, evidence-scope, relationship, source-coverage signals, and prior Agent decisions.
-materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/extraction-preview.yaml

@@ -1,6 +0,0 @@
-schema: agent-graph.resource.v1
-id: context.extraction-preview
-kind: context-view
-mediaType: text/markdown
-description: Current batch code-extraction scale, output profile, ownership, structural probe coverage, and capability report.
-materializer: actions/materialize-context-view.yaml

package/providers/context/resources/views/structure-current.yaml

@@ -1,6 +0,0 @@
-schema: agent-graph.resource.v1
-id: context.structure-current
-kind: context-view
-mediaType: text/markdown
-description: Current multi-document structure slots, declarations, and compile batch.
-materializer: actions/materialize-context-view.yaml

package/providers/context/schemas/code-index-audit-decision.schema.json

@@ -1,94 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "context.code-index-audit-decision.v1",
-  "title": "Context code-index Agent audit decision",
-  "type": "object",
-  "additionalProperties": false,
-  "required": [
-    "schema",
-    "report_digest",
-    "decision",
-    "summary",
-    "reviewed_units",
-    "scope_assessment",
-    "signal_assessments"
-  ],
-  "properties": {
-    "schema": { "const": "context.code-index-audit-decision.v1" },
-    "report_digest": { "type": "string", "minLength": 1 },
-    "decision": {
-      "type": "string",
-      "enum": ["accept", "revise", "request-input"]
-    },
-    "summary": { "type": "string", "minLength": 1 },
-    "reviewed_units": {
-      "type": "array",
-      "minItems": 1,
-      "uniqueItems": true,
-      "items": { "type": "string", "minLength": 1 }
-    },
-    "scope_assessment": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": ["matches_requested_scope", "omissions", "summary"],
-      "properties": {
-        "matches_requested_scope": { "type": "boolean" },
-        "omissions": {
-          "type": "array",
-          "uniqueItems": true,
-          "items": { "type": "string" }
-        },
-        "summary": { "type": "string", "minLength": 1 }
-      }
-    },
-    "signal_assessments": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "additionalProperties": false,
-        "required": ["signal_id", "disposition", "reason"],
-        "properties": {
-          "signal_id": { "type": "string", "minLength": 1 },
-          "disposition": {
-            "type": "string",
-            "enum": ["fix", "acceptable", "not-applicable"]
-          },
-          "reason": { "type": "string", "minLength": 1 }
-        }
-      }
-    },
-    "revision_plan": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": ["units", "actions"],
-      "properties": {
-        "units": {
-          "type": "array",
-          "minItems": 1,
-          "uniqueItems": true,
-          "items": { "type": "string", "minLength": 1 }
-        },
-        "actions": {
-          "type": "array",
-          "minItems": 1,
-          "items": { "type": "string", "minLength": 1 }
-        }
-      }
-    },
-    "requested_material": {
-      "type": "array",
-      "minItems": 1,
-      "items": { "type": "string", "minLength": 1 }
-    }
-  },
-  "allOf": [
-    {
-      "if": { "properties": { "decision": { "const": "revise" } } },
-      "then": { "required": ["revision_plan"] }
-    },
-    {
-      "if": { "properties": { "decision": { "const": "request-input" } } },
-      "then": { "required": ["requested_material"] }
-    }
-  ]
-}

package/providers/context/schemas/document-optimization-decisions.schema.json

@@ -1,57 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "context.document-optimization-decisions.v2",
-  "title": "Context source-constrained editorial revision decisions",
-  "type": "object",
-  "additionalProperties": false,
-  "required": ["schema", "decisions"],
-  "properties": {
-    "schema": { "const": "context.document-optimization-decisions.v2" },
-    "decisions": {
-      "type": "array",
-      "items": {
-        "type": "object",
-        "additionalProperties": false,
-        "required": ["fragment_id", "input_digest", "context_digest", "policy_digest", "action"],
-        "properties": {
-          "fragment_id": { "type": "string", "minLength": 1 },
-          "input_digest": { "type": "string", "minLength": 1 },
-          "context_digest": { "type": "string", "minLength": 1 },
-          "policy_digest": { "type": "string", "minLength": 1 },
-          "action": {
-            "enum": ["keep", "repair", "reshape", "omit"],
-            "description": "Keep the Section, repair local presentation, reshape it within the same source boundary, or omit a mechanically eligible non-knowledge Section."
-          },
-          "replacement": { "type": "string" },
-          "assessment": {
-            "type": "string",
-            "minLength": 12,
-            "description": "Required when keeping a Section that has mechanical signals and when a repair or reshape retains review-confidence signals after rescan. Name every remaining signal code and explain why it is a false positive or why changing the Section would reduce source fidelity. Repair and reshape replacements cannot retain high-confidence signals. This value is decision-only and is not published."
-          },
-          "reason": {
-            "enum": [
-              "unanswered-question",
-              "empty-or-placeholder",
-              "draft-without-decision",
-              "duplicate-content",
-              "obsolete-without-replacement",
-              "volatile-reference",
-              "sensitive-value-candidate",
-              "conversion-artifact"
-            ]
-          }
-        },
-        "allOf": [
-          {
-            "if": { "properties": { "action": { "enum": ["repair", "reshape"] } } },
-            "then": { "required": ["replacement"] }
-          },
-          {
-            "if": { "properties": { "action": { "const": "omit" } } },
-            "then": { "required": ["reason"] }
-          }
-        ]
-      }
-    }
-  }
-}

package/providers/context/schemas/indexer-contract-overlay-authorization-input.schema.json

@@ -1,32 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "context.indexer.contract-overlay-authorization-input/v1",
-  "type": "object",
-  "additionalProperties": false,
-  "required": [
-    "protocol",
-    "validation_input",
-    "expected_conformance_report_digest",
-    "authority_ref",
-    "authority_scope_digest",
-    "input_digest"
-  ],
-  "properties": {
-    "protocol": { "const": "context.indexer.contract-overlay-authorization-input/v1" },
-    "validation_input": {
-      "type": "object",
-      "required": ["protocol", "input_digest"],
-      "properties": {
-        "protocol": { "const": "context.indexer.contract-overlay-validation-input/v1" },
-        "input_digest": { "$ref": "#/$defs/digest" }
-      }
-    },
-    "expected_conformance_report_digest": { "$ref": "#/$defs/digest" },
-    "authority_ref": { "type": "string", "minLength": 1 },
-    "authority_scope_digest": { "$ref": "#/$defs/digest" },
-    "input_digest": { "$ref": "#/$defs/digest" }
-  },
-  "$defs": {
-    "digest": { "type": "string", "pattern": "^sha256:[a-f0-9]{64}$" }
-  }
-}

package/providers/context/schemas/indexer-contract-overlay-authorization-result.schema.json

@@ -1,121 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "context.indexer.contract-overlay-authorization-result/v1",
-  "type": "object",
-  "additionalProperties": false,
-  "required": [
-    "protocol",
-    "trusted_validation_input",
-    "validation",
-    "project_authorization",
-    "result_digest"
-  ],
-  "properties": {
-    "protocol": { "const": "context.indexer.contract-overlay-authorization-result/v1" },
-    "trusted_validation_input": {
-      "type": "object",
-      "required": ["protocol", "project_authorization", "input_digest"],
-      "properties": {
-        "protocol": { "const": "context.indexer.contract-overlay-validation-input/v1" },
-        "project_authorization": { "type": "object" },
-        "input_digest": { "$ref": "#/$defs/digest" }
-      }
-    },
-    "validation": {
-      "type": "object",
-      "required": [
-        "protocol",
-        "outcome",
-        "graph_outcome",
-        "validation_input_digest",
-        "trust_receipt",
-        "result_digest"
-      ],
-      "properties": {
-        "protocol": { "const": "context.indexer.contract-overlay-validation-result/v1" },
-        "outcome": { "const": "trusted" },
-        "graph_outcome": { "const": "completed" },
-        "validation_input_digest": { "$ref": "#/$defs/digest" },
-        "trust_receipt": {
-          "type": "object",
-          "additionalProperties": false,
-          "required": [
-            "protocol",
-            "trust_class",
-            "project_ref",
-            "overlay_digest",
-            "attestation_digest",
-            "base_contract_digest",
-            "provider_integrity",
-            "operator_contract_digest",
-            "conformance_report_digest",
-            "trust_adapter",
-            "trust_adapter_version",
-            "trust_management_authority_digest",
-            "trust_policy_digest",
-            "authorization_receipt_digest",
-            "receipt_digest"
-          ],
-          "properties": {
-            "protocol": { "const": "context.indexer.overlay-trust-receipt/v1" },
-            "trust_class": { "const": "project-authorized-exact-digest" },
-            "project_ref": { "type": "string", "minLength": 1 },
-            "overlay_digest": { "$ref": "#/$defs/digest" },
-            "attestation_digest": { "$ref": "#/$defs/nullableDigest" },
-            "base_contract_digest": { "$ref": "#/$defs/digest" },
-            "provider_integrity": { "$ref": "#/$defs/digest" },
-            "operator_contract_digest": { "$ref": "#/$defs/digest" },
-            "conformance_report_digest": { "$ref": "#/$defs/digest" },
-            "trust_adapter": { "type": "null" },
-            "trust_adapter_version": { "type": "null" },
-            "trust_management_authority_digest": { "type": "null" },
-            "trust_policy_digest": { "type": "null" },
-            "authorization_receipt_digest": { "$ref": "#/$defs/digest" },
-            "receipt_digest": { "$ref": "#/$defs/digest" }
-          }
-        },
-        "result_digest": { "$ref": "#/$defs/digest" }
-      }
-    },
-    "project_authorization": {
-      "type": "object",
-      "additionalProperties": false,
-      "required": [
-        "protocol",
-        "project_ref",
-        "overlay_digest",
-        "attestation_digest",
-        "base_contract_digest",
-        "provider_integrity",
-        "operator_contract_digest",
-        "conformance_report_digest",
-        "authority_ref",
-        "authority_scope_digest",
-        "authorization_receipt_digest"
-      ],
-      "properties": {
-        "protocol": { "const": "context.indexer.overlay-project-authorization/v1" },
-        "project_ref": { "type": "string", "minLength": 1 },
-        "overlay_digest": { "$ref": "#/$defs/digest" },
-        "attestation_digest": { "$ref": "#/$defs/nullableDigest" },
-        "base_contract_digest": { "$ref": "#/$defs/digest" },
-        "provider_integrity": { "$ref": "#/$defs/digest" },
-        "operator_contract_digest": { "$ref": "#/$defs/digest" },
-        "conformance_report_digest": { "$ref": "#/$defs/digest" },
-        "authority_ref": { "const": "context.indexer-contract-overlay" },
-        "authority_scope_digest": { "$ref": "#/$defs/digest" },
-        "authorization_receipt_digest": { "$ref": "#/$defs/digest" }
-      }
-    },
-    "result_digest": { "$ref": "#/$defs/digest" }
-  },
-  "$defs": {
-    "digest": { "type": "string", "pattern": "^sha256:[a-f0-9]{64}$" },
-    "nullableDigest": {
-      "oneOf": [
-        { "type": "null" },
-        { "$ref": "#/$defs/digest" }
-      ]
-    }
-  }
-}

package/providers/context/schemas/prose-structure-batch.schema.json

@@ -1,35 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "context.prose.structure-batch.v1",
-  "title": "Context prose structure batch",
-  "type": "object",
-  "additionalProperties": false,
-  "required": ["schema", "items"],
-  "properties": {
-    "schema": {
-      "const": "context.prose.structure-batch.v1"
-    },
-    "items": {
-      "type": "array",
-      "minItems": 1,
-      "maxItems": 100,
-      "items": {
-        "type": "object",
-        "additionalProperties": false,
-        "required": ["phase_id", "input"],
-        "properties": {
-          "phase_id": {
-            "type": "string",
-            "minLength": 1,
-            "description": "One declared phase.align.prose id from the current pending structure targets."
-          },
-          "input": {
-            "type": "string",
-            "minLength": 1,
-            "description": "Project-relative or absolute YAML/JSON context.structure.v1 payload path for this target."
-          }
-        }
-      }
-    }
-  }
-}