@jrpool/kilotest 60.0.3 → 60.0.5

package/docs/AI-TOOLS.md

@@ -95,19 +95,29 @@ A change to the tool or API contract (tool names, parameter names, schemas, resp
 - The LobeHub MCP Market listing is published from `lhm.plugin.json` and is non-automated, because LobeHub requires browser-based OAuth. A normal release pushes the updated file when `npm run postPR` runs `npm run publish:lhm`; to push a contract update without a release, run `npm run publish:lhm` manually.
 - The RapidAPI Hub listing stores a copy of the API endpoints. Its importer accepts only OpenAPI 3.0 documents, so after releasing a contract change, update the definition in Studio: `My APIs` → the Kilotest API project → `Hub Listing` → `Definitions` → `CI/CD` → `Import OpenAPI`, and upload the regenerated `openapi-3.0.yaml` (not `openapi.yaml`, which is 3.1 and is rejected). The `/publish/…` pages contain only listing metadata, not the spec.
 
-#### Step by step
+### Step by step
 
-When you make an API or tool contract change in a feature branch, here are all the maintenance steps:
+When you make a change in a feature branch **without** any API or tool contract change, here are the maintenance steps:
+
+1. Stage, commit, and optionally push all changes.
+2. Execute `npm run prePR -- <level>` (`major`, `minor`, or `patch`).
+3. Submit a pull request.
+4. When all checks succeed, squash-merge to `main` and delete the feature branch on GitHub.
+5. Execute `npm run postPR` (with interactive browser OAuth).
+6. Wait until `npmjs.com` has processed the publication.
+7. Use `git pull`, `npm ci`, and `pm2 restart kilotest` to deploy the revised `main` branch on the public server.
+
+When you **make an API or tool contract change** in a feature branch, here are the maintenance steps:
 
 1. `lhm.plugin.json`: Transform it to match `api/schemas.ts` and `mcp.ts`.
 2. `llms.txt`, `llms-full.txt`, `capability.md`, `README.md`: Update parameter and path names.
-3. Stage and commit all changes.
+3. Stage, commit, and optionally push all changes.
 4. Execute `npm run prePR -- <level>` (`major`, `minor`, or `patch`).
 5. Submit a pull request.
 6. When all checks succeed, squash-merge to `main`.
 7. Execute `npm run postPR` (with interactive browser OAuth).
 8. Wait until `npmjs.com` has processed the publication.
-9. Use `git pull` and `pm2 restart kilotest` to deploy the revised `main` branch on the public server.
+9. Use `git pull`, `npm ci`, and `pm2 restart kilotest` to deploy the revised `main` branch on the public server.
 10. Visit the [RapidAPI Studio](https://rapidapi.com/studio) and update the API definition at `Hub Listing` → `Definitions` → `CI/CD` → `Import OpenAPI` by uploading the regenerated `openapi-3.0.yaml`.
 
 If any step fails, see the details above for troubleshooting instructions.

package/lhm.plugin.json

@@ -4423,5 +4423,5 @@
       }
     }
   ],
-  "version": "60.0.3"
+  "version": "60.0.5"
 }

package/openapi-3.0.yaml

@@ -2,7 +2,7 @@ openapi: 3.0.3
 info:
   title: Kilotest API
   description: 'Kilotest is an ensemble testing and reporting service for front-end web quality. It uses an ensemble of 12 rule engines to test web pages for front-end quality (accessibility, usability, and web standards, including HTML, CSS, ARIA, and WCAG). 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, 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: 60.0.3
+  version: 60.0.5
   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 is an ensemble testing and reporting service for front-end web quality. It uses an ensemble of 12 rule engines to test web pages for front-end quality (accessibility, usability, and web standards, including HTML, CSS, ARIA, and WCAG). 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, 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: 60.0.3
+  version: 60.0.5
   license:
     name: MIT
     identifier: MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jrpool/kilotest",
-  "version": "60.0.3",
+  "version": "60.0.5",
   "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": "60.0.3",
+  "version": "60.0.5",
   "remotes": [
     {
       "type": "streamable-http",