@mdwrk/extension-runtime 1.0.1 → 1.1.0

package/README.md

@@ -1,24 +1,24 @@
-# mdwrk/extension-runtime
+# @mdwrk/extension-runtime
 
 Portable extension runtime for Markdown Workspace hosts.
 
-This package provides:
+## Runtime responsibilities
+
 - bundled extension registration
 - external catalog registration and loading
-- manifest validation
-- compatibility checks
+- manifest validation and compatibility checks
 - persisted enabled/config/install state with deterministic namespaced keys
 - activation and deactivation lifecycle management
 - capability-scoped host wrappers
 - runtime diagnostics and state snapshots
-- signed-manifest verification
-- module integrity verification
-- install/update/remove flows for external extensions
+- signed-manifest verification and integrity checks
+- install / update / remove flows for external extensions
 - installed extension cache rehydration
 
-## Public runtime surface
+## Public API surface
 
 The runtime exposes methods for:
+
 - registering bundled entries
 - registering or loading catalogs
 - listing available catalog entries
@@ -26,9 +26,31 @@ The runtime exposes methods for:
 - enabling/disabling and activating/deactivating extensions
 - reading configuration stores and runtime services
 
-## Current status
+## Compatibility declarations
+
+This package depends on the contract packages rather than app internals:
+
+- `@mdwrk/extension-host`
+- `@mdwrk/extension-manifest`
+- `@mdwrk/theme-contract`
+
+## Lifecycle and integration tests
+
+- `tests/runtime.test.ts` covers lifecycle, install/cache, compatibility, and state-management behavior
+- `tests/run-smoke.mjs` covers runtime exports and smoke-level integration
+- `tests/prepare-workspace-links.mjs` keeps workspace package links usable for package-local test execution
+
+## Install / host integration guidance
+
+Hosts should provide the runtime with:
+
+- a compliant host API implementation from `@mdwrk/extension-host`
+- a registration sink that maps runtime registrations onto host surfaces
+- a storage adapter for config/install state
+- trust/signing policy for external catalog flows
+
+## API/reference docs
 
-Implemented through Phase 13.
+See the generated reference page at:
 
-The package is publishable and includes the formal third-party catalog installer/runtime path described in the repository architecture docs.
-Production deployments should still use managed signing keys and hosted catalog infrastructure rather than the development sample signer generated in checkpoint tooling.
+- `docs/reference/packages/mdwrk-extension-runtime.md`

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const EXTENSION_RUNTIME_VERSION: "1.0.0";
+export declare const EXTENSION_RUNTIME_VERSION: "1.1.0";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -1,2 +1,2 @@
-export const EXTENSION_RUNTIME_VERSION = "1.0.0";
+export const EXTENSION_RUNTIME_VERSION = "1.1.0";
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mdwrk/extension-runtime",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "type": "module",
   "license": "Apache-2.0",
   "publishConfig": {
@@ -25,7 +25,7 @@
   "dependencies": {
     "@mdwrk/extension-host": "^1.0.1",
     "@mdwrk/extension-manifest": "^1.0.0",
-    "@mdwrk/theme-contract": "^1.0.0"
+    "@mdwrk/theme-contract": "^1.1.0"
   },
   "devDependencies": {},
   "scripts": {