@jrpool/kilotest 60.0.6 → 60.0.7

package/README.md

@@ -65,3 +65,36 @@ There is additional documentation at:
 - [llms.txt](llms.txt): basic documentation for LLMs
 - [llms-full.txt](llms-full.txt): comprehensive documentation for LLMs
 - [lhm.plugin.json](lhm.plugin.json): documentation for registration with the LobeHub MCP Market
+
+## Maintenance
+
+These are the routine steps for maintaining Kilotest as currently deployed.
+
+### No API changes
+
+When you make a change in a feature branch **without** any API or tool contract change:
+
+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 authentication).
+6. Wait until `npmjs.com` has processed the publication.
+7. Use `git pull`, `npm ci`, and `pm2 restart kilotest` (but **not** `npm audit fix`) to deploy the revised `main` branch on the public server.
+
+### API changes
+
+When you **make an API or tool contract change** in a feature branch:
+
+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, 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 authentication).
+8. Wait until `npmjs.com` has processed the publication.
+9. Use `git pull`, `npm ci`, and `pm2 restart kilotest` (but **not** `npm audit fix`) 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 in `docs/AI-TOOLS.md` for troubleshooting instructions.

package/docs/AI-TOOLS.md

@@ -62,6 +62,8 @@ The external features that support the use of Kilotest as a collection of AI too
 
 ## Required maintenance
 
+The maintenance routine is prescribed in the [README.md](../README.md) file.
+
 Releasing a new version is a two-script procedure:
 
 - On a feature branch, commit all substantive changes, then execute `npm run prePR -- <level>` (`major`, `minor`, or `patch`). The script bumps `package.json` and `package-lock.json`, regenerates `openapi.yaml`, `openapi-3.0.yaml`, and the versions of `server.json` and `lhm.plugin.json` by explicitly running `npm run generate`, commits and pushes the result, and records the branch name for the next step.
@@ -95,33 +97,6 @@ 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
-
-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` (but **not** `npm audit fix`) 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, 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`, `npm ci`, and `pm2 restart kilotest` (but **not** `npm audit fix`) 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.
-
 ## Use cases
 
 The rationale for Kilotest as a collection of tools for language models is set forth in the `llms-full.txt` file and is not repeated here.

package/lhm.plugin.json

@@ -4423,5 +4423,5 @@
       }
     }
   ],
-  "version": "60.0.6"
+  "version": "60.0.7"
 }

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.6
+  version: 60.0.7
   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.6
+  version: 60.0.7
   license:
     name: MIT
     identifier: MIT

package/package.json

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

package/scripts/postPR.ts

@@ -76,12 +76,13 @@ if (branchVersion !== mainVersion) {
   console.error(`main is at version ${mainVersion} but ${branch} is at ${branchVersion}; merge the pull request first`);
   process.exit(1);
 }
+run('npm', ['login']);
 run('npm', ['publish']);
 run('npm', ['run', 'publish:lhm']);
 // Branch cleanup is best-effort: deletion must precede pruning, because "git branch -d" checks mergedness against the upstream ref, which pruning would remove.
 const deleted = spawnSync('git', ['branch', '-d', branch], {stdio: 'inherit'});
 if (deleted.status !== 0) {
-  console.warn(`Could not delete ${branch}; delete it manually after confirming the merge`);
+  console.warn(`Could not delete ${branch}; delete it after confirming the merge`);
 }
 if (spawnSync('git', ['remote', 'prune', 'origin'], {stdio: 'inherit'}).status !== 0) {
   console.warn('git remote prune origin failed');

package/server.json

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