owlrunkit 0.13.0 → 0.15.0

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # Changelog
 
+## 0.15.0
+
+- Makes detected npm launchers resolve to absolute regular files that Formal
+  verification can execute without weakening symlink rejection.
+- Adds workspace-aware `apps/*` and `packages/*` profile candidates with exact
+  workspace script commands.
+- Expands read-only runtime-isolation diagnostics across common formatters,
+  linters, and explicitly broad test collectors.
+- Preserves rejected verification preflights as append-only execution evidence
+  and persists non-accepted finalize outcomes with their request binding.
+- Consumes completed adoption/profile facts in doctor and inspect guidance only
+  when the launcher and exact local registry bindings are still safe.
+- Keeps Contract v0.2, 0.13/0.14 configurations, profiles, historical
+  executions, receipts, and verifier Core identities readable; repeated
+  upgrades write exclusive sequenced ConfigV2 Core-refresh receipts.
+- Refuses Core or process-wide Codex Skill upgrades before mutation when any
+  explicitly enrolled project has an active execution, writer lease,
+  ambiguous closeout, or invalid config.
+- Archives the exact prior Skill and project config bytes, adds receipt-bound
+  exact rollback, and adds an exact-Core active-fleet recovery path for
+  installations already drifted by an older unsafe replacement.
+- Runs registry pack/install/upgrade/rollback gates through npm owned by each
+  selected Node runtime and proves active work blocks upgrade before mutation
+  and rollback restores the exact prior Skill identity and config bytes.
+- Keeps OwlCoda CLI `0.15.31` unchanged and grants no Git, publish, release, or
+  deploy authority.
+
+## 0.14.0
+
+- Adds ordinary `--help` and `--version`, read-only `doctor`, exact official
+  registry `adopt`, and deterministic `profiles detect`, `validate`, and
+  `impact` commands for self-service project onboarding.
+- Makes `init` guide new users through doctor, profile detection, then exact
+  adoption or Formal start while retaining a complete JSON machine view.
+- Includes the previously prepared Core v0.13 documentation corrections for
+  Quick verification, deterministic repair, offline transport,
+  registry-first adoption, and the canonical Codex Skill update boundary.
+- Updates the bundled Codex Skill and config template to Core `0.14.0`.
+- Keeps Contract v0.2 and OwlCoda CLI `0.15.31` unchanged.
+- Does not add signing, keys, GitHub Actions, or authority.
+
 ## 0.13.0
 
 - First standalone npm release of OwlRunKit.

package/README.md

@@ -11,16 +11,77 @@ release authority.
 ## Install
 
 ```bash
-npm install --save-exact owlrunkit@0.13.0
+npm install --save-exact owlrunkit@0.15.0
 ```
 
-Initialize and inspect a project:
+Check the ordinary CLI surface, then initialize a project:
 
 ```bash
+owlrunkit --help
+owlrunkit --version
 owlrunkit init --workspace /absolute/path/to/project
-owlrunkit inspect --workspace /absolute/path/to/project --json
+owlrunkit doctor --workspace /absolute/path/to/project
+owlrunkit profiles detect --workspace /absolute/path/to/project --dry-run
+owlrunkit adopt --workspace /absolute/path/to/project --exact owlrunkit@0.15.0
 ```
 
+`doctor` is read-only and distinguishes offline/DNS timeout, registry
+authentication, missing version, and local install binding failures. Profile
+detection is deterministic and dry-run only; use `profiles validate` and
+`profiles impact --changed` for supported profile checks. `adopt` writes typed
+evidence only after the exact installed package and lockfile match the official
+npm registry release.
+
+Core 0.15 keeps Contract v0.2 and all 0.13/0.14 project artifact schemas
+readable. `init` refreshes an older ConfigV2 Core binding with an append-only
+migration receipt only when the project has no active execution, active writer
+lease, or ambiguous control state. Otherwise the upgrade exits before changing
+the config or writing migration evidence. Legal refreshes preserve profiles,
+executions, receipts, and adoption evidence byte-for-byte. Existing profiles
+are never rewritten automatically; a fresh `profiles detect --dry-run` supplies
+safer, workspace-aware candidates for human review.
+Repeated Core refreshes create sequenced receipts without replacing an earlier
+migration event, and rejected Formal finalize gates retain their request-bound
+reason as append-only evidence.
+
+## Updating the process-wide Codex Skill
+
+Do not replace a shared installed Skill while any consuming project is active.
+For a changed Skill manifest, enumerate the complete consuming fleet with
+repeated `--workspace` arguments:
+
+```bash
+node ./scripts/runkit-contract/install-codex-skill.mjs install \
+  --repository /absolute/path/to/owlrunkit-package \
+  --target /absolute/path/to/installed/owlcoda-runkit \
+  --archive /absolute/path/to/skill-archives \
+  --workspace /absolute/project-a \
+  --workspace /absolute/project-b
+```
+
+The update is refused before global or project mutation if any listed project
+is active or invalid. A successful update records the exact prior Skill
+identity and each original project config in an append-only receipt. Restore
+that exact state with:
+
+```bash
+node ./scripts/runkit-contract/install-codex-skill.mjs restore \
+  --target /absolute/path/to/installed/owlcoda-runkit \
+  --archive /absolute/path/to/skill-archives \
+  --receipt /absolute/path/to/skill-upgrade-receipt.json
+```
+
+`recover-active` is reserved for a fleet already drifted by an older unsafe
+replacement. It accepts only an archived Skill whose Core identity exactly
+matches every affected config and active execution pin, leaves all project
+bytes untouched, and writes a recovery receipt.
+
+Use Quick Verification for one low-risk source-bound command that needs a
+reusable receipt but no writer lease or Formal acceptance. Use Formal Delivery
+for multi-writer, long-running, migration, integration, release, production,
+funds, or formally accepted work. A Quick receipt cannot become Formal
+acceptance, and accepted never grants Git or release authority.
+
 The package also includes the read-only verifier:
 
 ```bash
@@ -37,7 +98,8 @@ Those remain explicit external decisions even when verification passes.
 
 - Node.js 20.19 or newer
 - a local project directory
-- no network access for normal verification and recovery operations
+- network access only for explicit `doctor` registry diagnostics and `adopt`;
+  normal verification and recovery remain local
 
 ## License
 

package/docs/architecture/OWLCODA_RUN_KIT_CONTRACT_V0_2.md

@@ -453,6 +453,85 @@ claim that every provider exposes reliable remaining quota, reset time, or
 pricing. Live provider adapters require a separately verifiable source and may
 legitimately report typed unknown fields.
 
+## Core v0.13 standalone distribution, Quick verification and repair
+
+Core `0.13.0` is distributed through the standalone `owlrunkit` package. The
+RunKit package has an independent semantic version lifecycle from the
+`owlcoda` CLI; a RunKit packaging or documentation patch does not change the
+Contract `0.2` / Core `0.13.0` identity unless Core behavior or its bound
+dependency closure changes.
+
+Core `0.13.0` adds a bounded Quick Verification lane for one exact command
+without a writer lease or Formal acceptance. `quick-verify` records the
+pre/post workspace fingerprints, exact executable and argv, stdout/stderr
+materials, exit result and an authorization-free
+`OwlCodaQuickVerificationReceiptV1`. `quick-attest` recomputes the selected
+workspace and receipt bindings. `quick-metrics --local` reads only the
+project-owned receipt store and performs no telemetry or network access. A
+Quick `GO` remains `captured_verification`; it cannot satisfy the Formal
+Contract v0.2 acceptance gate.
+
+Deterministic `repair` persists a reviewable plan before replay, reuses only
+fresh receipt-bound coverage, replays pending exact argv, and appends
+replacement lineage. Failed and orphaned attempts remain inspectable. Repair
+cannot rewrite the parent receipt, lower risk, replace the executable after
+planning, or activate a green leaf after source/profile drift.
+
+`offline-export` and `offline-import` move exact receipt bytes through
+`OwlCodaOfflineAttestationBundleV1`. Export refuses an existing destination.
+Import is idempotent only when the stored receipt bytes match exactly and fails
+closed on conflicts, symlinked paths or malformed bundles. The embedded
+read-only attestation component is part of the standalone package; it does not
+need a separate public package for the first adoption wave.
+
+Formal cross-project adoption is registry-first. The installed package and
+controller-owned `OwlCodaRunKitRegistryReleaseEvidenceV1` must bind the same
+exact official npm registry version, 40-hex `shasum`, canonical SHA-512
+`integrity`, and exact tarball URL. A local directory, `file:` dependency,
+local tarball, symlink, workspace link, Git reference or mutable dist-tag can
+exercise a release candidate but is not formal adoption evidence.
+
+The canonical Codex Skill is assembled atomically with a content manifest that
+binds its Skill text, Core, contracts and attestation files. Known valid
+installations may be archived and replaced; unknown drift fails closed. Core
+`0.13.0` does not grant Git, npm, release, or foreign-project authority.
+Signing, keys, external anchors and GitHub Actions remain deferred.
+
+## Core v0.14 self-service onboarding
+
+Core `0.14.0` keeps Contract `0.2`, Quick/Formal lane separation, exact
+registry binding, append-only execution lineage, independent review and all
+authority boundaries unchanged. Its product change is the first-adoption
+surface of the standalone `owlrunkit` package:
+
+- top-level `--help` and `--version` follow ordinary CLI expectations and exit
+  successfully without creating project state;
+- `doctor` performs read-only Node, Core, config, package, registry, profile
+  and project-script diagnostics with a short network timeout and a typed
+  offline/DNS-timeout, authorization, missing-version and binding-mismatch
+  taxonomy;
+- `profiles detect --dry-run`, `profiles validate`, and
+  `profiles impact --changed` provide deterministic official entrypoints
+  without treating guessed profiles as authoritative configuration;
+- `adopt --exact owlrunkit@0.14.0` accepts only the official npm registry exact
+  version whose registry metadata and local install/lock binding pass the
+  existing strict adoption evaluator; and
+- `init` and `inspect` add a separate onboarding projection for
+  `doctor -> profiles detect --dry-run -> adopt or Formal start`.
+
+Read-only onboarding commands must not write project state or expose registry
+credentials. Adoption evidence is written atomically only after eligibility.
+Local directories, worktrees, `file:` or Git dependencies, local tarballs,
+workspace links and mutable tags remain fail-closed. Profile detection never
+overwrites existing config, and an implementation may omit `profiles apply`
+rather than infer authority from a deterministic suggestion.
+
+The onboarding projection is not the recovery state machine: a project with a
+stale Packet, invalid evidence or engine drift must still follow the Core's
+`nextAllowedAction`. Core `0.14.0` does not grant Git, npm, release, deploy or
+foreign-project authority. Signing, keys, external anchors and GitHub Actions
+remain deferred.
+
 ## Deferred work
 
 Contract v0.2 still does not add a built-in browser or Electron driver, Plugin,

package/integrations/codex/skills/owlcoda-runkit/SKILL.md

@@ -7,6 +7,9 @@ description: Run receipt-backed, project-owned software execution with OwlCoda R
 
 Use the bundled deterministic Core to coordinate work through project artifacts rather than chat memory. Require Node.js 20 or later.
 
+Current release: standalone `owlrunkit@0.15.0`, bundling Contract `0.2` and
+Core `0.15.0`. The root `owlcoda` package has a separate version lifecycle.
+
 The session is an execution interface. Project artifacts are the system of record.
 
 ## Start safely
@@ -22,8 +25,8 @@ Set `SKILL_ROOT` to this skill directory before running the examples below.
 ## Initialize and inspect
 
 ```bash
-node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" init --workspace "$PROJECT_ROOT"
-node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" inspect --json --workspace "$PROJECT_ROOT"
+owlrunkit init --workspace "$PROJECT_ROOT"
+owlrunkit inspect --json --workspace "$PROJECT_ROOT"
 ```
 
 Initialization may write only `.owlcoda/runkit/`. It must not modify business source.
@@ -53,6 +56,164 @@ dangling or non-regular control truth fails closed instead of appearing absent.
 Project config authority fields are validated before output, human text escapes
 control characters, and indexed ordering is locale independent.
 
+## Core v0.13 distribution, verification and recovery
+
+Core `0.13.0` introduced the standalone distribution, Quick verification and
+repair surfaces. OwlRunKit uses its own version lifecycle: the standalone
+`owlrunkit` npm package may change without changing the `owlcoda` CLI version.
+
+For one low-risk exact command, use the Core v0.13 Quick path:
+
+```bash
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" quick-verify \
+  --workspace "$PROJECT_ROOT" -- "$ABSOLUTE_EXECUTABLE" "arg-one"
+
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" quick-attest \
+  --workspace "$PROJECT_ROOT" --receipt "$QUICK_RECEIPT"
+
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" quick-metrics \
+  --workspace "$PROJECT_ROOT" --local
+```
+
+Quick receipts are `captured_verification`, not Formal acceptance. Metrics are
+local-only and perform no telemetry or network request.
+
+Core v0.13 also adds deterministic repair and exact-byte offline transport:
+
+```bash
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" repair \
+  --workspace "$PROJECT_ROOT" --run-id "$RUN_ID"
+
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" offline-export \
+  --workspace "$PROJECT_ROOT" --receipt "$RECEIPT" --output "$BUNDLE"
+
+node "$SKILL_ROOT/scripts/runkit-contract/runkit-cli.mjs" offline-import \
+  --workspace "$PROJECT_ROOT" --bundle "$BUNDLE" --store "$OFFLINE_STORE"
+```
+
+Repair must preserve the failed attempt and append replacement lineage. Offline
+export refuses an existing target; import is idempotent only for identical
+bytes. Neither operation grants authority.
+
+Formal cross-project adoption is registry-first adoption. It requires an exact
+published `owlrunkit` version plus matching official npm registry `shasum`,
+`integrity`, tarball URL, and controller-owned release evidence. A local
+worktree, directory, `file:` dependency, local tarball, symlink, workspace link,
+Git ref, or mutable dist-tag may test a release candidate but is not evidence
+for formal adoption.
+
+Do not hand-edit an installed Skill. Inspect or atomically refresh it from an
+authoritative package/repository with:
+
+```bash
+node "$RUNKIT_PACKAGE_ROOT/scripts/runkit-contract/install-codex-skill.mjs" \
+  inspect --target "$RUNKIT_SKILL_TARGET"
+
+node "$RUNKIT_PACKAGE_ROOT/scripts/runkit-contract/install-codex-skill.mjs" \
+  install --repository "$RUNKIT_PACKAGE_ROOT" \
+  --target "$RUNKIT_SKILL_TARGET" --archive "$RUNKIT_SKILL_ARCHIVE_ROOT" \
+  --workspace /absolute/project-a --workspace /absolute/project-b
+```
+
+The install manifest binds every Skill, Core, contract and attest file.
+Unknown installed drift fails closed instead of being overwritten. A changed
+process-wide Skill requires an explicit fleet: pass every project that consumes
+that Skill as a repeated `--workspace`. The installer validates every project
+config and refuses the whole update before replacing the Skill or changing any
+project when one project has an active execution, an active writer lease,
+ambiguous control state, or invalid configuration. Omitting the fleet is an
+error; do not pass a partial fleet to bypass this guard.
+
+A successful update archives the exact prior Skill, migrates each inactive
+project, and writes an append-only upgrade receipt containing the prior Skill
+manifest identity and each prior ConfigV2 byte sequence. Use that receipt for
+an exact rollback:
+
+```bash
+node "$RUNKIT_PACKAGE_ROOT/scripts/runkit-contract/install-codex-skill.mjs" \
+  restore --target "$RUNKIT_SKILL_TARGET" \
+  --archive "$RUNKIT_SKILL_ARCHIVE_ROOT" \
+  --receipt /absolute/path/to/skill-upgrade-receipt.json
+```
+
+If an older unsafe process-wide replacement already drifted a running fleet,
+do not run ordinary `install` or `restore`. Recover only an archived Skill whose
+embedded Core identity exactly matches every affected project config and active
+execution pin:
+
+```bash
+node "$RUNKIT_PACKAGE_ROOT/scripts/runkit-contract/install-codex-skill.mjs" \
+  recover-active --target "$RUNKIT_SKILL_TARGET" \
+  --archive "$RUNKIT_SKILL_ARCHIVE_ROOT" \
+  --archived-installation /absolute/path/to/exact-archived-skill \
+  --workspace /absolute/affected-project
+```
+
+Active recovery changes only the process-wide Skill installation. It preserves
+project config, execution, lease, receipt, and closeout bytes and writes an
+append-only recovery receipt. It refuses an approximate version match or a
+fleet with no matching active execution. An accepted receipt, ready-for-commit
+receipt, package publication, valid install, rollback, or recovery still does
+not grant Git, npm, release, deploy, or foreign-project authority.
+
+## Core v0.15 consolidated onboarding and compatibility
+
+Core v0.14 introduced self-service onboarding. The bundled Core is now
+`0.15.0`; new users should not need internal module calls,
+an external schema validator, or the full Formal lifecycle merely to understand
+whether a project can adopt RunKit.
+
+```bash
+owlrunkit --help
+owlrunkit --version
+owlrunkit doctor --workspace "$PROJECT_ROOT"
+owlrunkit profiles detect --workspace "$PROJECT_ROOT" --dry-run
+owlrunkit profiles validate --workspace "$PROJECT_ROOT"
+owlrunkit profiles impact --workspace "$PROJECT_ROOT" --changed path/to/file
+owlrunkit adopt --workspace "$PROJECT_ROOT" --exact owlrunkit@0.15.0
+```
+
+`doctor` and `profiles detect --dry-run` are read-only. Registry diagnostics use
+a short timeout and distinguish offline or DNS/timeout failures, authorization
+failures, missing versions and local-install binding mismatches without
+printing credentials. Profile detection is deterministic evidence for a human
+decision; it does not write or overwrite project configuration.
+
+`adopt` accepts only an exact `owlrunkit@0.15.0` binding from the official npm
+registry. It recomputes the registry and local install/lock facts, invokes the
+strict adoption evaluator, and writes typed project evidence only after an
+eligible result. Worktrees, `file:` dependencies, local tarballs, Git sources,
+workspace links and mutable tags remain ineligible.
+
+Detected commands use canonical absolute regular-file launchers, including
+NVM-managed npm installs, so a detector result does not conflict with Formal
+symlink rejection. Workspace discovery understands safe literal and one-level
+`apps/*` / `packages/*` patterns and emits exact root-owned npm workspace
+commands. Detection remains dry-run only and never rewrites an existing
+profile.
+
+`doctor` warns when explicit broad formatter, linter, or test-collector
+commands can include `.owlcoda/runkit/`; it never edits ignore or tool
+configuration. `init` and `inspect` consume valid current-version adoption and
+profile facts only while the exact local registry binding remains intact and
+every launcher is Formal-safe; otherwise launcher review or adoption remains
+explicitly incomplete. The recovery action remains authoritative. A rejected
+Formal executable preflight or non-accepted finalize gate is preserved under
+the execution before the CLI returns the result.
+
+Contract v0.2 remains unchanged. Upgrading a 0.13 or 0.14 ConfigV2 project
+is allowed only while its RunKit control state is inactive and unambiguous. An
+active execution or writer lease refuses the upgrade before `config.json` or
+migration evidence changes. A legal refresh writes an exclusive sequenced
+Core-refresh migration receipt and changes only `config.json`; a repeated
+transition cannot replace its first receipt. Compatibility gates invoke npm
+through each selected Node runtime, prove active 0.13/0.14 work blocks 0.15
+before mutation, and prove upgrade-receipt rollback restores the exact prior
+Skill manifest and ConfigV2 bytes. Existing profiles, adoption evidence,
+executions, delivery packets, snapshots, verification receipts, and closeouts
+remain byte-identical and readable. Neither compatibility nor a completed
+onboarding projection grants authority.
+
 ## Choose the smallest assurance lane
 
 Choose the lane before planning. Do not create a Formal execution merely

package/integrations/codex/skills/owlcoda-runkit/assets/templates/config.json

@@ -2,7 +2,7 @@
   "schemaVersion": "OwlCodaRunKitConfigV2",
   "core": {
     "contractVersion": "0.2",
-    "coreVersion": "0.12.0",
+    "coreVersion": "0.15.0",
     "coreManifestSha256": "sha256:replace-with-installed-core-manifest",
     "coreSourceRef": "artifact:sha256:replace-with-content-addressed-source"
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "owlrunkit",
-  "version": "0.13.0",
+  "version": "0.15.0",
   "description": "Project-owned execution, evidence, verification, and recovery for coding agents.",
   "license": "GPL-3.0-or-later",
   "author": "yeemio <owlclaw@163.com>",

package/packages/attest/distribution-manifest-v1.json

@@ -36,6 +36,16 @@
     "sha256": "sha256:3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986"
   },
   "supportedProducerCoreIdentities": [
+    {
+      "contractVersion": "0.2",
+      "coreVersion": "0.15.0",
+      "coreManifestSha256": "sha256:06d7616c369b4b3ece3aca32f05c505d4b30781d3ca87a13bd8d7293c1491f64"
+    },
+    {
+      "contractVersion": "0.2",
+      "coreVersion": "0.14.0",
+      "coreManifestSha256": "sha256:d3b498562bebb2fa180d6861cb834ce3551288bf499ce0d769ee6c64b2663231"
+    },
     {
       "contractVersion": "0.2",
       "coreVersion": "0.13.0",

package/packages/attest/src/quick.mjs

@@ -18,6 +18,16 @@ import { captureWorkspaceSnapshot } from "./workspace-snapshot.mjs";
 export { validQuickReceiptShape } from "./quick-receipt-contract.mjs";
 
 export const SUPPORTED_QUICK_CORE_IDENTITIES = Object.freeze([
+  {
+    contractVersion: "0.2",
+    coreVersion: "0.15.0",
+    coreManifestSha256: "sha256:06d7616c369b4b3ece3aca32f05c505d4b30781d3ca87a13bd8d7293c1491f64",
+  },
+  {
+    contractVersion: "0.2",
+    coreVersion: "0.14.0",
+    coreManifestSha256: "sha256:d3b498562bebb2fa180d6861cb834ce3551288bf499ce0d769ee6c64b2663231",
+  },
   {
     contractVersion: "0.2",
     coreVersion: "0.12.0",

package/registry-release-policy-v1.json

@@ -2,7 +2,7 @@
   "schemaVersion": "OwlCodaRunKitRegistryReleasePolicyV1",
   "status": "release_candidate_unpublished",
   "packageName": "owlrunkit",
-  "candidateVersion": "0.13.0",
+  "candidateVersion": "0.15.0",
   "registry": "https://registry.npmjs.org",
   "registryRequiredBeforeAdoption": true,
   "exactVersionRequired": true,

package/sbom.spdx.json

@@ -2,8 +2,8 @@
   "spdxVersion": "SPDX-2.3",
   "dataLicense": "CC0-1.0",
   "SPDXID": "SPDXRef-DOCUMENT",
-  "name": "owlrunkit-0.13.0",
-  "documentNamespace": "https://owlcoda.com/spdx/owlrunkit/0.13.0",
+  "name": "owlrunkit-0.15.0",
+  "documentNamespace": "https://owlcoda.com/spdx/owlrunkit/0.15.0",
   "creationInfo": {
     "created": "2026-07-29T00:00:00Z",
     "creators": [
@@ -14,8 +14,8 @@
     {
       "name": "owlrunkit",
       "SPDXID": "SPDXRef-Package-OwlRunKit",
-      "versionInfo": "0.13.0",
-      "downloadLocation": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.13.0.tgz",
+      "versionInfo": "0.15.0",
+      "downloadLocation": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.15.0.tgz",
       "filesAnalyzed": false,
       "licenseConcluded": "GPL-3.0-or-later",
       "licenseDeclared": "GPL-3.0-or-later",
@@ -24,7 +24,7 @@
         {
           "referenceCategory": "PACKAGE-MANAGER",
           "referenceType": "purl",
-          "referenceLocator": "pkg:npm/owlrunkit@0.13.0"
+          "referenceLocator": "pkg:npm/owlrunkit@0.15.0"
         }
       ]
     }