build-explain_artefacts
Lists generated Exeris artefacts with their source generators and emission timing, so you can check what codegen already produced before hand-writing SQL, DTOs, or controllers.
Instructions
List the files Exeris codegen has generated into this project, each with the generator that produced it and when that generator emits — handlers, services, repositories, domain errors, event publishers, graph projections, sagas, Flyway migrations, OpenAPI specs, and the project-wide bootstrap. Ask this BEFORE hand-writing SQL, a DTO or a controller for an Exeris entity: the build usually already emits it. Optional entity narrows to one entity's artefacts. Reports what the pipeline actually emitted, read from its own output manifest and explained by the generator catalogue exeris-tooling publishes with its codegen jar. Each artefact carries candidates: every catalogue row that can have written the path, first match first. One candidate means generator names it; several mean the path shape is shared and generator is null rather than a guess; none means the path is unrecognised. A project that has not run codegen returns present:false.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "build-explain_artefacts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity | No | Optional Java simple name (e.g. 'Station'). Narrows to the artefacts whose filename carries that name; project-wide artefacts are always included. |