@unispechq/unispec-schema 0.1.5 → 0.2.0

package/README.md

@@ -13,7 +13,7 @@ It contains everything required to understand, validate, and evolve the language
 - Human-readable reference documentation
 - Official examples (REST, GraphQL, WebSocket, mixed APIs)
 - Versioning and compatibility rules
-- Links to RFCs governing format evolution
+- Documented process for evolving the format over time
 
 UniSpec powers all components of the UniSpec platform:
 Core Engine → CLI → Framework Adapters → Registry → Portal → Enterprise extensions.
@@ -57,7 +57,7 @@ This repo defines the UniSpec language, not its implementation.
 - JSON Schemas
 - Examples and documentation
 - Rules for versioning and compatibility
-- Official reference for implementers
+- Documented process for evolving the format over time
 
 ### This repository does NOT contain:
 
@@ -91,7 +91,7 @@ UniSpec is built on the following principles:
 - Supports custom extensions via x-extensions, similar to OpenAPI but cleaner and more consistent.
 
 5. Transparent evolution
-- All major changes require an approved RFC.
+- All major changes must be clearly documented.
 - Minor changes and clarifications must maintain backward compatibility.
 
 ## JSON Schema
@@ -104,7 +104,7 @@ The canonical, machine-readable definition of UniSpec lives in the schema/ direc
 - Must use $defs for reusable components
 - Must clearly describe field semantics and constraints
 - All examples must validate against the schema
-- Breaking changes require an RFC and a major version bump
+- Breaking changes require explicit agreement and a major version bump
 
 ## Examples
 
@@ -138,7 +138,7 @@ UniSpec follows Semantic Versioning (SemVer):
 
 All changes must be recorded in CHANGELOG.md.
 
-## RFC Process
+## Format Changes and Contributions
 
 Any change that alters:
 
@@ -147,10 +147,7 @@ Any change that alters:
 - compatibility rules
 - supported protocols
 
-must be proposed, discussed, and approved in the
-unispec-rfcs repository before being applied here.
-
-No schema modifications may occur without a corresponding approved RFC.
+should be proposed and discussed in a pull request before being applied here.
 
 ## Contributing
 
@@ -159,7 +156,7 @@ Contributions are welcome!
 To contribute:
 
 1. Read the reference docs.
-2. Review open RFCs or create a new proposal.
+2. Discuss substantial format changes in an issue or pull request.
 3. Submit a PR with clear explanation and schema validation.
 
 All contributions must preserve backward compatibility unless explicitly approved otherwise.

package/index.d.ts

@@ -0,0 +1,9 @@
+export const unispec: Record<string, any>;
+export const manifest: Record<string, any>;
+
+declare const _default: {
+  unispec: typeof unispec;
+  manifest: typeof manifest;
+};
+
+export default _default;

package/package.json

@@ -1,10 +1,11 @@
 {
   "name": "@unispechq/unispec-schema",
-  "version": "0.1.5",
+  "version": "0.2.0",
   "description": "Official UniSpec JSON Schemas",
   "type": "module",
   "main": "index.cjs",
   "module": "index.mjs",
+  "types": "index.d.ts",
   "scripts": {
     "release:patch": "node scripts/release.js patch",
     "release:minor": "node scripts/release.js minor",
@@ -13,7 +14,8 @@
   "exports": {
     ".": {
       "import": "./index.mjs",
-      "require": "./index.cjs"
+      "require": "./index.cjs",
+      "types": "./index.d.ts"
     },
     "./schema": "./schema/index.json",
     "./schema/unispec.schema.json": "./schema/unispec.schema.json"
@@ -21,7 +23,8 @@
   "files": [
     "schema/",
     "index.cjs",
-    "index.mjs"
+    "index.mjs",
+    "index.d.ts"
   ],
   "license": "MIT",
   "repository": {