@jrpool/kilotest 38.0.0 → 38.1.0

package/docs/decisions/001-api-design.md

@@ -42,7 +42,7 @@ As of the date of this decision, a partial initial API version already exists: a
 
 ## Considered options
 
-1. **Iterate and instrument.** (1) Add a tool that implements level 4; then (2) add a tool that asks LLMs to comment on how the API design could better satisfy their needs; then (3) add metrics to make API usage and submitted LLM comments available to Kilotest managers.
+1. **Iterate and instrument.** (1) Finish redesigning the tools at levels 1, 2, and 3, to represent the hypothesized typical needs of LLM consumers; then (2) add a tool that implements level 4; then (3) add a tool that asks LLMs to comment on how the API design could better satisfy their needs; then (4) add metrics to make API usage and submitted LLM comments available to Kilotest managers.
 2. **Research first.** (1) Pause further API development while doing fundamental research to predict LLM needs; then (2) resume API and metrics development, including API redesign if the research results warrant.
 
 ## Decision
@@ -98,7 +98,7 @@ The sub-decision was **identifiers plus labels** (option 2). This decision was b
 - **Risk:** The cost estimate assumes a well-behaved client that preserves conversation history; a poorly implemented client could still incur higher-than-necessary costs.
   - **Mitigation:** MCP clients are expected to maintain message history by protocol; the ancestor labels provide a minimal human-friendly substitute.
 - **Risk:** Scenario 1 users may still want an aggregated "everything about page X" response.
-  - **Mitigation:** A future tool can be added to aggregate the hierarchy on the server side and return a structured summary, but that decision is deferred until usage data justify it.
+  - **Mitigation:** A future tool can be added to aggregate the hierarchy on the server side and return a structured summary, but that decision is deferred until usage and suggestions data justify it.
 
 ## References
 

package/index.js

@@ -345,7 +345,7 @@ const requestHandler = async (request, response) => {
       // If the service is provision of a list of all available reports:
       if (service === 'reportList') {
         // Get the response (potentially error) data.
-        const responseData = await require(path.join(__dirname, 'reportList', 'api')).response(specs);
+        const responseData = await require(path.join(__dirname, 'api', 'reportList')).response(specs);
         // Send them.
         setHeaders('application/json', null, 'ultra');
         response.end(JSON.stringify(responseData));
@@ -353,7 +353,7 @@ const requestHandler = async (request, response) => {
       // Otherwise, if the service is provision of a report summary:
       else if (service === 'reportSummary') {
         // Get the response (potentially error) data.
-        const responseData = await require(path.join(__dirname, 'reportSummary', 'api'))
+        const responseData = await require(path.join(__dirname, 'api', 'reportSummary'))
         .response(specs);
         // Send them.
         setHeaders('application/json', null, 'high');

package/mcp.js

@@ -12,8 +12,8 @@ const {StreamableHTTPServerTransport} = require(
 const {z} = require('zod');
 const {isReportAvailable, isURL} = require('./util');
 const targetAPI = require('./target/api');
-const reportListAPI = require('./reportList/api');
-const reportSummaryAPI = require('./reportSummary/api');
+const reportListAPI = require('./api/reportList');
+const reportSummaryAPI = require('./api/reportSummary');
 const reportIssueAPI = require('./reportIssue/api');
 const testRecFormAPI = require('./testRecForm/api');
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jrpool/kilotest",
-  "version": "38.0.0",
+  "version": "38.1.0",
   "description": "An ensemble testing service with a focus on accessibility",
   "main": "index.js",
   "scripts": {