Skip to content

docs(verify): retire the fixed #75 and #76 known findings - #104

Merged
Upd4ting merged 1 commit into
mainfrom
docs/ant-1811
Nov 10, 2026
Merged

Upd4ting merged 1 commit into
mainfrom
docs/ant-1811

Conversation

@Upd4ting

Copy link
Copy Markdown
Member

Why

The verify-interface skill still listed #75 and #76 as open known findings. Both are closed. #99 registers @Get("") at the controller root, and #101 refuses @Connection on handlers that never receive a connection. An agent reading the skill learned behaviour that is no longer true. The route-locations journey also stripped one trailing slash, so it pinned neither form of the root location.

What changed

Proof

Verify journeys the retired findings pointed at, run on this branch's packed build:

$ antelopejs-verify journey "$RUN" routes
PASS routes/route-locations (0.0 s)
PASS routes/route-errors (0.0 s)
$ antelopejs-verify journey "$RUN" parameter-sources injected-values
PASS parameter-sources/injected-values (0.0 s)
$ antelopejs-verify journey "$RUN" --plan
PASS smoke/core-calls (0.4 s)
PASS smoke/export-surface (0.0 s)

The same route-locations journey with src/routes.ts set back to the pre-#99 join (${controller.location}/${segment}), a local change that was not committed:

FAIL routes/route-locations (0.0 s)
    02-run-the-route-locations-scenario: route-locations answers as docs/ states (expected "{\"routes\":[[\"handler\",\"get\",\"/users/listUsers\",\"listUsers\",null],[\"handler\",\"get\",\"/users\",\"root\",null],...

With the strip in place, that regression would pass.

pnpm run checks:

Checks: 9 passed, 0 failed.
flowchart LR
  A["@Get("") on Controller("/users")"] --> B[ProcessCallback]
  B --> C["location /users"]
  C --> D{"route-locations journey"}
  D -- "before: strip one trailing slash" --> E["/users and /users/ both pass"]
  D -- "after: compare as registered" --> F["only /users passes"]
Loading

@Upd4ting
Upd4ting merged commit a5650d9 into main Nov 10, 2026
7 checks passed
@Upd4ting
Upd4ting deleted the docs/ant-1811 branch November 10, 2026 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant