@modootoday/pmcp 0.13.0 → 0.14.0

package/plugins/jasmine-core-7/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/jasmine-core-7/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/jasmine-core-7/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "jasmine-core-7", "version": "7.0.1" }

package/plugins/jasmine-core-7/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "jasmine-core-7",
+  "version": "7.0.1",
+  "description": "Use jasmine-core ^7.0.0 directly from Node: install its globals into a chosen object, inspect the core version, reset shared state, and define Jasmine specs, expectations, spies, and not-applicable specs. It is not the Jasmine CLI or test runner.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/jasmine-core-7/skills/jasmine-core/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: jasmine-core
+description: "Use jasmine-core ^7.0.0 directly from Node: install its globals into a chosen object, inspect the core version, reset shared state, and define Jasmine specs, expectations, spies, and not-applicable specs. It is not the Jasmine CLI or test runner."
+---
+
+Verified against jasmine-core@7.0.2 on 2026-09-08. 5 of 5 examples executed.
+
+# jasmine-core 7.x
+
+## What this package is
+
+`jasmine-core` is the Jasmine core/assets package. In Node, importing it returns an automatically-created core instance. The same instance is returned on every import. Node does not install globals automatically.
+
+Node test discovery, test-file loading, configuration, and terminal execution belong to the separate `jasmine` package. Browser execution belongs to the browser tooling. This package alone is not a CLI runner.
+
+## Import and booting in 7.x
+
+```js
+const jasmineCore = require('jasmine-core');
+```
+
+The module exposes the documented module members and the Jasmine globals. It does **not** expose `boot`, `noGlobals`, or `jasmineRequire`.
+
+Install globals explicitly when a script needs the global Jasmine API:
+
+```js
+jasmineCore.installGlobals();
+```
+
+`installGlobals(dest)` copies the Jasmine globals to `dest`; if `dest` is omitted, it uses `globalThis`. The exported globals include `describe`, `it`, `expect`, `expectAsync`, lifecycle hooks, spy helpers, pending/focused/disabled spec helpers, spec-property helpers, `throwUnless`, and `notApplicable`.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import jasmineCore from "jasmine-core";
+
+const target: Record<string, unknown> = {};
+jasmineCore.installGlobals(target);
+
+for (const name of ["describe", "it", "expect", "spyOn", "notApplicable"]) {
+  assert.equal(typeof target[name], "function", `${name} should be installed`);
+}
+assert.equal(typeof (globalThis as any).describe, "undefined");
+```
+
+## State and version
+
+`version()` returns the jasmine-core version. `reset()` removes specs, suites, and reporters and restores default configuration. Use `reset()` between independent runs in the same process because imports share the automatically-created core instance.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import jasmineCore from "jasmine-core";
+
+assert.equal(typeof jasmineCore.version(), "string");
+assert.match(jasmineCore.version(), /^7\./);
+assert.equal(typeof jasmineCore.reset, "function");
+
+jasmineCore.reset();
+```
+
+## Defining specs and expectations
+
+After installing globals into a destination, use the installed functions from that destination rather than assuming Node globals exist. A spec has the form `describe(description, specDefinitions)`, with `it(description, testFunction, timeout)` for examples and `expect(actual)` for expectations.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import jasmineCore from "jasmine-core";
+
+const j: Record<string, any> = {};
+jasmineCore.installGlobals(j);
+
+assert.doesNotThrow(() => {
+  j.describe("a suite", () => {
+    j.it("passes", () => {
+      j.expect(true).toBe(true);
+    });
+  });
+});
+```
+
+Defining a suite is not the same as executing it. Use the separate Jasmine runner/tooling when you need discovery, loading, configuration, reporters, and terminal execution.
+
+## Spies
+
+The documented spy helpers are:
+
+- `spyOn(obj, methodName)`, returning a `Spy`.
+- `spyOnAllFunctions(obj, includeNonEnumerable)`, returning the spied object.
+- `spyOnProperty(obj, propertyName, accessType)`, returning a `Spy`.
+
+They are intended for use in Jasmine specs or another correctly initialized Jasmine environment.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import jasmineCore from "jasmine-core";
+
+const j: Record<string, any> = {};
+jasmineCore.installGlobals(j);
+
+assert.equal(typeof j.spyOn, "function");
+assert.equal(typeof j.spyOnAllFunctions, "function");
+assert.equal(typeof j.spyOnProperty, "function");
+
+const object = { greet() { return "hello"; } };
+assert.doesNotThrow(() => {
+  j.describe("spies", () => {
+    j.it("can define a method spy", () => {
+      const spy = j.spyOn(object, "greet");
+      assert.equal(typeof spy, "object");
+    });
+  });
+});
+```
+
+## Pending versus not applicable
+
+Jasmine 7 adds `notApplicable(reason)`. It marks a spec as not applicable, which is distinct from `pending`. Reporters must handle the `notApplicable` status; results can include `notApplicableReason`.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import jasmineCore from "jasmine-core";
+
+const j: Record<string, any> = {};
+jasmineCore.installGlobals(j);
+assert.equal(typeof j.notApplicable, "function");
+assert.equal(typeof j.pending, "function");
+
+assert.doesNotThrow(() => {
+  j.describe("environment-specific behavior", () => {
+    j.it("is not applicable here", () => {
+      j.notApplicable("This environment does not provide the required feature");
+    });
+  });
+});
+```
+
+## 6.x shapes that are wrong in 7.x
+
+Do not carry these older boot patterns forward:
+
+```js
+// 6.x — not a 7.x Node API
+const jasmineCore = require('jasmine-core');
+jasmineCore.boot();
+```
+
+Use:
+
+```js
+const jasmineCore = require('jasmine-core');
+jasmineCore.installGlobals();
+```
+
+Likewise, `noGlobals()` was removed. In 7.x, simply importing the module is the no-automatic-globals behavior; call `installGlobals()` only when globals are wanted. To discard state, use `installGlobals()` as needed and then `reset()`; do not use the old `boot(false)` shape.
+
+The 7.0 module redesign also removed most private APIs, stopped exposing `jasmineRequire`, and blocks monkey-patching. Do not depend on removed `HtmlReporter`, `HtmlSpecFilter`, or `jsApiReporter` surfaces.
+
+## Configuration and integration migration notes
+
+The documented 7.x migration uses a runner's `configureDefaultReporter` API rather than the old configuration shape:
+
+```js
+const runner = new Jasmine();
+runner.configureDefaultReporter({
+  color: false,
+  alwaysListPendingSpecs: false
+});
+```
+
+`jsLoader: "require"` is no longer supported; remove it or provide a custom loader. These runner configuration APIs are not APIs of the `jasmine-core` module itself.
+
+## Does not cover
+
+This skill does not cover the separate `jasmine` CLI/runner, browser runner boot files, test discovery or file loading, reporter implementation, complete matcher/async-matcher behavior, the full environment API, custom loaders, or migration details not documented in the supplied research. It also does not cover Zone.js or Karma integration; the supplied 7.0 notes state that Zone.js cannot be used with 7.x and current `karma-jasmine` is incompatible.

package/plugins/jest-cli-30/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "jest-cli-30",
+  "version": "30.0.0",
+  "description": "Use jest-cli 30 programmatically and avoid Jest 29 CLI/API shapes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/jest-cli-30/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/jest-cli-30/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/jest-cli-30/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "jest-cli-30", "version": "30.0.0" }

package/plugins/jest-cli-30/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "jest-cli-30",
+  "version": "30.0.0",
+  "description": "Use jest-cli 30 programmatically and avoid Jest 29 CLI/API shapes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/jest-cli-30/skills/jest-cli/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: jest-cli
+description: Use jest-cli 30 programmatically and avoid Jest 29 CLI/API shapes.
+---
+
+Verified against jest-cli@30.5.1 on 2026-09-08. 2 of 2 examples executed.
+
+# jest-cli 30
+
+## Surface
+
+`jest-cli` exposes exactly three named exports:
+
+```ts
+buildArgv(maybeArgv?: string[]): Promise<Config.Argv>
+run(maybeArgv?: string[], project?: string): Promise<void>
+yargsOptions: {[key: string]: Options}
+```
+
+Use the package's documented exports rather than deep imports into Jest internals. Jest 30 bundles internals, so paths such as `jest-runner/build/testWorker` are not stable.
+
+## Parse CLI arguments with `buildArgv`
+
+`buildArgv` asynchronously converts an argument array into Jest's parsed argument object. Pass only the arguments that would follow the `jest` command.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {buildArgv} from 'jest-cli';
+
+const argv = await buildArgv(['--runInBand']);
+assert.equal(argv.runInBand, true);
+```
+
+CLI values take precedence over configuration values when Jest runs. Flags requiring values are validated; for example, `--maxWorkers` and `--selectProjects` must be given values.
+
+## Run Jest programmatically
+
+`run` starts the Jest command-line runner and resolves when the run completes:
+
+```ts
+import {run} from 'jest-cli';
+
+await run(['--runInBand'], process.cwd());
+```
+
+The runner needs an actual Jest project and test-runner environment. It is not demonstrated as a standalone executable example here because the required examples run with no test files, configuration file, framework globals, filesystem setup, or network access. Ordinary `jest` and `npm test` usage is the supported runner boundary.
+
+Programmatic users of lower-level APIs such as `jest.runCLI` must provide the newly required `globalConfig` in Jest 30. Prefer the documented `jest-cli` exports instead of relying on internals.
+
+## Inspect the option definitions
+
+`yargsOptions` is the exported map of CLI option definitions. The package declaration does not document a complete list of keys or additional behavior.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import {yargsOptions} from 'jest-cli';
+
+assert.equal(typeof yargsOptions, 'object');
+assert.notEqual(yargsOptions, null);
+```
+
+## Jest 30 CLI changes
+
+### Rename `--testPathPattern`
+
+Jest 29 code commonly uses:
+
+```sh
+jest --testPathPattern="unit/.*"
+```
+
+In Jest 30, use the plural option:
+
+```sh
+jest --testPathPatterns "unit/.*" "integration/.*"
+```
+
+Multiple patterns can be space-separated or supplied repeatedly. `--testPathPattern` was renamed to `--testPathPatterns`.
+
+### `--init` was removed
+
+Do not use:
+
+```sh
+jest --init
+```
+
+Use the package-manager generators instead:
+
+```sh
+npm init jest@latest
+yarn create jest
+pnpm create jest
+```
+
+### Filter result shape
+
+A custom `--filter` implementation must return an object with an array property:
+
+```ts
+{filtered: string[]}
+```
+
+Returning an array directly is the older shape.
+
+## Common Jest 29-era mistakes
+
+These changes are outside the three `jest-cli` exports but affect projects upgraded to Jest 30:
+
+- Replace `expect(fn).toBeCalled()` with `expect(fn).toHaveBeenCalled()`; matcher aliases were removed.
+- Replace `jest.genMockFromModule('fs')` with `jest.createMockFromModule('fs')`; `genMockFromModule` was removed.
+- Ensure `jest.mock()` module paths use exact case.
+- Custom sequencers receive additional context in Jest 30.
+
+## Runtime requirements
+
+Jest 30 requires Node 18.x or later. Node 14, 16, 19, and 21 are unsupported. The minimum TypeScript version is 5.4. `jest-environment-jsdom` uses JSDOM 26.
+
+## Not covered
+
+This skill does not document the complete `yargsOptions` key set, Jest configuration options, test discovery, custom sequencer APIs, the detailed `globalConfig` shape for lower-level runner APIs, or how to construct a runnable Jest project. Those require behavior or documentation not covered by the supplied research.

package/plugins/jest-extended-7/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "jest-extended-7",
+  "version": "7.0.0",
+  "description": "Use jest-extended v7 matchers with a Jest/Vitest-compatible expect.extend host, and understand the small subset that can be exercised directly without a test runner.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}