Windows fix

[gaob3441-arch]

I'm not sure whether these always work reliably:

filePath, handlerName := getHandlerInfo(route.HandlerFunc)
filePath, _ := funcInfo.FileLine(ptr)

So I added a code generator that scans the source code before build time and generates annotation metadata and struct information.

I also added an @body annotation to make it easier to populate request body parameters.

example:

$ go run github.com/ckanthony/gin-mcp/cmd/annotate-gen ./backend/internal/server/
Generated [_path_]/backend\internal\server\annotations_gen.go (1 handlers, 44 structs)

func init() {
	convert.SetGeneratedAnnotations(map[string]*convert.HandlerDoc{
		"login": {
			Summary: "Get API TOKEN",
			Description: "Get access token and refresh token with username and password",
			OperationID: "POST_api_auth_login",
			BodyTypeName: "loginRequest",
			Params: map[string]string{
				"tag": "Filter products by tag",
			},
			Tags: []string{"Authentication", "Login", "Token"},
		},
	})

	convert.SetGeneratedStructs(map[string]*types.StructMeta{
		"Server": {
			Name: "Server",
			Fields: []types.FieldMeta{
				{JSONName: "store", Type: "string"},
				{JSONName: "jwtSecret", Type: "string"},
				{JSONName: "builtinProviders", Type: "object"},
				{JSONName: "queryCache", Type: "string"},
			},
		},
		"binaryExpression": {
			Name: "binaryExpression",
			Fields: []types.FieldMeta{
				{JSONName: "op", Type: "string"},
				{JSONName: "left", Type: "string"},
			},
		},

That‘s enough. After startup, the body parameters and the information from the annotations can be displayed correctly.

[ckanthony]

Thanks for this — I test-merged it onto main locally: clean merge, all 180 tests pass, vet/gofmt clean. The code itself works.

Before merging I need a few things:

1. Retitle the PR. "Windows fix" doesn't describe this — it's a compile-time annotation generator plus @Body support. Something like "feat: add annotate-gen code generator and @Body annotation" would be accurate.

2. README documentation. annotate-gen is a user-facing tool (go run github.com/ckanthony/gin-mcp/cmd/annotate-gen

   ) and @Body is a new annotation — both need a README section covering: what problem codegen solves (runtime reflection via FileLine being unreliable), how to run it, where the generated file lands, and the @Body syntax.

3. Generated-file guidance. Should annotations_gen.go be committed or gitignored + regenerated in CI/go:generate? Please document the intended workflow.

Minor (non-blocking): consider a go:generate example in the docs once you add them.