@decantr/core - npm Package Compare versions

Comparing version 3.8.1 to 3.8.2

dist/index.d.ts

@@ -907,2 +907,3 @@ import { EssenceV4, StructurePage, EssenceFile } from '@decantr/essence-spec';
     resolver?: ContentResolver;
+    stylingMode?: 'host' | 'decantr-css';
 }
@@ -909,0 +910,0 @@ declare function renderExecutionPackMarkdown(pack: ExecutionPackBase<unknown>): string;

package.json

 {
   "name": "@decantr/core",
-  "version": "3.8.1",
+  "version": "3.8.2",
   "description": "Decantr core — execution-pack, typed graph, and Contract capsule primitives",
@@ -63,4 +63,4 @@ "keywords": [
   "dependencies": {
-    "@decantr/registry": "3.8.1",
-    "@decantr/essence-spec": "3.8.1"
+    "@decantr/essence-spec": "3.8.1",
+    "@decantr/registry": "3.8.1"
   },
@@ -67,0 +67,0 @@ "devDependencies": {},

README.md

@@ -32,3 +32,3 @@ # @decantr/core
 
-The graph exports establish the storage boundary, typed schema shape, temporal snapshot/diff shape, payload-filterable node queries, hybrid route-context ranking, hybrid node/source impact traversal, and provider-neutral contract capsule shape for CLI, MCP, verifier, Studio, and CI integration. Ranking blends deterministic weighted traversal with local personalized PageRank and optional task-text boosts, so central graph nodes and task-relevant nodes both surface without introducing a graph database dependency. Behavior obligations remain app-owned local law in `.decantr/local-patterns.json`; higher-level packages project accepted obligations into existing `LocalRule` graph nodes with `payload.kind = "behavior-obligation"` instead of adding a new graph node type. Evidence Bundles, runtime probes, visual manifests, baseline diffs, repair plans, and proof reports are ingested through existing graph node/edge shapes where possible, and `TEST_COVERS_NODE` edges act as verification hints rather than proof of production UI behavior. The capsule keeps the contract cache key stable while listing bounded SourceArtifact paths agents can use for file-impact follow-up queries. The core package remains pure library code: filesystem graph persistence belongs in higher-level packages such as the CLI.
+The graph exports establish the storage boundary, typed schema shape, temporal snapshot/diff shape, payload-filterable node queries, hybrid route-context ranking, hybrid node/source impact traversal, and provider-neutral contract capsule shape for CLI, MCP, verifier, Studio, and CI integration. Ranking blends deterministic weighted traversal with local personalized PageRank and optional task-text boosts, so central graph nodes and task-relevant nodes both surface without introducing a graph database dependency. Behavior obligations remain app-owned local law in `.decantr/local-patterns.json`; higher-level packages project accepted obligations into existing `LocalRule` graph nodes with `payload.kind = "behavior-obligation"` instead of adding a new graph node type. Evidence Bundles, runtime probes, visual manifests, repair plans, and proof reports are ingested through existing graph node/edge shapes where possible; generated health-baseline diffs are excluded to avoid circular graph invalidation, and `TEST_COVERS_NODE` edges act as verification hints rather than proof of production UI behavior. The capsule keeps the contract cache key stable while listing bounded SourceArtifact paths agents can use for file-impact follow-up queries. The core package remains pure library code: filesystem graph persistence belongs in higher-level packages such as the CLI.
 
@@ -35,0 +35,0 @@ ## FAQ

No alert changes

Worsened metrics

Total package byte prevSize

438604

-0.14%

Lines of code

5901

-0.08%

No dependency changes