@decantr/registry 2.2.0 → 3.0.0-next.0

package/README.md

@@ -3,7 +3,7 @@
 Support status: `core-supported`  
 Release channel: `stable`
 
-Registry contracts, schemas, API client, ranking helpers, and content utilities for Decantr.
+Certified vocabulary contracts, schemas, API client, ranking helpers, and content utilities for Decantr.
 
 ## Install
 
@@ -13,12 +13,12 @@ npm install @decantr/registry
 
 ## What It Exports
 
-- strong types for patterns, themes, blueprints, archetypes, shells, and intelligence metadata
-- `ContentHealthReport` types for registry content supply-chain health artifacts
+- strong types for patterns, themes, starter-kit blueprints, archetypes, shells, and intelligence metadata
+- `ContentHealthReport` types for vocabulary supply-chain health artifacts
 - `RegistryAPIClient` for server-side and tool-side registry access
 - `@decantr/registry/client` for web-safe API usage
-- public schema exports for registry content, content health, and summary responses
-- ranking and sorting helpers for public registry content
+- public schema exports for vocabulary content, content health, and summary responses
+- ranking and sorting helpers for public vocabulary content
 - Brownfield-aware pattern discovery helpers: `patternToDiscoveryCandidate()`, `scorePatternCandidate()`, and `rankPatternCandidates()`
 - blueprint portfolio metadata helpers for public `All`, `Featured`, `Certified`, and `Labs` registry cuts
 
@@ -63,9 +63,9 @@ This package owns the canonical registry schemas published under `@decantr/regis
 
 Blueprint records can include `blueprint_portfolio` metadata. List/search summaries expose that metadata so clients can show public-facing blueprint sets without leaking internal maturity labels:
 
-- `all` — supported public blueprints, excluding Labs and folded slugs by default
+- `all` — supported public starter-kit blueprints, excluding Labs and folded slugs by default
 - `featured` — curated default discovery picks
-- `certified` — blueprints with certified artifact metadata
+- `certified` — starter kits with certified artifact metadata
 - `labs` — opt-in experimental directions
 
 ## Compatibility
@@ -76,6 +76,10 @@ Blueprint records can include `blueprint_portfolio` metadata. List/search summar
 - additive response fields may be introduced without breaking the stable contract
 - breaking client, schema, or path changes require a major version
 
+## Security And Permissions
+
+`@decantr/registry` provides registry schemas, content utilities, and API clients. It may read explicit local registry JSON files when resolver helpers are used, and it may call the configured Decantr API base URL when client methods are invoked. It does not write files, spawn processes, emit telemetry, or upload source by itself. See [security permissions](https://decantr.ai/reference/security-permissions.md).
+
 ## License
 
 MIT

package/package.json

@@ -1,17 +1,17 @@
 {
   "name": "@decantr/registry",
-  "version": "2.2.0",
-  "description": "Registry contracts, schemas, API client, and content utilities for Decantr",
+  "version": "3.0.0-next.0",
+  "description": "Certified vocabulary contracts, schemas, API client, and content utilities for Decantr",
   "keywords": [
     "decantr",
     "decantr-ai",
     "registry",
-    "design-registry",
+    "certified-vocabulary",
     "ui-patterns",
-    "blueprints",
+    "starter-kits",
     "archetypes",
-    "design-intelligence",
-    "ai-generated-ui",
+    "ai-frontend-governance",
+    "design-contracts",
     "content-health"
   ],
   "author": "Decantr AI",
@@ -69,7 +69,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@decantr/essence-spec": "2.0.1"
+    "@decantr/essence-spec": "3.0.0-next.0"
   },
   "scripts": {
     "build": "tsup",