@modootoday/pmcp 0.13.0 → 0.14.0

package/plugins/npm-run-path-6/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/npm-run-path-6/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "npm-run-path-6", "version": "6.0.0" }

package/plugins/npm-run-path-6/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "npm-run-path-6",
+  "version": "6.0.0",
+  "description": "Use npm-run-path ^6.0.0 to construct npm-style PATH values or environment objects for Node child processes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/npm-run-path-6/skills/npm-run-path/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: npm-run-path
+description: Use npm-run-path ^6.0.0 to construct npm-style PATH values or environment objects for Node child processes.
+---
+
+Verified against npm-run-path@6.0.0 on 2026-09-08. 3 of 3 examples executed.
+
+# npm-run-path
+
+`npm-run-path` 6.0.0 is an ESM package requiring Node.js 18 or newer. Import its two named exports:
+
+```ts
+import {npmRunPath, npmRunPathEnv} from 'npm-run-path';
+```
+
+It supplies PATH data; it is not a runner or CLI. Use the returned environment with Node's `child_process` APIs when launching a local binary outside an npm script.
+
+## API
+
+### `npmRunPath(options?): string`
+
+Returns an augmented PATH string. Its options are:
+
+- `cwd?: string | URL` — defaults to `process.cwd()`.
+- `execPath?: string | URL` — defaults to `process.execPath`.
+- `addExecPath?: boolean` — defaults to `true`.
+- `preferLocal?: boolean` — defaults to `true`.
+- `path?: string` — the input PATH value; this option belongs to `npmRunPath()` only.
+
+### `npmRunPathEnv(options?): ProcessEnv`
+
+Returns an augmented environment object based on `process.env`. Its options are:
+
+- `cwd?: string | URL` — defaults to `process.cwd()`.
+- `execPath?: string | URL` — defaults to `process.execPath`.
+- `addExecPath?: boolean` — defaults to `true`.
+- `preferLocal?: boolean` — defaults to `true`.
+- `env?: ProcessEnv` — the input environment; this option belongs to `npmRunPathEnv()` only.
+
+`ProcessEnv` is `Record<string, string | undefined>`.
+
+## Examples
+
+### Construct a PATH and an environment
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {npmRunPath, npmRunPathEnv} from 'npm-run-path';
+
+const path = npmRunPath({
+  path: '/usr/bin',
+  preferLocal: false,
+  addExecPath: false,
+});
+
+assert.equal(path, '/usr/bin');
+
+const env = npmRunPathEnv({
+  env: {
+    PATH: '/usr/bin',
+    CUSTOM_VALUE: 'kept',
+  },
+  preferLocal: false,
+  addExecPath: false,
+});
+
+assert.equal(env.PATH, '/usr/bin');
+assert.equal(env.CUSTOM_VALUE, 'kept');
+```
+
+### Pass the generated environment to a child process
+
+The package does not execute commands itself. Pass `npmRunPathEnv()` to a Node child-process API:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import childProcess from 'node:child_process';
+import {npmRunPathEnv} from 'npm-run-path';
+
+const output = childProcess.execFileSync(
+  process.execPath,
+  ['-e', 'process.stdout.write(process.env.PMCP_VALUE ?? "")'],
+  {
+    env: npmRunPathEnv({
+      env: {
+        ...process.env,
+        PMCP_VALUE: 'available-to-child',
+      },
+      preferLocal: false,
+      addExecPath: false,
+    }),
+    encoding: 'utf8',
+  },
+);
+
+assert.equal(output, 'available-to-child');
+```
+
+### Use the options supported by the current type surface
+
+`cwd` and `execPath` accept either strings or URLs. `path` is for `npmRunPath`; `env` is for `npmRunPathEnv`. Do not interchange those option names.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {npmRunPath, npmRunPathEnv} from 'npm-run-path';
+
+const path = npmRunPath({
+  cwd: new URL('.', import.meta.url),
+  execPath: process.execPath,
+  path: '/custom/path',
+  preferLocal: false,
+  addExecPath: false,
+});
+assert.equal(path, '/custom/path');
+
+const environment = npmRunPathEnv({
+  cwd: new URL('.', import.meta.url),
+  execPath: process.execPath,
+  env: {PATH: '/custom/path'},
+  preferLocal: false,
+  addExecPath: false,
+});
+assert.equal(environment.PATH, '/custom/path');
+```
+
+## Common mistakes
+
+- **Using CommonJS imports:** v6 is ESM (`"type": "module"`). Use named ESM imports from `npm-run-path`.
+- **Expecting the package to run a command:** it only computes PATH data. Launch the command with Node's `child_process` APIs and provide `env: npmRunPathEnv()`.
+- **Using the wrong input option:** `path` is accepted by `npmRunPath()`, while `env` is accepted by `npmRunPathEnv()`.
+- **Assuming the older major has a different API:** the v5.3.0 examples use effectively the same two-function shape and option names. Code copied from that older documentation is still representative, but v6 requires Node.js 18 or newer.
+- **Forgetting the defaults:** local npm binaries are preferred by default, the executable path is added by default, and the current working directory and `process.execPath` are used by default.
+- **Re-augmenting a PATH without considering v6 behavior:** v6 makes the operation idempotent and handles an empty PATH better.
+
+## Not covered
+
+This skill does not cover the internal directory-search algorithm, the exact ordering of every generated PATH segment, platform-specific PATH details, or the separate `npm-run-path-cli` package. It also does not cover runner-injected globals such as `describe`, `it`, or `expect`; examples here are standalone Bun scripts.

package/plugins/nyc-18/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "nyc-18",
+  "version": "18.0.0",
+  "description": "Use nyc 18.x for its CommonJS API, coverage-file lifecycle, directory resolution, and CLI/runner boundaries. Covers the Node runtime change from nyc 17.x and avoids standalone examples that depend on runner or subprocess internals.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/nyc-18/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/nyc-18/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/nyc-18/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "nyc-18", "version": "18.0.0" }

package/plugins/nyc-18/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "nyc-18",
+  "version": "18.0.0",
+  "description": "Use nyc 18.x for its CommonJS API, coverage-file lifecycle, directory resolution, and CLI/runner boundaries. Covers the Node runtime change from nyc 17.x and avoids standalone examples that depend on runner or subprocess internals.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/nyc-18/skills/nyc/SKILL.md

@@ -0,0 +1,152 @@
+---
+name: nyc
+description: Use nyc 18.x for its CommonJS API, coverage-file lifecycle, directory resolution, and CLI/runner boundaries. Covers the Node runtime change from nyc 17.x and avoids standalone examples that depend on runner or subprocess internals.
+---
+
+Verified against nyc@18.0.0 on 2026-09-08. 3 of 3 examples executed.
+
+# nyc 18.x
+
+## Runtime and package shape
+
+`nyc` 18.0.0 exposes one CommonJS export: the `NYC` class.
+
+```js
+const NYC = require('nyc')
+const nyc = new NYC({ cwd: process.cwd() })
+```
+
+The supported Node engine is `20 || >=22`. This is the important migration difference from nyc 17.x: nyc 17 had already raised its minimum Node version to 18, while nyc 18's transitive dependencies require Node 20 or Node 22 and newer. Do not assume a Node 18 runtime is sufficient.
+
+The constructor copies the supplied configuration. Relevant fields are:
+
+- `cwd`: base directory; defaults to `process.cwd()`.
+- `tempDirectory` or the older alias `tempDir`: temporary coverage directory; defaults to `./.nyc_output`.
+- `reportDir`: report directory; defaults to `coverage`.
+- `reporter`: one reporter or an array; defaults to `text`.
+
+`tempDirectory()` and `reportDirectory()` return absolute paths resolved from `cwd`.
+
+```ts pmcp-example
+const assert = require('node:assert/strict')
+const NYC = require('nyc')
+const path = require('node:path')
+
+const nyc = new NYC({
+  cwd: '/workspace/project',
+  tempDirectory: '.coverage-data',
+  reportDir: 'artifacts/coverage',
+  reporter: ['text', 'lcov']
+})
+
+assert.equal(nyc.cwd, '/workspace/project')
+assert.deepEqual(nyc.reporter, ['text', 'lcov'])
+assert.equal(nyc.tempDirectory(), path.resolve('/workspace/project', '.coverage-data'))
+assert.equal(nyc.reportDirectory(), path.resolve('/workspace/project', 'artifacts/coverage'))
+```
+
+When using older configuration, `tempDir` is still accepted. Prefer `tempDirectory` in new code, but do not replace it with an unrelated field name.
+
+```ts pmcp-example
+const assert = require('node:assert/strict')
+const NYC = require('nyc')
+const path = require('node:path')
+
+const nyc = new NYC({ cwd: '/repo', tempDir: 'tmp/nyc' })
+
+assert.equal(nyc.tempDirectory(), path.resolve('/repo', 'tmp/nyc'))
+assert.equal(nyc.reportDirectory(), path.resolve('/repo', 'coverage'))
+assert.deepEqual(nyc.reporter, ['text'])
+```
+
+## Instrumentation
+
+The programmatic instrumentation methods exposed by the class are:
+
+- `instrumenter()`
+- `addFile(filename)`: reads and instruments a named file.
+- `wrap(bin)`: wraps a command or executable and returns the same `NYC` instance.
+
+`instrumenter()` is a plain API call, but `wrap()` reaches into subprocess/runtime internals. It is not suitable for a standalone `bun example.ts` example: in this execution environment it requires an internal Node binding that Bun does not implement. Exercise wrapping through nyc's supported command-line/tool execution instead.
+
+`addFile()` performs file I/O and instrumentation. Supply an actual source filename when invoking it in a real application; a nonexistent filename is not a valid no-op.
+
+## Coverage files
+
+`writeCoverageFile()` writes coverage data. `coverageFiles(baseDirectory)` asynchronously reads the directory and returns the result of `fs.readdir`; when no directory is supplied it uses `tempDirectory()`.
+
+`coverageFileLoad(filename, baseDirectory)` asynchronously parses the named JSON coverage file. Its default base directory is `tempDirectory()`. If loading or parsing fails, it returns `{}` rather than throwing for that failure.
+
+```ts pmcp-example
+const assert = require('node:assert/strict')
+const NYC = require('nyc')
+
+;(async () => {
+  const nyc = new NYC({ cwd: process.cwd() })
+  const loaded = await nyc.coverageFileLoad('missing-coverage-file.json', process.cwd())
+
+  assert.deepEqual(loaded, {})
+})()
+```
+
+Use `coverageFiles()` only after the temporary coverage directory exists. Use `writeCoverageFile()` after instrumentation has produced coverage data; these methods are filesystem operations, not in-memory configuration helpers.
+
+## Temporary directories, reset, and reports
+
+The lifecycle methods are:
+
+- `createTempDirectory()`: asynchronously creates the temporary coverage directory.
+- `reset()`: resets nyc's coverage state.
+- `report()`: creates reports using the configured reporters.
+- `getCoverageMapFromAllCoverageFiles(baseDirectory)`: asynchronously combines coverage files; the base directory is the coverage temporary directory when omitted.
+
+`report()` creates reports using the configured reporters. Ensure that coverage data and the temporary directory are available before calling it.
+
+## CLI and runner boundary
+
+nyc is the Istanbul command-line client. In CLI usage, nyc options must appear before the program it executes:
+
+```json
+{
+  "scripts": {
+    "test": "mocha",
+    "coverage": "nyc npm run test"
+  }
+}
+```
+
+A direct CLI form is:
+
+```sh
+nyc --reporter=lcov --reporter=text-summary ava
+```
+
+The command being measured follows nyc's options. nyc wraps test runners or npm scripts; it is not a replacement for the runner.
+
+Do not put `describe`, `it`, or `expect` in a standalone `bun example.ts` example. Those names are normally supplied by a test runner and are not provided by nyc.
+
+`jest` and `tap` already include IstanbulJS libraries. For those runners, use their coverage configuration rather than installing nyc unnecessarily.
+
+## Configuration loading
+
+Loading nyc configuration is provided separately by `@istanbuljs/load-nyc-config`, not by the documented nyc CLI surface. Its `loadNycConfig()` API is asynchronous and does not consider command-line arguments:
+
+```js
+const {loadNycConfig} = require('@istanbuljs/load-nyc-config')
+;(async () => {
+  console.log(await loadNycConfig())
+})()
+```
+
+Do not treat this utility as if it resolved nyc CLI flags.
+
+## What this skill does not cover
+
+- The complete nyc CLI option list or command-line parsing behavior.
+- Test-runner-specific setup for Mocha, Ava, Jest, Tap, or other runners.
+- Using `wrap()` in a standalone Bun script; its subprocess internals require the tool/runtime execution path.
+- The exact shape of instrumented source and coverage-map objects.
+- Reporter-specific output formats or reporter configuration beyond selecting reporter names.
+- The contents of nyc configuration files.
+- Source-map, exclude/include, subprocess, or caching behavior not shown by the supplied research.
+- How to implement a complete filesystem-backed coverage lifecycle in an application.

package/plugins/ow-3/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "ow-3",
+  "version": "3.0.0",
+  "description": "Use ow ^3.0.0 for runtime validation in Node.js 20+ ESM code. Covers the v3 API, validation results, predicates, modifiers, custom predicates, TypeScript inference, and v2-to-v3 migration traps.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/ow-3/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.