@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/vitest-4/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/vitest-4/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "vitest-4", "version": "4.0.0" }

package/plugins/vitest-4/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "vitest-4",
+  "version": "4.0.0",
+  "description": "Run isolated tests with module mocks, timer lifecycle and explicit async assertions.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vitest-4/skills/vitest/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: vitest
+description: Write and run Vitest 4 test suites with runner-backed module mocking, asynchronous assertions, mock cleanup, fake timers, and bounded execution using the project's test configuration.
+metadata:
+  target-version: "4.1.11"
+---
+
+# Vitest 4 development workflow
+
+This skill targets Vitest 4.1.11. Read the installed Vitest version, scripts,
+configuration, and environment before applying examples. Use the versioned
+[Vitest 4 documentation](https://v4.vitest.dev/guide/) for this major line; do not
+copy Vitest 5-only APIs into a 4.x suite.
+
+## Run real tests
+
+Place test/it callbacks in files discovered by Vitest and execute the project
+test script or its local vitest run command. Import expect, test, hooks, and vi
+from vitest unless the project intentionally enables globals.
+
+A direct node or bun execution is not a substitute for Vitest's runner and
+module transformation. Do not mark imported vi helpers or unexecuted test
+callbacks as a passing suite.
+
+```ts
+import { expect, test } from "vitest";
+
+test("rejects an unavailable record", async () => {
+  const readRecord = async () => {
+    throw new Error("unavailable");
+  };
+
+  await expect(readRecord()).rejects.toThrow("unavailable");
+});
+```
+
+Await promise assertions and asynchronous work. A test that finishes before an
+assertion runs can report misleading success. Select node, jsdom, happy-dom, or
+Browser Mode to match the system under test; changing environments can change
+what a passing test proves.
+
+## Preserve the project's execution policy
+
+Use a focused file or name filter while developing. On a constrained machine,
+an explicit one-worker, non-parallel-file run can bound resource use:
+
+```sh
+vitest run path/to/feature.test.ts --maxWorkers=1 --no-file-parallelism
+```
+
+This is an invocation choice, not a reason to overwrite a project's established
+pool, browser provider, isolation, coverage, or projects configuration. Vitest 4
+removed poolOptions and moved its supported settings to their new locations;
+check the [migration guide](https://v4.vitest.dev/guide/migration) when upgrading.
+See [fileParallelism](https://v4.vitest.dev/config/fileparallelism) and
+[maxWorkers](https://v4.vitest.dev/config/maxworkers) for the CLI options.
+
+## Mock the dependency boundary
+
+vi.mock is hoisted by the runner. Use vi.hoisted for state required by the mock
+factory, or keep the factory self-contained. Prefer the import-promise form for
+typed module paths. Call the system under test and assert its observable result
+as well as the relevant dependency interaction.
+
+```ts
+import { expect, test, vi } from "vitest";
+import { readUser } from "./service.js";
+import { findUser } from "./repository.js";
+
+vi.mock(import("./repository.js"), () => ({
+  findUser: vi.fn(async (id: string) => ({ id, name: "Ada" })),
+}));
+
+test("reads a user through its repository", async () => {
+  await expect(readUser("u1")).resolves.toBe("Ada");
+  expect(findUser).toHaveBeenCalledWith("u1");
+});
+```
+
+Mocking an exported function does not replace calls to that function from inside
+the same module. Choose a separable dependency boundary when that matters. ESM
+namespace spying also differs in Browser Mode; a Node suite does not establish
+that a browser mock works. See the [mocking guide](https://v4.vitest.dev/guide/mocking).
+
+## Keep cleanup intentional
+
+| Operation                     | Intended effect                                                                                                                           |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| mockClear / clearAllMocks     | Clear recorded calls while preserving the implementation.                                                                                 |
+| mockReset / resetAllMocks     | Clear mock state and reset implementations; vi.fn(initialImplementation) resets to its initial implementation.                            |
+| mockRestore / restoreAllMocks | Restore spied-on original methods. In Vitest 4, restoreAllMocks does not clear each spy's recorded history or restore automocked exports. |
+
+Choose clearMocks, mockReset, and restoreMocks for the suite's intended state
+model rather than enabling all of them blindly. Restore fake timers and explicit
+global/environment stubs even when assertions fail:
+
+```ts
+import { afterEach, expect, test, vi } from "vitest";
+
+afterEach(() => {
+  vi.useRealTimers();
+  vi.restoreAllMocks();
+  vi.unstubAllGlobals();
+  vi.unstubAllEnvs();
+});
+
+test("resolves after a delay", async () => {
+  vi.useFakeTimers();
+  const result = new Promise((resolve) => {
+    setTimeout(() => resolve("ready"), 100);
+  });
+
+  await vi.advanceTimersByTimeAsync(100);
+  await expect(result).resolves.toBe("ready");
+});
+```
+
+Do not combine fake timers and concurrent tests sharing global state. The
+[vi API](https://v4.vitest.dev/api/vi) documents reset and restoration behavior.
+
+## Completion evidence
+
+Check the runner exit code and executed test count. Distinguish passing tests,
+expected failures, skipped tests, and failures; an empty run or generated report
+alone is not proof of success. Report the exact Vitest version, environment, and
+targeted command. Coverage and typechecking are separate checks: transformed
+TypeScript tests do not prove their types are valid.

package/plugins/vitest-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "vitest-5",
+  "version": "5.0.0",
+  "description": "Use Vitest ^5.0.0 standalone assertions and mock functions correctly, while avoiding APIs that require the Vitest runner and accounting for v5 migration changes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vitest-5/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/vitest-5/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/vitest-5/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "vitest-5", "version": "5.0.0" }

package/plugins/vitest-5/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "vitest-5",
+  "version": "5.0.0",
+  "description": "Use Vitest ^5.0.0 standalone assertions and mock functions correctly, while avoiding APIs that require the Vitest runner and accounting for v5 migration changes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/vitest-5/skills/vitest/SKILL.md

@@ -0,0 +1,186 @@
+---
+name: vitest
+description: Use Vitest ^5.0.0 standalone assertions and mock functions correctly, while avoiding APIs that require the Vitest runner and accounting for v5 migration changes.
+---
+
+Verified against vitest@5.0.0 on 2026-09-07. 5 of 5 examples executed.
+
+# Vitest ^5.0.0
+
+## Requirements
+
+Vitest 5 requires Node.js >= 22.12.0 and Vite >= 6.4.0.
+
+Assertions are bundled into `vitest`; import `expect`, `vi`, and test APIs from `vitest` rather than relying on `@vitest/expect`.
+
+## What can run in a plain script
+
+A plain script can directly exercise assertions and several mock-function APIs exported by `vitest`. The examples below are standalone files: they do not use the Vitest runner.
+
+### Assertions
+
+Use `expect` from `vitest` for matchers such as `toBe`, `toBeCloseTo`, and `toContain`.
+
+```ts pmcp-example
+import { expect } from 'vitest'
+
+expect(Math.sqrt(4)).toBe(2)
+expect(Math.sqrt(144)).toBe(12)
+expect(Math.sqrt(0)).toBe(0)
+expect(0.1 + 0.2).toBeCloseTo(0.3)
+expect('vitest').toContain('test')
+```
+
+`expect.assertions(count)` is documented for checking the number of assertions made during a test run; it is not a standalone assertion-counting mechanism to rely on in an ordinary script.
+
+### Mock functions
+
+`vi.fn()` creates a mock function. Calls are recorded even when the function has no implementation, in which case it returns `undefined`.
+
+```ts pmcp-example
+import { expect, vi } from 'vitest'
+
+const getApples = vi.fn()
+
+getApples()
+
+expect(getApples).toHaveBeenCalled()
+expect(getApples).toHaveBeenCalledTimes(1)
+expect(getApples()).toBeUndefined()
+```
+
+### Spying on an object method
+
+`vi.spyOn(object, key)` creates a mock around an existing object method. Restore it with `vi.restoreAllMocks()` when the original implementation should be put back.
+
+```ts pmcp-example
+import { expect, vi } from 'vitest'
+
+const calculator = {
+  add(a: number, b: number) {
+    return a + b
+  },
+}
+
+const add = vi.spyOn(calculator, 'add')
+
+expect(calculator.add(2, 3)).toBe(5)
+expect(add).toHaveBeenCalledWith(2, 3)
+
+vi.restoreAllMocks()
+expect(calculator.add(1, 1)).toBe(2)
+```
+
+### Conditional mock behavior with `vi.when`
+
+Vitest 5 adds argument-based behavior configuration for mocks. Chain `calledWith(...).thenReturn(...)` clauses to return different values for different arguments.
+
+```ts pmcp-example
+import { expect, vi } from 'vitest'
+
+const spy = vi.fn()
+
+vi.when(spy)
+  .calledWith(1)
+  .thenReturn('one')
+  .calledWith(2)
+  .thenReturn('two')
+
+expect(spy(1)).toBe('one')
+expect(spy(2)).toBe('two')
+```
+
+### Mock lifecycle APIs
+
+- `vi.clearAllMocks()` clears recorded calls while preserving mock implementations.
+- `vi.resetAllMocks()` resets mock state and restores the mock's initial implementation. For a mock created with an implementation, that initial implementation remains available.
+- `vi.restoreAllMocks()` restores spied-on originals.
+
+Vitest 5 also defaults `clearMocks` to `true`, so the runner calls `vi.clearAllMocks()` before every test while preserving implementations.
+
+```ts pmcp-example
+import { expect, vi } from 'vitest'
+
+const mock = vi.fn(() => 'value')
+
+mock()
+expect(mock).toHaveBeenCalledTimes(1)
+
+vi.clearAllMocks()
+expect(mock).toHaveBeenCalledTimes(0)
+expect(mock()).toBe('value')
+
+vi.resetAllMocks()
+expect(mock()).toBe('value')
+```
+
+`vi.mockObject(value)` is not a standalone API in this environment: it reaches for Vitest's initialized mocker and throws when no runner has initialized it. Use it only under Vitest's transformed module runner.
+
+## APIs that require the Vitest runner
+
+Importing `test` or `it` from `vitest` is not enough to execute tests in an ordinary script. The callback is collected and run by Vitest's runner or its CLI/build integration.
+
+The documented form is:
+
+```ts
+import { expect, test } from 'vitest'
+
+test('Math.sqrt works for perfect squares', () => {
+  expect(Math.sqrt(4)).toBe(2)
+})
+```
+
+Test callbacks can receive a test context. Documented built-ins include `task`, `expect`, `signal`, `bench`, `onTestFailed`, and `onTestFinished`:
+
+```ts
+import { it } from 'vitest'
+
+it('math is easy', ({ expect }) => {
+  expect(2 + 2).toBe(4)
+})
+```
+
+These snippets belong in files executed by Vitest, not in a direct `bun example.ts` invocation.
+
+## v5 benchmarks
+
+Benchmarks moved into regular tests through the `bench` test-context fixture. The old standalone shape is not the v5 shape:
+
+```ts
+import { test } from 'vitest'
+
+test('sort', async ({ bench }) => {
+  await bench('sort', () => {
+    [3, 1, 2].sort()
+  }).run()
+})
+```
+
+`bench.skip`, `bench.only`, and `bench.todo` were removed. Use `test.skip`, `test.only`, and `test.todo` around the containing test instead. The `bench` fixture is runner-provided, so this is not a standalone Bun example.
+
+## Module mocking
+
+`vi.mock` substitutes imported modules and works with `import`, not `require`. Vitest statically analyzes and hoists it, so calls must be at module top level in v5:
+
+```ts
+import { vi } from 'vitest'
+
+vi.mock('./path/to/module.js', () => ({
+  default: { myDefaultKey: vi.fn() },
+  namedExport: vi.fn(),
+}))
+```
+
+Module mocking depends on Vitest's transformed module runner and is intended for test files. It is not equivalent to ordinary standalone Node or Bun module behavior. Unlike `vi.mock`, `vi.doMock` and `vi.doUnmock` remain non-hoisted.
+
+Do not put `vi.mock`, `vi.unmock`, or `vi.hoisted` inside a function or nested scope in v5; nested calls throw.
+
+## v5 migration traps
+
+- Replace removed `test.sequential`, `describe.sequential`, and `sequential` options with `concurrent: false`.
+- Do not use the former top-level `bench(...)` API for v5 benchmarks; use the test-context `bench` fixture.
+- Do not import removed entrypoints such as `vitest/coverage`, `vitest/reporters`, `vitest/environments`, `vitest/snapshot`, `vitest/runners`, `vitest/suite`, `vitest/mocker`, or `vitest/internal/module-runner`. The migration replacements include `vitest/node`, `vitest/runtime`, `TestRunner` from `vitest`, static `TestRunner` methods, and `@vitest/mocker`.
+
+## Not covered
+
+This skill does not cover Vitest configuration, CLI invocation, runner/build integration, environment setup, reporters, coverage configuration, snapshots, the complete matcher catalog, custom matcher implementation, module-resolution details, `vi.mockObject` outside the runner, or the full test-context lifecycle API. Those areas require the Vitest runner or additional documentation beyond the supplied research.

package/plugins/whatwg-mimetype-5/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "whatwg-mimetype-5",
+  "version": "5.0.0",
+  "description": "Use whatwg-mimetype ^5.0.0 to parse, inspect, mutate, serialize, classify, and compute MIME types from resource bytes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/whatwg-mimetype-5/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.