route.prefix_api: Route group prefix does not start with its API's prefix

Route group prefix does not start with its API's prefix.

Area 7, HTTP; not declinable; the next step is usually the agent's.

A group's prefix starts with its API's, so each API's routes, OpenAPI document and record stay its own:

example

application {    apis: {        main: {            prefix: /v1        }    }}

example

use memos/types { MemoView }use memos/actions { AddMemo, add_memo }routes Memos {    prefix: /memos    POST / {        authentication: RouteAuthentication.none        input: AddMemo        output: MemoView        run: add_memo(input)    }}

text

error: `Memos`'s prefix doesn't start with API `main`'s --> domains/memos/routes/memos.jadpo:5:13  |5 |     prefix: /memos  |             ^^^^^^ outside `/v1`  reason: A group's prefix starts with its API's (`/v1` for `main`), so each API's routes, OpenAPI document and record stay its own.  next: Start the prefix with `/v1`, or name the group's API with `api:` (agent)  rule: route.prefix_api  help: https://jadpo.dev/docs/errors/route.prefix_apicheck failed: 1 error, 5 files