The OpenAPI coverage test fails on a NOT_YET_DESCRIBED entry that is now described, and the stale entries leave #5407

A NOT_YET_DESCRIBED entry that is already described now fails the OpenAPI coverage test, and I deleted the 15 stale entries from the list. test/openapi-coverage.test.ts passes (3 tests). I did not run the rest of the suite, and the forge's check will run the full set on this push.

• New check: a new test, "NOT_YET_DESCRIBED has no entry that is now described", fails with a message that names each stale line to delete. I removed the removable filter and the console.log from the first test.
• Comment: the comment above the list now says that describing a route means deleting its line, and that the test fails until you do.
• Stale entries removed: the 15 were all described on main when I started. They are the routes behind #5240, #5241, #5242, #5245, #5040, #5150 and #5153, plus others. I took the list from the new test's own failure output rather than guessing.
• Rebase: the branch is based on current origin/main, with nothing to rebase. The other open OpenAPI issues delete lines from the same list, so those pulls may need a rebase.

Only the test file changed. To try it, run bun test test/openapi-coverage.test.ts.

Closes #5396

A NOT_YET_DESCRIBED entry that is already described now fails the OpenAPI coverage test, and I deleted the 15 stale entries from the list. test/openapi-coverage.test.ts passes (3 tests). I did not run the rest of the suite, and the forge's check will run the full set on this push.

• New check: a new test, "NOT_YET_DESCRIBED has no entry that is now described", fails with a message that names each stale line to delete. I removed the removable filter and the console.log from the first test.
• Comment: the comment above the list now says that describing a route means deleting its line, and that the test fails until you do.
• Stale entries removed: the 15 were all described on main when I started. They are the routes behind #5240, #5241, #5242, #5245, #5040, #5150 and #5153, plus others. I took the list from the new test's own failure output rather than guessing.
• Rebase: the branch is based on current origin/main, with nothing to rebase. The other open OpenAPI issues delete lines from the same list, so those pulls may need a rebase.

Only the test file changed. To try it, run bun test test/openapi-coverage.test.ts.

Steward: this pull is approved but no longer merges into main. #5932 split src/http/mcp.ts into one file per tool, and several other shared files moved. Bring it up to date with main: merge main and resolve keeping this pull's intent. If it adds or changes an MCP tool, move that into its own file in the new layout and regenerate the docs. Then let the check run. If the change is already on main, say so and close the pull.

The branch is merged with main again and pushed. The coverage test passes locally (3 of 3). I didn't run the type check or the rest of the suite; the forge's check runs those on this push.

What changed

• A NOT_YET_DESCRIBED entry for a route that now has an OpenAPI row fails test/openapi-coverage.test.ts. The failure lists the exact lines to delete. This is a test-only change with nothing to see in the preview.
• The merge conflicted only in that test file, because main moved the route rows into one file each under src/contract/openapi/routes/ and removed other entries in the meantime. I took main's version of the file and re-applied this pull's change on top of it.
• I deleted the entries that are described as of main now. That is 15 entries, so it is a different number from the earlier diff's 26. Main removed some of the old ones itself.
• The "could be removed" console.log that main had added is gone. The new failing test replaces it, and its comment now says a stale entry fails the test.
• Nothing in this pull touches the MCP tools, so the src/http/mcp.ts split didn't affect it.

Left out: describing the remaining routes, which is separate work.

The OpenAPI coverage test now fails with the exact lines to delete whenever a NOT_YET_DESCRIBED entry becomes described. I deleted the 15 entries that were already stale. The branch is clean and matches origin, so I pushed nothing new for this review.

• Stale entries: the test only checked that every route was either described or listed. It never complained when a listed route had since been described, so the list could not shrink. It now reports each stale entry and the line to remove.
• Cleanup: the 15 removed entries are the ones the old test would have flagged on the base.
• Console output: I removed the console.log and fixed the comment so it matches what the test does.
• No other changes: this is a test-only pull, so there is no app change and no preview surface.

Juniper approved with no requested changes, so there was nothing to address. Their two follow-ups are left out on purpose:

• More route descriptions: describing the remaining routes, starting with the user, origins and browse reads, belongs in its own pull.
• Telling other OpenAPI pulls to rebase: I did not contact them. Any open pull that edits NOT_YET_DESCRIBED will need to rebase onto this one, and the test output now names the stale lines to drop.

To try it, run bun test on the OpenAPI coverage test. To see it fail, remove a described route's path from the "described" set, or add an already-described route back to NOT_YET_DESCRIBED.

Parked by the crew: the last three runs here failed or were declined within an hour, so nothing more starts until a person says what to try.

The branch changes nothing new this turn. The feedback is a note that the crew parked this pull, not a request for a code change. The branch is already pushed and has no unpushed commits.

What the pull does: test/openapi-coverage.test.ts now fails when a NOT_YET_DESCRIBED entry is already described in the OpenAPI document. The 15 stale entries are deleted. The latest merge of main also dropped entries that had since been described.

Check this turn: I ran bun test test/openapi-coverage.test.ts and all 3 tests pass. I started the full bun test but did not wait for it to finish, so I have no full-suite result.

What I left out: I did not restart or retry anything beyond that check. The note says nothing more starts until a person says what to try, so I'm waiting for that.

Handed to a person by the crew: this pull is approved, but 2 runs to bring it up to date with main ended without a push, so no more start here. Conflicting files: test/openapi-coverage.test.ts. Merge main into it, or say what to try and assign it back to the crew. (The forge posts this under your name; you did not write it.)

Handed to a person by the crew: this pull is approved, but 2 runs to bring it up to date with main ended without a push, so no more start here. Conflicting files: test/openapi-coverage.test.ts. Merge main into it, or say what to try and assign it back to the crew. (The forge posts this under your name; you did not write it.)

This pull now fails the OpenAPI coverage test on a NOT_YET_DESCRIBED entry that is already described, and the stale entries are removed. I merged current main into the branch and pushed it. test/openapi-coverage.test.ts was the only file that conflicted.

• Conflict: main had added and removed entries in the same list as this branch. I merged both sides, sorted the list, and then deleted every entry whose route now has an OpenAPI row.
• Tests: the three tests in test/openapi-coverage.test.ts pass after the merge. That covers "every route has a row or is listed", "no listed entry is now described" and "the list is sorted and names registered routes". I did not run the full bun test or the type check. No source files changed in the merge.
• What the list is now: against main, the test file changes 8 lines added and 52 removed. The remaining entries are routes that are still undescribed.
• What I left out: describing any of the remaining routes. That is separate work, and the test makes sure each one gets removed from the list once it is described.

To try it, run bun test test/openapi-coverage.test.ts.