@jrpool/kilotest 46.0.11 → 46.1.0

package/docs/AI-TOOLS.md

@@ -4,56 +4,71 @@
 
 Until 2026 Kilotest was intended, and implemented, as a web application performing a service for human users.
 
-Beginning in May 2026, it [became evident](https://github.com/jrpool/kilotest/issues/2) that Kilotest could also act as a provider of tools for use by language models. Language models are asked for help in all domains, including the domain of software quality. When asked about the front-end quality (accessibility, usability, and standards conformity) of specific web pages, models gave answers without the use of tools. The answers were at best fragmentary but often speculative and fabricated. If Kilotest provided its functionalities to language models, models could give more inexpensive, comprehensive, factual, authoritative, and grounded answers. Every reported defect could be documented and ascribed to one or more specific rule engines in the Kilotest ensemble.
+Beginning in May 2026, it [became evident](https://github.com/jrpool/kilotest/issues/2) that Kilotest could operate as a set of tools for language models to allow them to improve their answers to questions about the front-end quality (accessibility, usability, and standards conformity) of specific web pages.
 
-Given the potential of Kilotest to serve language models and the expected continued growth in the share of questions that are directed to AI platforms that use language models, a decision was made to **make Kilotest discoverable, usable, and, where appropriate, used as a provider of tools for language models**.
+A decision was made to **make Kilotest discoverable, usable, and, where appropriate, used as a provider of tools for language models**.
 
 ## Terms
 
-- **Language model**: A model (e.g., Claude Haiku 4.5, Kimi K2.6, GPT-5.4, Gemini 3.1 Pro) that can consume and generate text, images, or other content.
+- **Language model**: A model (e.g., Claude Haiku 4.5, Kimi K2.7, GPT-5.4, Gemini 3.1 Pro) that can consume and generate text, images, or other content.
 - **AI platform**: A platform (e.g., Claude Desktop, Perplexity, ChatGPT, Gemini 3.5 Flash) that gives human users access to the services of language models and connects language models to productivity resources.
 - **tool**: A specialized productivity resource providing a capability that a language model needs but does not have. In the OpenAPI specification, the term _operation_ is used to mean tool.
 - **connector**: A service that allows AI platforms to enable their language models to discover, evaluate, and use tools.
 
-## Internal additions
+## Internal features
 
-The internal changes that have been made in the Kilotest codebase to support the use of Kilotest as a collection of tools are:
+The internal features that make Kilotest a collection of tools for language models are:
 
-- An API, consisting of:
-  - Additions to `index.js`.
-  - Additions to `util.js`.
-  - An `api` directory containing:
-    - Eight tool modules.
-    - A `util.js` module with shared functions used by tool modules.
-    - A `routes.js` file.
-    - A `schemas.js` file.
-    - A `testSuite.js` module for testing the API.
+- An API, with specific functional and utility modules in the `api` directory.
+- Tests of the functionalities of the API.
 - A [`JSON-LD`](https://json-ld.org/) script in the `index.html` file, providing structured data about the Kilotest API.
-- Additions to the `env.example` file.
+- Environment variables in the `env.example` file.
 - An `llms.txt` file and an `llms-full.txt` file, documenting the use of Kilotest by language models, conforming to the [llms-txt](https://llmstxt.org/) specification.
-- An `openapi.yaml` file, documenting the Kilotest API, conforming to the [OpenAPI specification](https://spec.openapis.org/oas/v3.1.0).
+- A generated `openapi.yaml` file, documenting the Kilotest API, conforming to the [OpenAPI specification](https://spec.openapis.org/oas/v3.1.0).
 - An `mcp.js` file, providing an MCP server for Kilotest.
+- A `server.json` file, conforming to the [MCP server schema](https://modelcontextprotocol.io/), and a GitHub Actions workflow (`publish-mcp.yml`) that authenticates via GitHub OIDC and publishes that file to the official MCP Registry whenever `server.json` or `api/version.js` changes on the `main` branch.
+- A `capability.md` file with a URL, summarizing what Kilotest tools can do.
+- `mcp`, `mcp-server`, and `modelcontextprotocol` keywords in `package.json`, supporting discovery of the `@jrpool/kilotest` npm package by tools and humans searching the npm registry for MCP servers.
+- An `lhm.plugin.json` file, conforming to the [LobeHub plugin manifest format](https://market.lobehub.com/s/publish-mcp/references/manifest), declaring Kilotest as a plugin in the [LobeHub MCP Market](https://lobehub.com/mcp). Publishing and updating are non-automated (`lhm plugin publish`/`update`), because LobeHub requires browser-based OAuth and does not support machine-to-machine publishing.
 - A `sitemap.xml` file.
-- Additions to the `README.md` file.
+- Documentation in the `README.md` file.
 - This `AI-TOOLS.md` file.
 - A [tutorial on authorizing language models to use Kilotest](https://kilotest.com/qai/).
 
-## External actions
+## External features
 
-The external actions that have been taken to support the use of Kilotest as a collection of AI tools are:
+The external features that support the use of Kilotest as a collection of AI tools are:
 
 - A [pull request](https://github.com/public-apis/public-apis/pull/6346/changes) to add Kilotest to the list of public APIs in the `public-apis` repository.
 - An [issue](https://github.com/APIs-guru/openapi-directory/issues/2677) to add Kilotest to `openapi-directory`.
 - A [pull request](https://github.com/w3c/wai-evaluation-tools-list/pull/1153) to add Kilotest to the WAI evaluation tools list.
+- Registration of Kilotest as an active server in the [official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=kilotest) (`io.github.jrpool/kilotest`), maintained by the [Model Context Protocol](https://modelcontextprotocol.io/) project. The [PulseMCP](https://www.pulsemcp.com/servers) directory and the VS Code MCP gallery both crawl this registry, so Kilotest is discoverable through them with no separate submission.
 - Registration of Kilotest with the [Smithery](https://smithery.ai/servers/pool/kilotest) MCP server registry.
 - Registration of Kilotest with the [Glama](https://glama.ai/mcp/connectors/com.kilotest/kilotest) MCP server registry.
+- Registration of Kilotest with [Awesome MCP Servers](https://www.tensorblock.co/mcp/servers/github-jrpool-kilotest-f518ba36).
 - Registration of Kilotest with the [RapidAPI](https://rapidapi.com/jrpool/api/kilotest/playground/apiendpoint_0f03577a-ff9a-472a-a0ed-533bd198981a) Hub.
+- Registration of Kilotest with the [LobeHub MCP Market](https://lobehub.com/mcp) (identifier: `jrpool-kilotest`), enabled with an `lhm.plugin.json` file.
 - Deployment of an MCP server in HTTP mode on the Kilotest service host.
 - Configuration of Claude Desktop on the local development host and the `claude.ai` web application to connect Claude Desktop models to the Kilotest MCP server. The configuration was performed in the UI of each platform with the addition of Kilotest as a _connector_. The user used the `Customize/Connectors/Add connector/Add custom connector` interface, providing these data before activating the `Add` button:
 
   - Name: Kilotest
   - Remote MCP server URL: `https://kilotest.com/mcp`
 
+- MCP-related topics added to the [repository details](https://github.com/jrpool/kilotest).
+- An [MCP Registry badge](https://registry.modelcontextprotocol.io/v0/servers?search=kilotest) added to the `README.md` file.
+- A link to the MCP server on the `README.md` page of the [`testaro-issues`](https://github.com/jrpool/testaro-issues) repository.
+- Registration of Kilotest and its sitemap at [Google Search Console](https://search.google.com/search-console?resource_id=sc-domain:kilotest.com) and [Bing Webmaster Tools](https://www.bing.com/webmasters/home?siteUrl=https://kilotest.com/).
+
+## Required maintenance
+
+Whenever the `/api/version.js` file is updated:
+
+- Update the `server.json` file (version field).
+- Update the `lhm.plugin.json` file (version field).
+- Regenerate `openapi.yaml` (`npm run generate:openapi`).
+- Create a pull request and merge to `main` (triggers `publish-mcp.yml` automatically for the MCP Registry).
+- Execute `lhm plugin update --dir .` (for LobeHub).
+
 ## 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.
@@ -71,148 +86,46 @@ Among these use cases, case 3 would make it feasible for the user to tell an AI
 
 Use cases 1, 2, 4, 5, and 6 exemplify a widespread expectation and demand for AI platform capability. The commonality is: “I have a question; answer it.” If Kilotest can be employed as an expert for AI platforms in relevant cases, platforms will be more successful in satisfying that demand. At present this is a difficult problem because of platform limitations and a lack of standardization.
 
-## Implementation strategy
-
-Connector and tool discovery and utilization have been only partly standardized. Major differences in protocols exist among model and platform families. Therefore, small testable increments of improvement in the connector and tool functionality of Kilotest can best be defined by model and platform family and by use-case characteristics.
-
-One benefit of such incrementalism is that, after the first increment succeeds, it becomes possible to make and test external changes publicizing the fact that a particular platform-model combination delivers unprecedentedly inexpensive, comprehensive, and truthful answers in a particular class of use cases to questions about front-end web quality.
-
-Another benefit is that subsequent increments can be defined incrementally rather than in advance. Lessons learned from the work on each increment can inform the choice of what to work on next.
-
-## Implementation history
-
-The Kilotest project has been attempting to solve the just-described problem. A chronology of this work follows.
-
-### Increment 1
-
-In the first increment, the objective was to make Anthropic Claude models use Kilotest to help them answer questions from developers using the Claude Desktop application for use case 3, where the code in question is already deployed as a public web page.
-
-A locally installed MCP server, `@ivotoby/openapi-mcp-server`, was used. It turned out to be incompatible with Claude Desktop, so even though connections to Kilotest were made and calls to its tools were submitted the responses did not arrive.
-
-The model behavior motivated an architectural change in the MCP server and improvements in the naming and description of the Kilotest tools before the next increment.
-
-### Increment 2
-
-Increment 2 repeated the exercise of increment 1 with the `claude.ai` web application instead of Claude Desktop, and with the improvements indicated by increment 1 made.
-
-With Kilotest added as a custom connector, the user asked the platform, “I want to know whether the home page of the nonprofit organization named ‘Open Secrets’ has quality defects, such as with accissibility [_sic_] and usability.”
-
-It was discovered that Claude Haiku 4.5 with Extended capability used Kilotest tools, but Claude Haiku 4.5 without Extended capability did not.
-
-When Kilotest was used, it was used appropriately for the task, but the planning was suboptimal, because the model initially stated an intention to recommend the web page for testing instead of first checking for an existing available report on it.
-
-The output to the user was a mixture of Kilotest results with knowledge and judgments of the model. Kilotest results were presented with some selective pruning, interpretation, and advice on what to do.
-
-The trial in increment 2 suggested some opportunities for further improvements:
-
-- Clearer instructions about the sequencing of tool calls
-- Addition of instructions to attribute the interpretive additions by the model to the model or its other sources rather than to Kilotest.
-
-### Increment 3
-
-After the above-described improvements were made, a similar exercise, with the home page of a company named “CMT Services”, was performed again in Claude Desktop. In this case Claude Haiku 4.5 succeeded in recognizing the relevance of Kilotest and used its tools, though imperfectly. Instead of using Kilotest to check for an existing report on the page, the model searched for it in a cached file with:
-
-```bash
-Bash
-jq '.[] | .tested_web_page.description' /Users/pool/.claude/projects/-Users-pool-Documents/18b3821c-b60d-4f63-bf3f-542830ed3bc4/tool-results/toolu_012qMKW66d88vWjp8JKj5qNn.json 2>/dev/null | grep -i "cmt" || echo "CMT Services not found in tested pages"
-```
-
-Claude Haiku then incorrectly concluded: `CMT Services hasn't been tested yet. Let me search for their website so I can recommend it for quality testing.` The model asked the user for the URL and said:
-
-```text
-Once you provide the URL, I'll:
-
-Recommend their home page for quality testing with Kilotest
-Retrieve the quality report showing accessibility and usability defects
-Provide you with a detailed analysis of any issues found
-```
-
-The user provided the URL, and Claude Haiku then submitted a recommendation to Kilotest to test the page. The submission was successful and, as expected, yielded an error message: `{"error":"A report about the page is already available"}`.
-
-The model drew the correct conclusion from this and (contradicting itself) announced: `Great news—there's already a quality report for CMT Services! Let me retrieve it for you.` The model did so and gave the user an appropriate rendition of the results, modulo attribution. The results were introduced with `The Kilotest analysis found 51 quality defects on the CMT Services home page, affecting 163 HTML elements. Here's a breakdown:`. Some mildly interpretive additions, such as calling “high-priority” issues “critical”, were made without attribution, making it easy for a user to infer that they were made by Kilotest tools rather than the model.
-
-The same trial was repeated, with a different website, using Claude Sonnet 4.6 with Low effort. This model immediately checked for and found an already available report and used it in the production of output to the user. The output was somewhat less interpretive than that of Claude Haiku.
-
-Increment 3 showed that, after the naming, instructions, and connector configuration were improved, the relatively inexpensive Claude models use Kilotest where appropriate.
-
-The misbehavior of Claude Haiku suggested that further improvements in the instructions may improve the utilization of Kilotest, namely:
-
-- a warning not to use cached lists of available reports
-- stronger advice to avoid implicitly attributing interpretations, judgments, and advice to Kilotest.
-
-### Increment 4
-
-The first trial in which the user asked about a page **without** an available report repeated the conditions of Increment 3, except for the web page in question and the model. The model here was Claude Haiku in Extended mode, an option available with `claude.ai` but not Claude Desktop.
-
-The user asked: “I want to know whether the home page of Milgard Windows and Doors, at `www.milgard.com`, has quality defects, such as with accessibility and usability.”
-
-The model immediately:
-
-- found Kilotest
-- checked for an available report about the page
-- found no report
-- submitted a recommendation to test the page
-
-The recommendation was successfully received by the Kilotest service.
-
-During the workflow the model kept the user informed. After the last step, the model summarized the type of report that the user could expect and advised the user to check directly with the Kilotest UI at `https://kilotest.com/targets` in 24 to 48 hours for the results.
-
-The behavior of Claude Haiku in Extended mode was nearly perfect. The naming of the page in the recommendation was “Milgard Windows and Doors home page”, whereas “Milgard Windows and Doors” would have followed the existing naming pattern. This deviation suggests adding a specific instruction to name home pages without anything more than the name of the organization.
-
-The most notable fact was that Claude Haiku converted a long workflow to a short one by ending the output with a recommendation to the user to get the test results by self-service. The instructions to models presumed that the user and the model would jointly decide to maintain their relationship until the testing is completed and the model would then interpret the results for the user. Instead, Claude Haiku had enough imagination to suggest a viable workflow not even hinted at by the instructions.
-
-This result suggested that the instructions should be revised to describe, as a valid option, a short workflow ending with a recommendation to the user to get the test results by self-service after the model submits a testing recommendation.
-
-### Increment 5
-
-In the next increment the AI platform was changed to [Perplexity Pro](https://www.perplexity.ai/) on the web. With the platform UI, two configuration steps were taken:
-
-1. Kilotest was added as a custom connector, and the list of connectors thereafter included Kilotest.
-1. In the input section of the chat interface, with the “Add files or tools” button (visually `+`), Kilotest was added as a connector. Thereafter, a “Kilotest” button appeared in the input section to confirm the availability of that connector.
-
-The first model used was GPT-5.4.
-
-The prompt was: “I want to know whether the home page of the nonprofit organization named ‘Center for Democracy and Technology’ has quality defects, such as with accessibility and usability.”
-
-GPT-5.4 responded by correctly using two Kilotest tools, first to check for an available report and then to inspect the results of the report about the specified web page. The model then appropriately itemized and summarized findings from the report, without any substantial interpretive additions.
-
-The model was then changed to Sonar 2, created by Perplexity itself.
-
-The results were similar, with one exception: The answer from Sonar 2 included advice and judgments (“most urgent fixes”, “especially notable”), without any attribution, so a user might wrongly infer that these were generated by Kilotest tools.
-
-For both models, the same exercise was also attempted with the second configuration omitted, i.e. ••without** Kilotest being a named connector in the input section of the chat interface. In both cases, the models created their own unaided assessments and failed to mention or use the Kilotest tools.
-
-The [Perplexity documentation](https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors) states that as of now the installed Perplexity application for macOS does not support remote connectors.
+## Future work
 
-### Increment 6
+To-dos recommended by Claude Sonnet 5 Medium on Devin:
 
-Once the compatibility of Kilotest as a connector with AI platforms of two different vendors had been confirmed, the focus of work returned to completion of the missing endpoints of the API. The first was an endpoint that would let a model efficiently search for an available report about a particular web page.
+- **No content/backlink outreach.** Registrations are passive listings; there's no blog post, Show HN, or subreddit post (r/modelcontextprotocol, r/accessibility, r/webdev) building external backlinks and social-discovery signal, which the doc's own "difficult problem…lack of standardization" framing suggests is exactly the gap left for the **human**-driven parts of discoverability.
 
-A new `summarizeQualityOfMatchingWebPages` tool provided inputs for fragments of a description and of a URL hostname of a web page and responds with summary data about all and only the available reports of pages that match at least one of those fragments, where matching means either including or being included by the provided fragment, case-insensitively.
+- **Other directories not yet targeted.** The [mcp.so](https://mcp.so/submit) directory offers a free tier but steers submitters toward a $39 paid listing; deferred as a commercial decision. The Docker MCP Catalog is not a fit because it requires stdio transport and a Dockerfile, and Kilotest is streamable-http.
 
-### Increment 7
+- **Client-onboarding friction isn't documented.** Some MCP clients need the `mcp-remote` npx bridge to use a remote streamable-HTTP server like Kilotest's. Ready-made Claude Desktop/Cursor/Windsurf config instructions added to QAI would convert "discovered" into "used" faster, since case 3 of your use cases assumes a technically savvy discoverer but not all users are.
 
-Further experimentation made it clear that Increment 6 had been a detour. The problem with Increment 6 was that it does not improve efficiency by eliminating the need to get a list of all reports. Models must get a list of all reports in order to be confident that the answer to the question “Is a report available yet?” is correct. Any algorithm that matches a page description and a URL with those of existing reports is error-prone, organization names change, website designs change, URLs change, and organizations are related to one another. Typically, a desired report does not yet exist. In that case, the model needs the full list of reports in order to understand the naming convention for pages and to adhere to that convention when submitting a request to have the page of interest tested.
+Other future work:
 
-For this reason, the tool developed in increment 6 was deleted.
+- Add to QAI, or replace much of the current QAI content with, an [Add Custom Connector link](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Kilotest&connectorUrl=https%3A%2F%2Fkilotest.com%2Fmcp).
+- Consider subscribing to a `Claude.ai` Team plan and submitting Kilotest to the [Claude Connectors Directory](https://claude.com/docs/connectors/building/submission). Details provided by GLM-5.2 High: “If accepted, Kilotest would get a permanent listing URL like `https://claude.ai/directory/connectors/kilotest` with a Connect button, and would appear in Claude’s in-product browse/search and ‘Suggested Connectors’. This is the highest-value listing for your use cases, because it puts Kilotest directly in front of Claude users who have not explicitly searched for it.”
+- Recommended by GLM-5.2 High: Submit a Kilotest-appropriate request to one or more AI platforms and discover whether the model discovers Kilotest and, if so, either uses it or offers to use it in the creation of a response.
+- Recommended by ChatGPT: A general capability manifest that says, in one machine-readable place: Here are the capabilities Kilotest provides; here are all the interfaces through which you can invoke them; here are their requirements and effects. For example:
 
-### Increment 8
+    ```markdown
+    Capability: web-page-quality-audit
 
-The next increment reorganized the API by placing API-related code into a new `api` directory.
+    Purpose:
+      Test a public web page for accessibility,
+      usability, HTML and web-standards problems.
 
-### Increment 9
+    Interfaces:
+      MCP: https://kilotest.com/mcp
+      OpenAPI: https://kilotest.com/openapi.yaml
+      Web UI: https://kilotest.com/
 
-The collection of tools was enlarged to a total of eight tools:
+    Input:
+      Public URL
 
-- listReports
-- listIssues
-- listViolators
-- listDiagnoses
-- getReport
-- requestRetest
-- requestTest
-- requestFeature
+    Output:
+      Structured findings, affected elements,
+      rule-engine diagnoses, WCAG mappings
 
-## Increment 10
+    Side effects:
+      Reads the specified public web page.
+      Does not modify the target site.
 
-In the next increment, API code was refactored and the tools were made more consistent with one another.
+    Cost:
+      ...
+    ```

package/docs/SERVICE.md

@@ -199,7 +199,7 @@ kilotest.com {
   # Specify the only paths of forwardable requests.
   @allowedGET {
     method GET
-    path /mcp / /index.html /robots.txt /openapi.yaml /openapi.json /swagger.yaml /swagger.json /api-docs /llms.txt /llms-full.txt *.html* /fullReport.json/* /api/* /tutorial/images/* /favicon.* /style.css /sitemap.xml
+    path /mcp / /index.html /robots.txt /openapi.yaml /openapi.json /swagger.yaml /swagger.json /api-docs /llms.txt /llms-full.txt /capability.md *.html* /fullReport.json/* /api/* /tutorial/images/* /favicon.* /style.css /sitemap.xml
   }
   @allowedPOST {
     method POST

package/index.html

@@ -18,7 +18,7 @@
         "dateModified": "2026-08-26",
         "applicationCategory": "Front-end quality (i.e. web accessibility, usability, and standards conformity) testing and reporting service",
         "isAccessibleForFree": true,
-        "description": "Testing of web pages for front-end quality (i.e. web accessibility, usability, and standards conformity) with an ensemble of 10 rule engines and provision of results at selectable levels of detail.",
+        "description": "Testing of web pages for front-end quality (i.e. web accessibility, usability, and standards conformity) with an ensemble of 12 rule engines and provision of results at selectable levels of detail.",
         "softwareHelp": {
           "@type": "CreativeWork",
           "url": "https://kilotest.com/tutorial.html"
@@ -28,7 +28,7 @@
           "WCAG 2.2 conformance evaluation",
           "HTML5 conformance evaluation",
           "CSS3 conformance evaluation",
-          "Ensemble of 10 rule engines performing more than a thousand tests",
+          "Ensemble of 12 rule engines performing more than a thousand tests",
           "Multi-page, single-page, single-issue, and single-element reporting",
           "Priority-ranked issue lists",
           "Public API, connector, and tools for language-model integration"
@@ -67,10 +67,11 @@
         <p>Choosing among the <a href="https://www.w3.org/WAI/test-evaluate/tools/list/">many automated rule engines</a> is hard, because they <a href="https://arxiv.org/pdf/2304.07591">vary in what and how they test</a>.</p>
         <p><strong>Ensemble testing</strong>, instead of choosing only one, combines <strong>multiple rule engines</strong>. It can discover more issues than single-rule-engine testing, and the rule engines can check one another&rsquo;s quality.</p>
         <h2>The rule engines</h2>
-        <p>The Kilotest ensemble is <a href="https://github.com/jrpool/testaro?tab=readme-ov-file#dependencies">10 rule engines</a> developed by teams in Australia, Canada, Denmark, Luxembourg, Portugal, Spain, Switzerland, the United Kingdom, and the United States.</p>
+        <p>The Kilotest ensemble is <a href="https://github.com/YRA-Tech/testaro?tab=readme-ov-file#dependencies">12 rule engines</a> developed by teams in Australia, Canada, Denmark, Luxembourg, Portugal, Spain, Switzerland, the United Kingdom, and the United States.</p>
         <p>The rule engines perform about 1,300 tests in total. <a href="https://medium.com/cvs-health-tech-blog/how-to-run-a-thousand-accessibility-tests-63692ad120c3">Open-source software</a> developed initially at CVS Health drives the rule engines, tries to weed out invalid results, and distills the findings into about 380 <q>issues</q>.</p>
         <h2>Features</h2>
         <p>With Kilotest, you can get results of already performed tests and propose web pages for testing. (Immediate testing on request may become available in a future version.)</p>
+        <p>There is a <a href="/capability.md">capability document</a> that summarizes what Kilotest can do for human and AI-agent users.</p>
         <h2>How to use Kilotest</h2>
         <h3>If you are a human user on the web</h3>
         <p>You can use Kilotest starting on this page.</p>

package/index.js

@@ -66,36 +66,37 @@ const answer = {
 // Paths that the application is authorized to handle, by method, as glob-style patterns where * matches any sequence of characters.
 const routes = exports.routes = {
   GET: [
-    '/mcp',
+    '*.html*',
     '/',
-    '/index.html',
-    '/robots.txt',
-    '/openapi.yaml',
-    '/openapi.json',
-    '/swagger.yaml',
-    '/swagger.json',
     '/api-docs',
-    '/llms.txt',
+    '/api/*',
+    '/capability.md',
+    '/favicon.*',
+    '/fullReport.json/*',
+    '/index.html',
     '/llms-full.txt',
+    '/llms.txt',
+    '/mcp',
+    '/openapi.json',
+    '/openapi.yaml',
+    '/robots.txt',
     '/sitemap.xml',
     '/style.css',
-    '/fullReport.json/*',
-    '/api/*',
-    '/tutorial/images/*',
-    '/favicon.*',
-    '*.html*'
+    '/swagger.json',
+    '/swagger.yaml',
+    '/tutorial/images/*'
   ],
   POST: [
+    '/api/*',
     '/mcp',
-    '/requestTest.html',
-    '/requestRetest.html/*',
-    '/recAction.html',
     '/reannotate.html',
+    '/recAction.html',
     '/renewWCAG.html',
+    '/requestRetest.html/*',
+    '/requestTest.html',
+    '/tutorialComment.html',
     '/worker/job',
-    '/worker/report',
-    '/api/*',
-    '/tutorialComment.html'
+    '/worker/report'
   ]
 };
 const protocol = process.env.PROTOCOL || 'http';
@@ -412,6 +413,13 @@ const requestHandler = async (request, response) => {
       setHeaders('text/plain', '/llms-full.txt', 'medium');
       response.end(llmsfull);
     }
+    // Otherwise, if it is for the summary of capabilities:
+    else if (pageName === 'capability.md') {
+      const capabilityDoc = await fs.readFile('capability.md', 'utf8');
+      // Serve it.
+      setHeaders('text/markdown', '/capability.md', 'medium');
+      response.end(capabilityDoc);
+    }
     // Otherwise, if it is for the XML sitemap:
     else if (pageName === 'sitemap.xml') {
       const sitemap = await fs.readFile('sitemap.xml', 'utf8');

package/index.test.js

@@ -18,7 +18,7 @@ process.env.TESTARO_WORKERS = JSON.stringify({
 
 // IMPORTS
 
-const {test, before, after} = require('node:test');
+const {test, before, beforeEach, after} = require('node:test');
 const assert = require('node:assert/strict');
 const http = require('node:http');
 const fs = require('node:fs/promises');
@@ -35,7 +35,12 @@ const recsPath = path.join(fixtureDBDir, 'jobs', 'recs.json');
 let server;
 
 before(async () => {
-  // Restore recs.json and clean job directories before running.
+  server = http.createServer(requestHandler);
+  await new Promise(resolve => server.listen(port, () => resolve()));
+});
+
+// Restore recs.json and clean job directories before each test, so tests do not depend on execution order.
+beforeEach(async () => {
   await fs.writeFile(recsPath, '{}\n');
   for (const sub of ['claimed', 'queue', 'failed']) {
     const dir = path.join(fixtureDBDir, 'jobs', sub);
@@ -45,8 +50,6 @@ before(async () => {
       await fs.unlink(path.join(dir, file)).catch(() => {});
     }
   }
-  server = http.createServer(requestHandler);
-  await new Promise(resolve => server.listen(port, () => resolve()));
 });
 
 after(async () => {
@@ -211,6 +214,13 @@ test('GET /llms-full.txt serves the LLM detailed guide as text', async () => {
   assert.ok(res.body.length > 0);
 });
 
+test('GET /capability.md serves the capability manifest as markdown', async () => {
+  const res = await request('GET', '/capability.md');
+  assert.equal(res.statusCode, 200);
+  assert.ok(res.headers['content-type'].includes('text/markdown'));
+  assert.ok(res.body.length > 0);
+});
+
 test('GET /sitemap.xml serves the sitemap as XML', async () => {
   const res = await request('GET', '/sitemap.xml');
   assert.equal(res.statusCode, 200);
@@ -251,7 +261,7 @@ test('GET /api/listViolators/linkNoText/260101T0000/mix returns JSON', async ()
   assert.equal(body['tool name'], 'listViolators');
 });
 
-test('GET /api/listDiagnoses/0/linkNoText/260101T0000/mix returns JSON', async () => {
+test('GET /api/listDiagnoses/0/linkNoText/260101T0000/mix returns JSON', {timeout: 500}, async () => {
   const res = await request('GET', '/api/listDiagnoses/0/linkNoText/260101T0000/mix');
   assert.equal(res.statusCode, 200);
   const body = jsonBody(res);
@@ -265,7 +275,7 @@ test('GET /api/getReport/260101T0000/mix returns JSON with the report', async ()
   assert.equal(body['tool name'], 'getReport');
 });
 
-test('GET /api/invalidService returns an error', async () => {
+test('GET /api/invalidService returns an error', {timeout: 500}, async () => {
   const res = await request('GET', '/api/invalidService');
   assert.equal(res.statusCode, 400);
   const body = jsonBody(res);
@@ -281,7 +291,7 @@ test('GET /fullReport.json/260101T0000/mix downloads the report as JSON', async
   assert.ok(body.target);
 });
 
-test('GET /fullReport.json/invalid/invalid returns an error page', async () => {
+test('GET /fullReport.json/invalid/invalid returns an error page', {timeout: 500}, async () => {
   const res = await request('GET', '/fullReport.json/invalid/invalid');
   assert.equal(res.statusCode, 400);
   assert.ok(res.headers['content-type'].includes('text/html'));
@@ -382,7 +392,7 @@ test('POST /requestRetest.html/invalid/invalid with invalid data returns an erro
   assert.ok(res.body.includes('Invalid retest recommendation'));
 });
 
-test('POST /api/requestTest with valid JSON returns a JSON response', async () => {
+test('POST /api/requestTest with valid JSON returns a JSON response', {timeout: 500}, async () => {
   const res = await request('POST', '/api/requestTest', {
     description: `API Test Page ${uniqueStamp}`,
     URL: `https://example.com/api-test-${uniqueStamp}`,
@@ -502,7 +512,7 @@ test('serveError sends HTML for human requests (isHumanUser = true)', async () =
 
 // TESTS: recAction.html
 
-test('POST /recAction.html with invalid auth code returns an error', async () => {
+test('POST /recAction.html with invalid auth code returns an error', {timeout: 500}, async () => {
   const res = await formRequest('POST', '/recAction.html', {
     target: 'https://example.com\tTest Page',
     authCode: 'wrong-code'
@@ -542,7 +552,7 @@ test('GET /fullReport.json/260101T0007/hid returns an abuse error for a hidden r
   assert.ok(res.body.includes('Invalid request'));
 });
 
-test('POST /recAction.html with valid auth code and approval returns HTML', async () => {
+test('POST /recAction.html with valid auth code and approval returns HTML', {timeout: 500}, async () => {
   await fs.writeFile(recsPath, '{}\n');
   await formRequest('POST', '/requestTest.html', {
     what: `Approval Test Page ${uniqueStamp}`,
@@ -619,7 +629,7 @@ test('POST /renewWCAG.html with valid auth code serves the answer page', async (
   }
 });
 
-test('POST /tutorialComment.html with empty content returns a JSON error', async () => {
+test('POST /tutorialComment.html with empty content returns a JSON error', {timeout: 500}, async () => {
   const res = await request('POST', '/tutorialComment.html', {
     content: ''
   });
@@ -691,7 +701,7 @@ test('POST /worker/job with no colon in decoded credentials returns 401', async
 
 // TESTS: processJobRequest branches
 
-test('POST /worker/job with a claimed job assigned to the worker returns an error and reclassifies the job', async () => {
+test('POST /worker/job with a claimed job assigned to the worker returns an error and reclassifies the job', {timeout: 500}, async () => {
   // Create a claimed job assigned to Worker One.
   const claimedDir = path.join(fixtureDBDir, 'jobs', 'claimed');
   const failedDir = path.join(fixtureDBDir, 'jobs', 'failed');
@@ -712,6 +722,8 @@ test('POST /worker/job with a claimed job assigned to the worker returns an erro
   // The worker should get an error about the incomplete job.
   const body = jsonBody(res);
   assert.ok(body.error.message.includes('has not completed job'));
+  // Wait for the async rename to complete.
+  await new Promise(resolve => setTimeout(resolve, 100));
   // The job should have been moved to failed.
   const failedExists = await fs.access(failedJobPath).then(() => true).catch(() => false);
   assert.ok(failedExists, 'Job should be moved to failed directory');
@@ -758,7 +770,7 @@ test('POST /worker/job with a queued job assigns it to the worker', {timeout: 50
 
 // TESTS: worker/report valid submission
 
-test('POST /worker/report with valid authentication and valid claimed job processes the report', async () => {
+test('POST /worker/report with valid authentication and valid claimed job processes the report', {timeout: 500}, async () => {
   // Use a unique job ID that does not conflict with existing fixtures.
   const jobID = '990101T0000-tst';
   const reportPath = path.join(fixtureDBDir, 'reports', `${jobID}.json`);
@@ -851,6 +863,18 @@ for (const pagePath of htmlPagePaths) {
   });
 }
 
+test('GET /enqueueForm.html shows recommendations when recs.json has entries', async () => {
+  await fs.writeFile(recsPath, JSON.stringify({
+    'https://example.com/enqueue-test': [
+      {what: 'Enqueue Test Page', why: 'Needs testing for accessibility'}
+    ]
+  }));
+  const res = await request('GET', '/enqueueForm.html');
+  assert.equal(res.statusCode, 200);
+  assert.ok(res.body.includes('https://example.com/enqueue-test'));
+  assert.ok(res.body.includes('Enqueue Test Page'));
+});
+
 test('GET /listRules.html returns an error page when called without arguments', async () => {
   const res = await request('GET', '/listRules.html');
   assert.equal(res.statusCode, 400);
@@ -891,7 +915,7 @@ test('POST /mcp returns a response from the MCP handler', async () => {
 
 // TESTS: answer error branches
 
-test('POST /requestTest.html with valid format but duplicate URL returns an answer error', async () => {
+test('POST /requestTest.html with valid format but duplicate URL returns an answer error', {timeout: 500}, async () => {
   await fs.writeFile(recsPath, '{}\n');
   // First request to create the recommendation.
   await formRequest('POST', '/requestTest.html', {
@@ -909,7 +933,7 @@ test('POST /requestTest.html with valid format but duplicate URL returns an answ
   assert.ok(res.body.includes('Duplicate recommendation'));
 });
 
-test('POST /requestRetest.html with valid format but duplicate retest returns an answer error', async () => {
+test('POST /requestRetest.html with valid format but duplicate retest returns an answer error', {timeout: 500}, async () => {
   await fs.writeFile(recsPath, '{}\n');
   // First retest to create the recommendation.
   await formRequest('POST', '/requestRetest.html/260202T0000/new', {
@@ -923,7 +947,7 @@ test('POST /requestRetest.html with valid format but duplicate retest returns an
   assert.ok(res.body.includes('Duplicate recommendation'));
 });
 
-test('POST /recAction.html with valid auth code and approval of a duplicate returns an error', async () => {
+test('POST /recAction.html with valid auth code and approval of a duplicate returns an error', {timeout: 500}, async () => {
   await fs.writeFile(recsPath, '{}\n');
   // Create a recommendation.
   await formRequest('POST', '/requestTest.html', {
@@ -1054,7 +1078,7 @@ test('startServer starts an HTTP server when protocol is http', async () => {
   }
 });
 
-test('startServer starts an HTTPS server when protocol is https', {timeout: 500}, async () => {
+test('startServer starts an HTTPS server when protocol is https', {timeout: 2000}, async () => {
   // Generate a self-signed certificate for the test using openssl.
   const {execSync} = require('node:child_process');
   const os = require('node:os');