@modootoday/pmcp 0.13.1 → 0.14.0

package/plugins/typescript-eslint-8/skills/typescript-eslint/SKILL.md

@@ -0,0 +1,179 @@
+---
+name: typescript-eslint
+description: Use typescript-eslint v8's unified flat-config package, extension lists, presets, and typed-linting configuration. Avoid carrying forward the split-package or legacy ESLint configuration shape unless the project explicitly uses legacy config.
+---
+
+Verified against typescript-eslint@8.70.0 on 2026-09-08. 3 of 3 examples executed.
+
+Those historical examples inspect exports and configuration composition only.
+The separate ESLint 9/10 fixtures exercise actual typed linting and project
+service behavior; their execution evidence is tracked separately.
+
+# typescript-eslint v8
+
+## Use the unified package first
+
+For v8, install the unified package:
+
+```sh
+npm i -D typescript-eslint@8
+```
+
+The main package exports `config`, `configs`, `extensions`, `globs`, `parser`, `plugin`, and `FlatConfig`. Its `parser` and `plugin` exports provide the TypeScript parser and ESLint plugin surfaces.
+
+The preferred v8 setup is ESLint flat config. The recommended and stylistic presets already configure the TypeScript parser and plugin, so do not manually register them when using those presets.
+
+```js
+import js from "@eslint/js";
+import { defineConfig } from "eslint/config";
+import tseslint from "typescript-eslint";
+
+export default defineConfig({
+  files: ["**/*.{js,ts}"],
+  extends: [js.configs.recommended, tseslint.configs.recommended],
+});
+```
+
+`tseslint.config(...)` accepts any number of ESLint configuration objects, but it is deprecated. Prefer ESLint core's `defineConfig(...)` for new flat configurations.
+
+## File extensions and globs
+
+Use the exported extension lists instead of duplicating them:
+
+- `extensions.ts`: `['mts', 'ts', 'cts', 'tsx']`
+- `extensions.js`: `['mjs', 'js', 'cjs', 'jsx']`
+- `extensions.jsts`: both sets; do not rely on the order of this combined list
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import tseslint from "typescript-eslint";
+
+assert.deepEqual(tseslint.extensions.ts, ["mts", "ts", "cts", "tsx"]);
+assert.deepEqual(tseslint.extensions.js, ["mjs", "js", "cjs", "jsx"]);
+assert.deepEqual(
+  [...tseslint.extensions.jsts].sort(),
+  ["mjs", "js", "cjs", "jsx", "mts", "ts", "cts", "tsx"].sort(),
+);
+
+const customGlob = `src/**/*.{${tseslint.extensions.ts.join(",")}}`;
+assert.equal(customGlob, "src/**/*.{mts,ts,cts,tsx}");
+```
+
+## Main package exports
+
+A plain script can inspect and compose the main package exports without running ESLint:
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import tseslint from "typescript-eslint";
+
+assert.equal(typeof tseslint.config, "function");
+assert.equal(typeof tseslint.parser, "object");
+assert.equal(typeof tseslint.plugin, "object");
+assert.equal(typeof tseslint.configs.recommended, "object");
+assert.ok(tseslint.extensions.ts.includes("ts"));
+assert.ok(tseslint.extensions.js.includes("js"));
+```
+
+Do not assume that the parser export has a `parse` method. The package exposes the parser object, but that particular method is not part of the verified standalone surface.
+
+The `config` helper is still available for compatibility, but new configuration should use ESLint's `defineConfig`. When using `config`, pass ESLint configuration objects rather than legacy string-based `extends` entries.
+
+```ts pmcp-example
+import assert from "node:assert/strict";
+import tseslint from "typescript-eslint";
+
+const result = tseslint.config({
+  files: ["**/*.ts"],
+  extends: [tseslint.configs.recommended],
+  rules: {
+    "@typescript-eslint/array-type": "error",
+  },
+});
+
+assert.ok(Array.isArray(result));
+assert.ok(result.length > 0);
+```
+
+## Typed linting
+
+Type-aware rules need TypeScript project/type information. They are not enabled merely by selecting a TypeScript parser. In flat config, use parser options with `projectService: true`:
+
+```js
+import { defineConfig } from "eslint/config";
+import tseslint from "typescript-eslint";
+
+export default defineConfig({
+  files: ["src/**/*.ts"],
+  extends: [tseslint.configs.recommendedTypeChecked],
+  languageOptions: {
+    parserOptions: {
+      projectService: true,
+      tsconfigRootDir: import.meta.dirname,
+    },
+  },
+});
+```
+
+The type-checked preset names in v8 are `recommendedTypeChecked` and `stylisticTypeChecked`. The hyphenated names `recommended-type-checked` and `stylistic-type-checked` are the legacy names commonly shown in older configuration examples.
+
+`projectService` uses TypeScript's editor-style service and generally replaces manually specifying `project` paths or creating a separate `tsconfig.eslint.json`. It is parser configuration consumed by ESLint; it is not a standalone typed-linting switch for an arbitrary script.
+
+## Parser utilities
+
+The research describes parser utilities such as `createProgram(configFile, projectDirectory?)` and `withoutProjectParserOptions(options)`. However, the verified `typescript-eslint` v8 standalone package export does not expose the tested utility methods through `tseslint.parser`; do not write code that assumes `tseslint.parser.createProgram` or `tseslint.parser.withoutProjectParserOptions` exists.
+
+These APIs are therefore not demonstrated here. Parser configuration and typed project services are primarily consumed while ESLint runs the configuration.
+
+## Legacy configuration warning
+
+Older projects may still use the split packages and `.eslintrc` shape:
+
+```js
+module.exports = {
+  extends: ["eslint:recommended", "plugin:@typescript-eslint/recommended"],
+  parser: "@typescript-eslint/parser",
+  plugins: ["@typescript-eslint"],
+  root: true,
+};
+```
+
+That setup requires separately installed `@typescript-eslint/parser` and `@typescript-eslint/eslint-plugin` and is run through ESLint. Do not translate it mechanically into v8 flat config: use the unified `typescript-eslint` package and its exported presets instead. v8 supports ESLint v9 and flat config; v7 was the first version with flat-config support.
+
+## Execute typed linting
+
+Version 8.70.0's peer range supports ESLint 8.57+, 9 and 10, and TypeScript
+`>=4.8.4 <6.1`. Earlier 8.x patches can have different supported ranges. Check the
+installed parser/plugin versions instead of installing a second incompatible
+copy as a workaround.
+
+Run the project's installed ESLint CLI on a real file inside its tsconfig.
+projectService uses the editor-style project boundary; files outside it need
+a separate untyped scope or a deliberately narrow default-project allowance.
+Keep allowDefaultProject bounded rather than matching all source files.
+
+```sh
+eslint src/example.ts --max-warnings=0
+eslint --print-config src/example.ts
+```
+
+Verify a type-aware rule with a source case that actually needs type information,
+such as an unhandled promise. Check both the intended failing case and a valid
+handled case. Parsing or importing the rule preset alone is not a typed-lint
+verification. Keep compiler diagnostics under the project's own typecheck.
+
+## What this skill does not cover
+
+- The detailed contents of every preset or every rule.
+- Creating a real TypeScript `Program` from a filesystem project.
+- The standalone `@typescript-eslint/project-service` API, including `createProjectService`, its settings, and lifecycle.
+- The separate `@typescript-eslint/utils` package and its exported AST, scope, and utility APIs.
+- Parser utility methods not verified on the unified package's standalone parser export.
+- Legacy ESLint configuration migration details beyond the v8 versus older configuration shapes described above.
+
+## Sources
+
+- [Unified package](https://typescript-eslint.io/packages/typescript-eslint/)
+- [Typed linting and project service](https://typescript-eslint.io/getting-started/typed-linting/)
+- [Troubleshooting typed linting](https://typescript-eslint.io/troubleshooting/typed-linting/)
+- [ESLint flat configuration](https://eslint.org/docs/latest/use/configure/configuration-files)

package/plugins/typescript-eslint-eslint-plugin-8/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "typescript-eslint-eslint-plugin-8",
+  "version": "8.0.0",
+  "description": "Use @typescript-eslint/eslint-plugin v8 exports, legacy preset names, rule definitions, typed-linting requirements, and v8 migration constraints.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/typescript-eslint-eslint-plugin-8/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/typescript-eslint-eslint-plugin-8/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/typescript-eslint-eslint-plugin-8/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "typescript-eslint-eslint-plugin-8", "version": "8.0.0" }

package/plugins/typescript-eslint-eslint-plugin-8/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "typescript-eslint-eslint-plugin-8",
+  "version": "8.0.0",
+  "description": "Use @typescript-eslint/eslint-plugin v8 exports, legacy preset names, rule definitions, typed-linting requirements, and v8 migration constraints.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/typescript-eslint-eslint-plugin-8/skills/typescript-eslint-eslint-plugin/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: typescript-eslint-eslint-plugin
+description: Use @typescript-eslint/eslint-plugin v8 exports, legacy preset names, rule definitions, typed-linting requirements, and v8 migration constraints.
+---
+
+Verified against @typescript-eslint/eslint-plugin@8.70.0 on 2026-09-08. 3 of 3 examples executed.
+
+# @typescript-eslint/eslint-plugin
+
+## What this package provides
+
+`@typescript-eslint/eslint-plugin` v8 is an ESLint plugin used to load typescript-eslint rules and configuration lists. Its documented exports are:
+
+- `configs`: named ESLint configuration settings.
+- `rules`: rule objects.
+
+The rules rely on `@typescript-eslint/parser` for TypeScript ASTs and, for type-aware rules, TypeScript programs.
+
+```ts pmcp-example
+import * as plugin from '@typescript-eslint/eslint-plugin';
+import assert from 'node:assert/strict';
+
+assert.equal(typeof plugin.configs, 'object');
+assert.equal(typeof plugin.rules, 'object');
+assert.equal(typeof plugin.configs.recommended, 'object');
+assert.equal(typeof plugin.rules['no-unused-vars'], 'object');
+```
+
+## Configuration names: do not mix package shapes
+
+The plugin's legacy configuration names are exposed through `plugin.configs` and are used by `.eslintrc.*` through `plugin:@typescript-eslint/...` strings. Documented legacy preset strings include:
+
+- `plugin:@typescript-eslint/recommended`
+- `plugin:@typescript-eslint/recommended-type-checked`
+- `plugin:@typescript-eslint/strict`
+- `plugin:@typescript-eslint/stylistic`
+- `plugin:@typescript-eslint/eslint-recommended`
+
+The direct property names for this plugin's legacy presets are not the camel-cased names from the `typescript-eslint` meta-package's flat-config API. In particular, do not assume that `plugin.configs.recommendedTypeChecked` exists: importing this package directly with v8 can leave that property undefined.
+
+```ts pmcp-example
+import * as plugin from '@typescript-eslint/eslint-plugin';
+import assert from 'node:assert/strict';
+
+const legacyNames = [
+  'recommended',
+  'recommended-type-checked',
+  'strict',
+  'stylistic',
+  'all',
+  'base',
+  'disable-type-checked',
+  'eslint-recommended',
+];
+
+for (const name of legacyNames) {
+  assert.equal(typeof plugin.configs[name], 'object', `missing config: ${name}`);
+}
+
+assert.equal(plugin.configs.recommendedTypeChecked, undefined);
+```
+
+This distinction is a common v8 mistake. Names such as `recommendedTypeChecked`, `strictTypeChecked`, `stylisticTypeChecked`, and the `...Only` variants are documented configuration names for the newer `typescript-eslint` configuration surface, not names to blindly substitute for properties on this plugin export.
+
+## Rules
+
+Rule definitions are available by rule name in `rules`. For example, `no-unused-vars` is exposed as a rule object:
+
+```ts pmcp-example
+import * as plugin from '@typescript-eslint/eslint-plugin';
+import assert from 'node:assert/strict';
+
+const rule = plugin.rules['no-unused-vars'];
+assert.equal(typeof rule, 'object');
+assert.ok(rule !== null);
+```
+
+A plain script can inspect these definitions, but this package does not itself run ESLint rules. Rule execution is performed by ESLint with the plugin and parser configured.
+
+## Legacy `.eslintrc.*` setup
+
+The older configuration shape remains supported in v8 and is still common. Legacy setup requires both the parser and plugin registration for TypeScript files:
+
+```js
+module.exports = {
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/recommended',
+    'plugin:@typescript-eslint/stylistic',
+  ],
+  parser: '@typescript-eslint/parser',
+  plugins: ['@typescript-eslint'],
+  root: true,
+};
+```
+
+Type-aware legacy presets can be selected with their hyphenated names:
+
+```js
+module.exports = {
+  extends: [
+    'plugin:@typescript-eslint/recommended-type-checked',
+    'plugin:@typescript-eslint/strict',
+    'plugin:@typescript-eslint/stylistic',
+    'plugin:@typescript-eslint/eslint-recommended',
+  ],
+  parser: '@typescript-eslint/parser',
+  plugins: ['@typescript-eslint'],
+};
+```
+
+Do not use a legacy `extends` string as though it were a camel-cased property on `plugin.configs`, and do not omit the parser when linting TypeScript syntax.
+
+## Flat config and v8
+
+v8 has full ESLint v9 support while retaining legacy configuration support. The newer flat-config shape uses the `typescript-eslint` meta-package and object configs:
+
+```js
+import js from '@eslint/js';
+import { defineConfig } from 'eslint/config';
+import tseslint from 'typescript-eslint';
+
+export default defineConfig({
+  files: ['**/*.{js,ts}'],
+  extends: [js.configs.recommended, tseslint.configs.recommended],
+});
+```
+
+For flat config, the documentation says that `@typescript-eslint/eslint-plugin` and `@typescript-eslint/parser` do not need to be installed explicitly. Do not mechanically copy the legacy `plugins: ['@typescript-eslint']` setup into this flat-config example.
+
+## Typed linting
+
+Type-aware presets require typed-linting parser options. In v8, `projectService` is the stabilized option replacing experimental `EXPERIMENTAL_useProjectService`:
+
+```js
+languageOptions: {
+  parserOptions: {
+    projectService: true,
+  },
+},
+```
+
+The `recommended-type-checked` and `strict-type-checked` presets require this setup. `disable-type-checked` is provided for files such as JavaScript overrides.
+
+Importing a rule or config in a standalone script does not provide typed linting. The parser and TypeScript program are supplied by the ESLint configuration and tool execution.
+
+## v8 rule and configuration changes
+
+Do not copy older rule lists into v8 unchanged:
+
+- `ban-types` was replaced by `no-restricted-types`, `no-unsafe-function-type`, and `no-wrapper-object-types`.
+- `no-empty-object-type` was split from `ban-types` / `no-empty-interfaces`.
+- `no-unnecessary-type-parameters` moved to `strict`.
+- `no-throw-literal`, `no-useless-template-literals`, and the `no-loss-of-precision` extension rule were removed or deprecated.
+
+## Does not cover
+
+This skill does not cover ESLint's complete CLI or API, the complete contents or options of individual rules and presets, TypeScript project configuration, parser installation details beyond the documented setup, or running linting in a framework or repository. Rule execution and typed linting are exercised by ESLint itself rather than by this package's standalone exports.

package/plugins/typescript-eslint-estree-8/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "typescript-eslint-estree-8",
+  "version": "8.0.0",
+  "description": "Use @typescript-eslint/typescript-estree ^8 to parse TypeScript into ESTree-compatible ASTs, distinguish plain parsing from type-aware services, and avoid v7 configuration shapes.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/typescript-eslint-estree-8/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/typescript-eslint-estree-8/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/typescript-eslint-estree-8/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "typescript-eslint-estree-8", "version": "8.0.0" }