@jrpool/kilotest 63.2.1 → 63.2.2

package/content.ts

@@ -8,15 +8,5 @@
 // Brief description of the Kilotest tool collection. Used as the MCP server description and as lhm.plugin.json’s top-level description. No length limit.
 export const collectionDescription = 'Tools that test web pages with an ensemble of 12 rule engines for front-end quality (accessibility, usability, and W3C web standards, including HTML, CSS, ARIA, and WCAG)';
 
-// Description of the Kilotest domain and data hierarchy. Used as (1) the McpServer
-// instructions, which is the only place most tools' own descriptions (everything but
-// getKilotestOverview) get this context from, since repeating it in each of their
-// descriptions would dilute how models read each tool, (2) the first paragraph of the
-// kilotestOverview prose that mcp.ts returns from the getKilotestOverview tool and the
-// kilotest-overview resource, (3) the opening paragraph of llms.txt, (4) the start of the
-// openapi.yaml info.description, and (5) the getKilotestOverview tool's own description and
-// the kilotest-overview resource's own description, because some MCP clients do not
-// propagate the McpServer instructions to their models, so getKilotestOverview and the
-// kilotest-overview resource (unlike the other tools) carry the context redundantly, in both
-// their own description and their returned body.
+// Description of the Kilotest domain and data hierarchy. Used as (1) the McpServer instructions, which is the only place most tools' own descriptions (everything but getKilotestOverview) get this context from, since repeating it in each of their descriptions would dilute how models read each tool, (2) the first paragraph of the kilotestOverview prose that mcp.ts returns from the getKilotestOverview tool and the kilotest-overview resource, (3) the opening paragraph of llms.txt, (4) the start of the openapi.yaml info.description, and (5) the getKilotestOverview tool's own description and the kilotest-overview resource's own description, because some MCP clients do not propagate the McpServer instructions to their models, so getKilotestOverview and the kilotest-overview resource (unlike the other tools) carry the context redundantly, in both their own description and their returned body.
 export const sharedContext = 'Kilotest integrates an ensemble of 12 rule engines, with about 1,300 rules, to test web pages for front-end quality (accessibility, usability, and W3C web standards, including HTML, CSS, ARIA, and WCAG). Each test job generates a standardized report describing which elements violated which rules and grouping the violations into about 380 issues. Kilotest can list the tested pages, the reports about each page, the issues in each report, the violators of each issue, and the diagnoses of each violation. Kilotest also accepts requests to test pages not yet tested and to retest already tested pages.';

package/docs/AI-TOOLS.md

@@ -97,8 +97,10 @@ A change to the tool or API contract (tool names, parameter names, schemas, resp
 - `openapi-3.0.yaml`: an OpenAPI 3.0.3 conversion of `openapi.yaml`, regenerated by the same hook, for registries whose importers reject 3.1 documents; never edit it by hand.
 - `server.json`: contains only the server descriptor (name, description, repository, remotes, version), no tool schemas. Its version is synced by `update-versions.ts`; edit it manually only if the server description or remote URL changes.
 - `lhm.plugin.json`: embeds every tool’s input and output schema and its descriptions, in the LobeHub manifest format. Its `description` and every tool’s `description`, `inputSchema`, `outputSchema`, and `annotations` are regenerated from `mcp.ts`/`api/schemas.ts` by `scripts/generate-lhm.ts` (run by `npm run generate`, part of `npm run prePR`); never edit those fields by hand. The remaining fields (`author`, `cloudEndpoint`, `homepage`, `identifier`, `name`, `prompts`, `resources`, `tags`, `version`, and each tool’s `execution` block) have no canonical source elsewhere and are still edited manually. See `docs/decisions/010-content-generation.md`.
-- `content.ts`: canonical prose shared verbatim by `mcp.ts`, `scripts/generate-openapi.ts`, and `scripts/generate-lhm.ts`. Also hand-check `llms.txt`’s opening paragraph, which is supposed to match `content.ts`’s `sharedContext` verbatim but is not generated.
+- `content.ts`: canonical prose shared verbatim by `mcp.ts`, `scripts/generate-openapi.ts`, `scripts/generate-lhm.ts`, and `scripts/generate-llms.ts` (which regenerates `llms.txt`'s opening paragraph from `sharedContext`); all four are run by `npm run generate`, so no hand-checking is needed there. `scripts/check-docs.ts` (also run by `npm run lint`) separately verifies that `llms.txt` and `llms-full.txt`'s quoted `/api/...` paths and parameters still match `api/routes.ts`.
 - `llms-full.txt`, `capability.md`, `README.md`, `docs/openai-plugin/skills/kilotest-overview/SKILL.md`: hand-maintained, intentionally paraphrased rather than copied verbatim; search them for stale parameter and path names after a contract change.
+- `docs/openai-plugin/plugin.json`: hand-maintained, submitted to OpenAI's plugin review (see "Registrations" above); its `review.test_cases[].tools_triggered` fields name actual tools verbatim (e.g. `"listPages, listIssues"`), so check them, not just the paraphrased prose fields, after a contract change. Its `version` and `release_notes` track revisions to this plugin submission (the manifest, the skill, and the test cases) and are unrelated to `package.json`'s version; `update-versions.ts` does not touch this file, so bump `version` and add a `release_notes` entry by hand whenever the submission changes.
+- `docs/openai-plugin/mcp.json`: hand-maintained, but contains only the server's type and URL, so a contract change never requires editing it.
 
 #### External registries that update themselves, needing no maintainer action
 

package/lhm.plugin.json

@@ -18,7 +18,7 @@
     "wcag",
     "web standards"
   ],
-  "version": "63.2.1",
+  "version": "63.2.2",
   "description": "Tools that test web pages with an ensemble of 12 rule engines for front-end quality (accessibility, usability, and W3C web standards, including HTML, CSS, ARIA, and WCAG)",
   "tools": [
     {

package/openapi-3.0.yaml

@@ -2,7 +2,7 @@ openapi: 3.0.3
 info:
   title: Kilotest API
   description: 'Kilotest integrates an ensemble of 12 rule engines, with about 1,300 rules, to test web pages for front-end quality (accessibility, usability, and W3C web standards, including HTML, CSS, ARIA, and WCAG). Each test job generates a standardized report describing which elements violated which rules and grouping the violations into about 380 issues. Kilotest can list the tested pages, the reports about each page, the issues in each report, the violators of each issue, and the diagnoses of each violation. Kilotest also accepts requests to test pages not yet tested and to retest already tested pages. Kilotest acts as a web server for human users, an MCP server for AI platforms, and an API for programmatic access. With this API you can request that a page be tested or retested, discover available reports, and incrementally retrieve facts from a report: from what reports are available, to what issues were reported in one report, to what elements violated one issue, to what diagnoses rule engines gave for one violation.'
-  version: 63.2.1
+  version: 63.2.2
   license:
     name: MIT
     url: https://github.com/jrpool/kilotest/blob/main/LICENSE

package/openapi.yaml

@@ -2,7 +2,7 @@ openapi: 3.1.0
 info:
   title: Kilotest API
   description: 'Kilotest integrates an ensemble of 12 rule engines, with about 1,300 rules, to test web pages for front-end quality (accessibility, usability, and W3C web standards, including HTML, CSS, ARIA, and WCAG). Each test job generates a standardized report describing which elements violated which rules and grouping the violations into about 380 issues. Kilotest can list the tested pages, the reports about each page, the issues in each report, the violators of each issue, and the diagnoses of each violation. Kilotest also accepts requests to test pages not yet tested and to retest already tested pages. Kilotest acts as a web server for human users, an MCP server for AI platforms, and an API for programmatic access. With this API you can request that a page be tested or retested, discover available reports, and incrementally retrieve facts from a report: from what reports are available, to what issues were reported in one report, to what elements violated one issue, to what diagnoses rule engines gave for one violation.'
-  version: 63.2.1
+  version: 63.2.2
   license:
     name: MIT
     identifier: MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jrpool/kilotest",
-  "version": "63.2.1",
+  "version": "63.2.2",
   "description": "Ensemble testing for front-end web quality",
   "type": "module",
   "main": "index.ts",

package/server.json

@@ -6,7 +6,7 @@
     "url": "https://github.com/jrpool/kilotest",
     "source": "github"
   },
-  "version": "63.2.1",
+  "version": "63.2.2",
   "remotes": [
     {
       "type": "streamable-http",